They continued harvesting data from users after the users explicitly disabled an option to shut that off. And for that, they owe $4 a person. When are we going to starting fining these companies properly? How about a thousand dollars a person for an infraction like this? Maybe a $98 billion fine might get them to start caring.

a transactional SMTP provider, which is almost certainly selling all outgoing email contents for AI training at least if not even more nefarious things.

That’s a big assumption, and that kind of behavior is specifically prohibited in the privacy policy of most, if not all SMTP relay providers, as well as GDPR regulations. If you think they’re violating their own privacy policy and government regulations and doing it anyway, there’s no reason to think Proton isn’t as well, or any other email provider, so that’s kind of a non-starter argument IMO. Plus this only applies to outgoing emails, not incoming. I don’t know about you, but I send about 5-10 outgoing emails a year, there’s not much to be gleaned there. Incoming is what you’d want to protect more than anything.

There’s really no viable way to run your own email server with actual delivery anymore

SMTP relays make IP reputation a complete non-issue. As long as you aren’t sending hundreds of emails a day, there are multiple free options (free tier, subsidized by paying corporate customers who send a lot of emails).

I’ll probably just install .1 and have a play then reinstall .2 from fresh and transfer my data.

There’s no need for that. X.1 -> X.2 is a minor upgrade, there’s no reason to wipe and reinstall for it.

All valid points. The compose setup is nasty, and OIDC definitely needs a major overhaul for sure. I’m hoping those are two issues they address in the near future. I can’t speak to the Android app as I use iOS, I don’t have any complains about that version of their app.

I use OpenCloud with Collabora

OliveTin, gives you a clean web UI for pre-defined shell scripts, with a dynamically reloadable YAML configuration.

There are a ton of things you could use it for, but I use it for container and system updates. A pre-processor runs on a schedule and collects a list of all containers and systems on my network that have available updates, and generates the OliveTin YAML config with a button for each. Loading up the OliveTin webUI in a browser and clicking the corresponding button installs the update and cycles the container or reboots the host as needed. It makes it trivially easy to see which systems need updating at a glance, and to apply those updates from any machine on my network with a web browser, including my phone or tablet.