The way I understand it, ufw is a frontend for iptables. So no.

This is a helpful blogpost on disabling input devices in Wayland

You don’t. Even if you’re happy to support the developers of the software you use (which is great!), I think it makes more sense to download and give it the spin first, then donate later.

Where indexing and searching mails is concerned, notmuch is the best I’ve seen. Do note that this is not an e-mail client, it only indexes, tags and searches (following the “UNIX philosophy” of doing one job well).

I personally use it with neomutt as a mail user agent, which is almost certainly not what you want. Notmuch supports other clients but they’re all pretty arcane.

So this is not a recommendation, just a glimpse into advanced e-mail setups I guess.

Nice, I didn’t know about the all selector

No need for external programs:

for_window [class="^.*"] inhibit_idle fullscreen
for_window [app_id="^.*"] inhibit_idle fullscreen 

I don’t think downgrading the curl library is promising here. curlftpfs seems to be unmaintained. I recommend looking for alternatives or alternative workflows.

Fixed in curl, but not in a curlftpfs, apparently. Look at the comments on the accepted answer.

Seems to be a known bug: https://github.com/curl/curl/discussions/14299

Error setting curl:

That doesn’t seem like a complete error message to me. Is there any more information? Maybe with the -d (debug) flag?

Same! This works really well.

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.)