tarneo

I use Iceraven with ublock, privacy badger, decentraleyes and canvasblocker.

Framaforms + framacalc.

To me, this is only one of the few advantages of immutability. I have already used nixOS on a server and I really didn't like having to learn how to do everything the right way. As for distrobox, to me it sounds quite like an additional failure point: it is an abstraction over the containers concept that hides the actual way it is done from you. I'd say if you run an app in a container, go all the way: make the container yourself. To me it just sounds like a bad idea, and I didn't really like distrobox when I tried it. I just want to say that both of these concepts (immutability, distrobox) would be great if it was perfectly done. But the learning curve of nixos and the wackiness of distrobox drove me away.

I totally agree. But I just wouldn't necessarily say gentoo is a bleeding edge distro: it's kinda up to the user. They are free to configure the package manager (portage) however they want and can even do updates manually. I just like the idea of having newer packages at the cost of stability, because I also use the server as a shell account host (with an isolated user ;-)) and need things like the latest neovim. These days I would know if an update failed because I would literally be in front of the process and test services are working after the updates, so I'd know if I have to rollback. This makes it basically like a stable distro IMO (even though the packages aren't battle tested before being pushed as updates).

I'm surprised this strategy was approved for a public server

The goal was to avoid getting hacked on a server that could have many vulnerable services (there are more than 20 services on there). When I set this up I was basically freaked out by the fact I hadn't updated mastodon more than a week after the last critical vulnerability in it was found (arbitrary code execution on the server). The quantity of affected users, compared to the impact it would have if hacked, made me choose the option of auto-updates back then, even if I now agree it wasn't clever (and I ended up shooting myself I'm the foot). These days I just do updates semi-regularly and I am subscribed to mailing lists like oss-security to know there's a vulnerability as early as possible. Plus I am not the only person in charge anymore.

Librewolf, icecat, qutebrowser, iceraven, surf... are not chromium-based.