Laser

I mean who currently owns Twitter? It's just another way for him to siphon money out of that company and it can't get worse for him anyways.

It's a shit move and the board that allows this are beyond saving but for Elmo and Elmo alone it makes sense.

Ja, also weder Caching noch Striping.

I know you're joking anyways, but I always cringe when I see that. There's no need to invoke su there. If you want a root shell, use sudo -s or sudo -i depending on what kind of shell you want.

Hab's im Einsatz, aber in einem sehr simplen Setup - nur eine Platte, bcachefs auf LUKS (ja, ich hatte wohl auch die interne Verschlüsselung probieren können...) - noch keinen Datenverlust, mir kommt die Platte langsam vor aber ich hatte die nie ohne bcachefs im Einsatz, daher fehlt mir der Vergleich.

Nowhere does it state that the relative can't be killed by you, or that there relative has to be dead in the first place. Very convenient. This should be an open and shut case (the STATE will lose)

I am currently running Jellyfin on Btrfs and there is quite a performance impact due to CoW. If 2 clients decide to browse the libraries, both clients grind to a near standstill with regards to being able to see things.

CoW is not recommended for databases, all DB servers advise for turning it off for the actual database. You'll run into the same issue with a dedicated database if you leave CoW on I guess. You could also disable CoW for jellyfin's database right now and performance should increase.

I also follow the progress of a dedicated DB, but on the other hand I don't know how much sense it makes architecturally. The likeliness that you have multiple jellyfin server instances access the same database is low - after all, there is info very specific to the server in there like the file path. Just migration is already not easy, how likely is sharing the database live? And if each database is specific to an instance - why not use SQLite (like it's done right now) and allow for more specific parameter tuning, like used memory and the like?

There's a keepassxc-full package that comes with all the functionality. Anyhow, Debian does not have the concept of USE flags, these don't make sense in a binary-based distribution.

That nicer place is probably at home. Not that there's anything wrong with it. But I think all fast food chains raised prices? At least here in Europe it's not like McDonald's is somehow standing out as more expensive. Worse, yes. But that was always the case

NixOS: (1, 2) - You can define specific package versions but with the large repos I doubt there is much QA going on

It depends on the nixpkgs channel you use (I'm also using the term for flakes here, though technically these are then called inputs). The main channels, those being NixOS-stable whatever the current version is at the time and NixOS-unstable have a rather big set of packages that must be built successfully before users get updates, including the tests defined in the build system plus sometimes distribution-specific tests, though these are often rather simple, like start program and see if its port is open. Even more, when a library gets updated, all programs and other libraries depending on it get rebuilt as well, including all tests.

Now what if a package outside of that scope breaks? Most likely, your new configuration won't build, so you're stuck on an older but working configuration, or it does build, but something doesn't work. But I'm the latter case, you can still choose to start the older working configuration.

Also the more complicated packages have very dedicated and capable maintainers from my experience, sure the smaller stuff is often updated mostly automatically with merge request created by bots and just the final merge approved by the maintainer, but the big infrastructure is usually tested quite well.

As a downside, this can sometimes lead to longer periods without updates when a lot of stuff has to get rebuilt and something doesn't work (multiple days, but not weeks). You can then switch to another set in case the problematic packages don't affect you, or just wait. However, saying there's little QA is unfair, in fact from my experience there's more QA in nixpkgs than in most distributions.

I don't recommend NixOS to new users because it abstracts a lot of stuff away and makes use of mechanics that are helpful to understand first. But if you're comfortable with Linux, NixOS is a great distribution that even on unstable works very well. Then again, it allows specific packages to depend on very specific versions of other packages, which is partially the reason you'd use a stable distribution.

I don't know what you're talking about.

Collabora has been quite active in the field, e.g. they're the prime developers of WINE's current Wayland solution. So it makes sense for Valve to partner up with them.

The remaining 17% just never stop