I use Vanadium/Trivalent (GrapheneOS fork of mobile Chromium and its desktop equivalent) for general internet use on a general-use system, and Firefox inside of specific qubes for specific purposes otherwise.

On a general-use system, the additional security of Vanadium and Trivalent give me a bit of peace of mind when using the same browser for admin work, sensitive stuff like banking, and general browsing.

With the Qubes model, everything is segmented and isolated anyway, so I can use Firefox, which despite its flaws has been my favorite since the Netscape days.

The dystopian part is being required by law to use a specific form of authentication tied to your real identity by the government in order to access the internet.

That sounds like a horribly dystopian solution to a horribly dystopian problem.

Four Weddings and a Funeral is a movie I adore entirely for the side characters, and pretty much ignore the two main characters and storyline completely.
The main friend group feels so real and alive and lovely, they’re charming and funny, and watching them be friends at their weddings and funeral feels like optimistic slice-of-life escapism. And beyond that, pretty much every other side character is memorable and funny and a joy to watch, especially Rowan Atkinson as the anxious priest. Great movie, 10/10, can’t remember the main characters at all.

Yep exactly! Setting up a raspberry pi low-performance computing cluster with secondary usb nics, going slowly insane trying to figure out why the vlan interfaces wouldn’t work when their base interfaces worked just fine, and going down all of the wrong rabbit holes along the way.

ifupdown2 has a 15-character interface name limit, and the systemd predictable interface naming system uses the mac address for usb nics (giving them a 15-character name), so if you try to create a vlan subinterface of a usb nic using the standard interface.vlan naming scheme on a systemd host, it will fail, and you’ll have to set up systemd network link files to rename the base interfaces to something shorter.

Yes, with the official M16A4 unit being defined as 1/100th the length between the goal lines of an American Football field.

The ups has data output to my firewall/router via usb, which the baremetal servers all connect to via apcupsd. When the ups loses or regains AC power, it broadcasts a message to all of them and they’re each scripted to act accordingly: laptops run on their own batteries, vms migrate over to laptops, non-vital hardware shuts down, etc.

Some laptop battery firmware allows you to force discharge even when connected to AC, and if your laptop can use the tlp recalibrate or tlp discharge commands then yours is supported.

I use this to power my thinkpad servers off of their own batteries during a power outage, to reduce load on my UPS. Great feature.

I switched a workstation to Secureblue for the very specific security priorities targeted by that project, but I think for the majority of users, the main reason for not switching to atomic is one you mentioned: why fix what isn’t broken? The main selling point promoted to potential new users seems to be that updates don’t break anything, but I can’t remember a single time since Debian Sarge that an update broke anything for me, and I actually find the rpm-ostree package layering and updating process to be far more of a headache than otherwise.

Unless it’s prepackaged like a steam deck, moving from the traditional way of doing things to atomic is a major change. Like any major change, people need a good reason to make it, and I think right now the only compelling ones are either hyper-specific (switching to okd and needing to build it on coreos, wanting to move to a specific atomic project, etc.), or just general curiosity.

Band of Brothers. The intro is so long, but feels like an important part of the whole experience.