Well, having a domain is basically documenting your IP publicly. It’s not that risky.

Regarding snapshots, I use a setup, where at the root of the btrfs partition I have the subvolumes “rootfs”, “home”, and a directory “snapshots”. I can boot into a snapshot by changing the mount options for the rootfs in the kernel command line, e.g.setting subvol=snapshots/rootfs-yyyy-mm-dd.

The only difference between a snapshot and a regular subvolume is that snapshots are readonly by default, you can keep a writable copy of a snapshot beside it for recovery purposes, if you need it. As long as nothing is written in it, it shouldn’t use any significant extra space.

I know that, but that does not give apps root access. Unless you mean something else by root access than being run with root privileges

But Shift+insert currently pastes the primary selection, not the copy-paste clipboard. So it doesn’t do the same as Ctrl+V.

Well, the article proposes to use dedicated copy and paste keys. If you don’t have an insert key, you probably don’t have those either.

And best of all, you get an OS that is secure, which traditional Linux distros aren’t due to every app having root access by default.

What? Which distro runs everything as root by default?

Sunless Sea, Sunless Skies and Stardew Valley have native Linux Support. For Stardew, even the third modding API works flawlessly for me.

For the other ones, they are reported to run well on protondb.com, which is a good place to check Linux support (not only for Steam games). The reports there usually also list, which proton version works well.

Manual firmware updates

As someone who’s work laptop no longer has Wi-Fi since the automatic firmware update, I like my updates to be manual.

Try eject /dev/sr0, that should be your disk drive if it is attached via SATA or USB. /dev/cdrom is usually just a symlink.

I don’t use GNOME, but from what I’ve read (and from experience with other software that has extensions) they often break when GNOME updates.

on my gaming PC, it never used the GPU.

In my experience, that is usually a problem with the GPU OpenCL drivers. Sadly, the Mesa OpenCL implementation didn’t include image support when I last checked (you can check with clinfo | grep "Image support"). For AMD cards you need to have either the “pro” driver or ROCM installed, both aren’t packaged by all distros. Similar with Intel, don’t know about Nvidia, but I’m sure if it works, it’s only with the proprietary driver.

I ended up installing darktable in an arch distrobox container, as arch has ROCM packages (in AUR) and ever since GPU acceleration is working fine.

This is mostly what I use too. Additionally, on images with high ISO I usually add the profiled denoise module, often without changing the default values. If the image has a lot of noise, I sometimes use the preset that only reduces chroma noise (so the image stays grainy, but without the color mismatches)