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.
I’m super happy with the ThinkPad T-Series. Solid build quality, and the keyboard is magnitudes better than the MBP i had before.
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?
It really depends on your approach to learning things. If you’re looking for a systematic approach, I really like No Starch Press books for that sort of thing: How Linux Works or Your Linux Toolbox (for a more playful approach).
But in the end there’s really no substitute for installing Debian on bare metal and tinkering with it. I would really recommend Debian, because it’s the archetype of how Linux systems have been working for the last 30 years or so. Arguably, this is currently changing, but come to grips with Debian before you dabble in more modern approaches to system management.
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.
NixOS and its declarative approach irreversibly changed the way I think about system configuration and maintenance. Home manager and flakes are really important puzzle pieces in that as well.
The steam deck is an amazingly well thought-out Linux computer that just anybody can use intuitively.
From a UX standpoint, I love being able to remap keys on the system level with Interception Tools. (e.g. CapsLock is Esc if pressed and Ctrl if held on all my hardware for all users.)
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.
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.