Layer things that genuinely need (often in boot sequence) low level access like filesystems (e.g. I have mergerfs+snapraid on my desktop). If you’re OK with a longer rpm-ostree update, you can layer some self contained things like btop with little risk, perhaps also your preferred shell. Also anything you want in TTYs if something breaks.

vim edit /etc/fstab works fine from within a distrobox, you just need to do sudo vim /run/host/etc/fstab or distrobox-export the binary to your main shell, which means that the container will start, but you don’t have to enter it. If you fire a terminal profile into the container by default at login you won’t need to start the container when you use an exported command.

Embrace the distrobox experience for development and generally mucking around, use Arch’s AUR, archive entire environments, there’s lots going for it.

Linux brew is coming along nicely, use it first if there’s a formula, but I’ve been fine with flatpak, distrobox and layers (in that order) for a couple of years now.

Black Mirror X Do Not Create The Torment Nexus

Thanks Yanks, I’m sure this won’t become the new normal worldwide. Mainlining Palantir via AR while Tolkien spins in his grave.

0/10 on the software side

Sadly to be assumed these days unless proven otherwise, that or hardcore trapped in a walled garden…

digging on Magastan!

Here’s a guy who Cracks His Knuckles in Only One Hand for Over 60 Years. What you need to worry about is when they stop cracking, symptom of systemic inflammation.

Look at adb or LineageOS, otherwise make sure to factor it in for your next phone (second hand + a new battery replacement pack from iFixit works well these days, not as bad as you think doing it, Pixels 8 and above get 7 years of security updates).

Check out https://github.com/CaramelFur/GPhotosShim which stops GCam from using Photos. This is why my gOS uses GCam with network denied (because it works way better on Pixels than the OSS equivalent).