Claws-Mail is still alive and well and works great. Lots of plugins, you can write your own post processing actions, custom powerful filters, customizable interface etc.

desec.io

If you don’t already know the benefits it’s unlikely it solves a problem you have.

Even among its users many are using it because it’s cool rather than because they actually need it.

It’s a declarative system, meaning you can describe how it should be setup (using a magic strings you have to look up online) and then it “sets up itself” according to the description.

It’s normally something you’d use for mass and/or repetitive deployments.

It’s usefulness for a single system is debatable, considering you can achieve very close to 100% of “reproducibility” anyway by copying /home and /etc and fetching a copy of the package list.

Where the prescriptive approach is supposed to help is when you attempt to reproduce the system a long time later, after things like config files and packages have changed. But it doesn’t help with /home, it hasn’t been tested over long intervals, and in fact nobody guarantees long term compatibility for Nix state.

If someone gets access they can delete your keys, or set up something that can intercept your keys in other ways.

The security of data at rest is just one piece of the puzzle. In many systems the access to the data is considered much more important than whether the data itself is encrypted in one particular scenario.

Now replace “signal” in your comment with “ssh” and think it over.

If any part of the data gets corrupted you lose the whole thing. Recovery tools can’t work with partially corrupted encrypted data.

You. Don’t. Store. Secrets. In. Plaintext.

SSH stores the secret keys in plaintext too. In a home dir accessible only by the owning user.

I won’t speak about Windows but on Linux and other Unix systems the presumption is that if your home dir is compromised you’re fucked anyway. Effort should be spent on actually protecting access to the home personal files not on security theater.

Oh no, tell that to SSH.

The AUR is basically just a script that describes best case scenario for building something under Arch. They don’t have any specific quality rules they have to meet.

It’s super easy to make and publish an AUR script compared to a regular distro package (including Arch packages).

The ads are added in the app. If you cast, the Chromecast can’t add apps (yet) so they’d have to make ad streams instead, and switch between the streams show-ad-show which would take several seconds of loading screen each way and so on. Which is a level of fuckery even they shied away from.

TLDR they can’t (easily) show ads during casting.