I recommend watching this video: https://www.youtube.com/watch?v=qbKGw8MQ0i8

AFAIK biometrics are only used to unlock the device’s keychain. So, in other words, it’s no different than using fingerprints to unlock your password manager (via the device’s keychain that has your actual password).

The compression issues are true for 1080p too, any dark scene on Netflix gets some horrible color banding and artifacts.

Ironically, the pirates don’t have that issue as their multi-gig torrents don’t have much compression compared to the some-hundred megs stream provided by Netflix

An Amazon Fire Stick is far smaller, much quieter, draws less power and is simpler to use than a general-purpose PC.

Plus, if I’m using a PC I’d probably only use Linux, so I’d have to deal with lower quality streams because DRM… so overall the experience would be worse.

Using a more ‘normie’ Windows box as a streaming box could work, but that doesn’t solve the noise(!) and power draw issues, that feels like a compromise rather than a choice.

I’ve recently bought a Fire Stick and don’t regret it one bit. It’s doesn’t fell janky and doesn’t have ads as far as I can tell. The provided remote inclues an IR emitter than can turn the TV on/off and change volume (why isn’t this provided by HDMI itself is beyond me), and it’s much faster than any smart tv so you can watch content without having to wait

They’ve violated the licenses

Did they? Because as far as I know they’re complying with the GPL and other licenses, since everybody that gets their RHEL license (and the software/binaries) also gets the sources. Or am I mistaken?

I don’t think the license says ‘grant everybody a copy of your source code’, only the ones that actually bought access to the binaries RHEL provides

I’d mostly focus on scrub, but I’ll also recommend that you keep an eye on your unallocated blocks, running out of them can get you into out-of-space situations that are non-trivial to fix. My general recommendation is about 5G per device, that should give it enough breathing room that it won’t -ENOSPC on most workloads. Also, please note that unallocated space is a subset of free space, that is, all unallocated space is free space but the inverse isn’t true.

Getting more unallocated space is as easy as running a balance with a filter, say “btrfs balance start -dusage=10 /mountpoint”. Just don’t balance metadata unless you want to convert it.

Regarding defrag, I still defrag databases, system journal files, etc, even on SSDs. Those workloads tend to cause a lot of fragmentation that can impact your performance (try reading your journalctl logs before and after a defrag, as an example).