I beg to slightly differ, but it’s a good take overall:
>:3 rawr
Aeon is the way
As pointed out by @themoonisacheese, immutable distros are getting some traction recently and they are good for making a system reproductible, allowing easy rollbacks, but this should not make a big difference, privacy-wise. It also add some work for configuration / learning. Here are two levels I’m thinking of from what you presented:
You go with any stable (big fan of Debian here too) so to avoid data breaches from brand new packages (xz…), then you can compartimentize your application with Flathub and manage the rights with Flatseal. If you go with software with less telemetry (Firefox), this should be a reasonable and easy to use setup. The rest of the privacy will depend on what is going on inside of your web browser, probably.
The next step would be something like Qudes-OS + Tor. If your workflow / usecase allows it, this should be a good step up for privacy. Your laptop seems beefy enough to handle the many VMs, and the install is easy enough imo.
Now we’re talking!
What should I do to use shared-memory communication from user-space on an immutable system?
This! And switching to DDG or others if TOR is needed.
This is exactly what I was looking for! Thanks for sharing!
Better UI consistency. It’s always really annoying when you have your nice dark theme and a bright white page pops out of nowhere and fry your eyes.
For ease on the eye, keep everything black on white, and turn down screen brightness if the environment is dark.