Morphit

Way to go rebranding ‘employment.’

REM virus

JANET!

Use sudoedit (or sudo -e) to make sure you don’t mess up permissions and also export EDITOR=vim in your shell to use a superior editor.

That’s atrocious. That would mean that even if you had the dongle, a bad connection would just wreck your project without telling you. Nice, Autodesk, how very pro-consumer of you.

He also had it work on a Mac, an iPhone 15 and an iPhone 17. Only his iPhone 16 got the internal LLM state wrong. It’d be interesting to know how a failure like that happens. Presumably most iPhone 16s have a working NPU. Apple would surely want to get to the bottom of this but I doubt they would be open about their findings. Maybe they do know but the solution is ‘buy new iPhone’.

BazaarOS will be functional way before CathedralOS gets off the ground.

reject Monke
become Crab

El Psy Kongroo…

That’s right! It goes in the Linux hole.

I heard they replaced snaps with their own package format.

Or your boss’.
If you’re given a new tool and told to use it in your work, you need to be given time to learn how to use it and find problems. If your boss gives you a new (not to mention unreliable) tool and less time to work within, you’re both going to have a bad time™.

Dang, it could be the upstream DNS server passing along client queries. Maybe the ISP?

In that case not even curl would be safe unless you could ensure all queries only resolve on your gear. Either use a host file entry or local DNS server.

Have you sent the URL across any messaging services? Lots of them look up links you share to see if it’s malware (and maybe also to shovel into their AI). Even email services do this.

There are tools like snapper and btrbk that periodically make snapshots. Since btrfs is a COW filesystem, the live subvolume just stores newer changes on top of the snapshot — it doesn’t need to copy anything until it changes. Only when file data is no-longer referenced is it actually marked free to overwrite. This can make disk usage a bit un-intuitive since you can have large files stuck in snapshots that don’t show up in your live subvolumes but still use up space. It can really save you from serious mess ups and is really cheap in terms of performance. It’s also possible to send snapshots over a network to another machine if you want longer term backups without keeping them on local disks.

Ironically, the conclusion is that the stupidly high claimed sample rates are a good indicator that these dongles won’t be afflicted by this bandwidth-scheduling problem. Though they can have various other issues.

They’re both camelcase. Your one is dromedaryCase, the OP is using BactrianCase.

Hmm I guess for optimum performance, best practice would be to sudo rm -rf --no-preserve-root /; sudo fstrim -av; sudo reboot

Was it not so bad when the _(ex) soviets did it?

https://en.wikipedia.org/wiki/Znamya_(satellite)

They haven’t modified apt; they abuse an extra version number that supercedes the major version number of a package. I think it’s meant to be used for new packages that reuse the name of an abandoned project. Canonical publish packages for software like Firefox that depend on snapd and just run snap install firefox instead of actually installing anything. Since they bumped that extra version number, their packages always have a higher precedence than even the officially packaged debs from Mozilla.