Your community is so new that you might as well look to the few users who have contributed so far (OpenStars, Tux, etc). Clearly, they've identified with the group and may be interested. I would check out their comment history just to ensure their general behaviour aligns with your expectations, and go from there.
thayerw
Great shots, I love the low contrast moody tones. Definitely adding these to the mix!
Noooo! Ugh, that's so disheartening to hear but I can't fault imsodin for his reasons. I sincerely hope that someone steps up to the plate, even if only for the F-Droid releases.
For anyone else interested, the discussion is taking place here:
https://forum.syncthing.net/t/discontinuing-syncthing-android/23002/7
I can only speak for myself, but I would never trust opaque, proprietary software to manage my credentials, especially in a networked environment. For me, that's a total showstopper.
I've never had need to use Bitwarden or Vaultwarden as I've always been happy with KeePass, but this news would definitely have me choosing an alternative.
For what it's worth, I only ever had sync issues when sharing a database between devices with transient connectivity. Once I added an always-on instance of Syncthing into the mix, collisions were a thing of the past.
We've been using KeePass trouble-free for many years now, sharing a single database across more than 6 devices, with frequent use and modification.
It seems to be isolated to GrapheneOS users, but I do think it's something that Voyager is doing since it isn't happening anywhere else. Either there's an issue with the reply function, or the way it's being called in certain circumstances. Anecdotally, I recall that it started after a GOS update, and Voyager hadn't been updated at the time. Maybe something changed in GOS' Vanadium/WebView which has essentially broken Voyager.
If you want free tier with good privacy practices, Proton is going to be the best option.
I have several paid webhost accounts already, so I just use those for email. Any important messages (which are increasingly rare) are saved to PDF and stored offline (business/tax/medical info, etc.), and the rest is purged once read/sent.
Despite some of the comments here, I suggest that you don't overthink it; just buy an APC Back-UPS 600VA and be done with it. You have relatively low power requirements. The UPS will provide some surge protection (490J), several minutes of uptime, and a USB connection for automated shutdown.
The 600VA unit is less than $100 USD and replacement batteries are about half that. I've been using several of this same model for years without issue and we have many brown/blackouts being in a rural BC community. The batteries have lasted me 4-5 years.
You can always plan for something more significant down the road, if your hardware or needs change, but this should do fine in the interim.
Lots of great responses here already. In terms of simplicity and ease of maintenance, Hugo is going to be the best solution with its single binary, built-in features, and ease of setup/use.
I don't even use Kmail, but kudos for sharing a quick fix to something that would drive me bonkers!
I was a happy Gedit user for many years, but switched to the new GNOME Text Editor a couple years ago and haven't looked back. It's perfect for quickly reading text files and writing simple markdown notes. Anything else and I fire up Vim or VSCodium. Still, I'm glad to see it getting some love and I'm sure there are plenty of diehard fans.