Just want to point out that, while it’s a mess in practice, there is a correct place for these files and the problem is that many applications ignore it. Configuration files should be written to an aptly named folder in ~/.config/ (or more precisely, in $XDG_CONFIG_HOME which is set to ~/.config/ in most systems). ~/.local/share/ (or $XDG_DATA_HOME, respectively) is for user data, which is different from config.

Not exactly what you are looking for, but modern shells like fish or zsh (probably?) are good at suggesting completions from history. fzf is another great tool for that. Both are super useful for remembering and repeating commands.

Snapper assumes that your system is “formatted with btrfs or some other snapper compatible filesystem”. I’m pretty sure that this means that that your root directory is mounted from a btrfs subvolume.

So all you need to do is setup btrfs at install time and then configure Snapper. You should consider mounting /home from its own subvolume. That way you can roll back the system but keep all your files.

There are a lot of other things to consider when setting up btrfs, so make sure you read the docs. (A lot of the config can changed at a later point.)

Revolution is a monad

That depends on your threat model. It’s a useful strategy to hide your traffic from your local network admin (e.g. at the workplace) and your ISP, but it’s a bad strategy for hiding your identity from the sites you’re visiting.

I’m sure you’re a great couple but if your concern is future-proofness consider separate domains.

Privacy is a trade-off against convenience, and there is no perfect privacy.

VPNs are a mediocre privacy tool, because they presuppose trust in the VPN provider. Tor is flawed because it is open to correlation attacks.

There are low-hanging fruit that everybody should be using like sensible cookie policies, HTTPS-only mode, and DNS over HTTPS.

If you are looking for a solution on the far end of privacy/inconvenience you could look into I2P and use that situationally.

Good clarification and advice.

There are so many considerations when “repairing” an installation, that I would definitely suggest a reinstall here.

Yes, for data recovery you really just need something to access the drives.

If you have backups, reinstall.

If you don’t, boot a “live CD” USB stick and make a backup, then reinstall.

Then think about how this happened and how to avoid it in the future:

I tried updating Kubuntu to the newest version, and it got screwed up the first time,

In either case, its a quick copy/paste on my part, so /shrug.

I was thinking “okay this somewhat unconventional but whatever” until I read this. Use greasemonkey or something for the love of Christ!

Fedora plus rpm-fusion (rather than stock Fedora). I agree that this works really well for beginners, but the extra step of adding rpm-fusion holds some potential for frustration.

Agreed, but use sway instead of i3 for Wayland support.

Pretty sure codeberg.org uses forgejo under the hood.

Another very solid option for self hosting is just adding a git user to a server with git installed, initiate bare repositories there, then talk to them with [email protected]:repo-name

Should really be prefaced by: Don’t bring your phone. Write the phone number you plan to call if arrested on your lower arm in sharpie. If for some reason you have to bring your phone, read the following.