I had this same question since seeing the post about the Fossify phone app. For phone, calendar, contacts, things like those, i dont see what value the official google apps have (other than syncing to your account, but i can manage that myself). For Messages from Google, tho, there is something they provide in the RCS, if only because they block others from implementing.
So, using Fossify Message, for example, sacrifices something of some actual value here…
Beside concrete suggestions, I would suggest having a look at the applications you use. (Decide whether you actually use and need them first.) Search for the application on AlternativeTo or similar sites and look for a FLOSS alternative there. And also search the internet for general FLOSS replacements for the use-cases of the applications you use. No need to rush anything. Even replacing one application a week is good progress.
Damn, thanks for letting me know. I’ve been using the Simple suite for years and even bought some of them because I wanted to reward the developer. I’m saddened by the news of the acquisition. I’ll swap them with the new fork.
I’d suggest trying FairEmail on your phone, email.faircode.eu, before trying to set up an email server.
I would ask if you have good knowledge of IMAP. That allows access to a unified inbox from several devices and you don’t have to own the server. It is far preferable to webmail for me.
I host my own email server and use many devices all over IMAP. If you need a server, nixos-mailserver is my recommendation. You could then try Roundcube on top but I bet you will use IMAP instead before you get there.
Prompt after a crash, include verbatim data sent, send only this time or opt in for automatic reporting, IMHO best practice as a user who respects the need for valueable analytics
As an OSS user, and developper, OPT-OUT is a shitty practice. It should be opt-in to users who face crashes issues if they want to share that data (they care enough to provide their info to the dev to fix it). I know this makes users sound entitled, but otherwise the “opt-out” permission will be exploited by someone which will make users even more paranoid about OSS apps.
It takes years to build a good reputation in OSS, and only one dumb thing (like opt-out of personal data) to ruin it.
(Yes, IPs may be considered personal data in that they can be used to identify individuals, and so subject to the GDPR and, potentially, the very high fines associated with that. Unless you’re evil, don’t collect any personal or identifying data unless you absolutely have to, and very triple sure the user knows what you’re sending and why)
This doesn’t really have anything to do with open source software. It’s more of a privacy topic. You can harvest as much data as you want and still be GPL.
opensource
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.