A federated or fully peer-to-peer messaging app is the only kind we would consider integrating into GrapheneOS.
We definitely won't integrate support for proprietary services like Signal or WhatsApp. Signal supposedly has open source server code, but doesn't publish all of it.
Conversation
Not really familiar with it. Element leaks a lot of metadata but you can at least make an account anonymously and it has default E2EE via a solid protocol for non-public chats. That looks like a project aiming to solve the issue of leaking all that important metadata to servers.
1
4
Since our official chat rooms are on Matrix, we probably are going to package Element in our planned first-party repository and make it one of the dozen recommended apps in the planned setup wizard page for that. Prefer recommending Element over Signal at this point at least.
Matrix really does leak a TON of metadata though. I still think it's better for people to leak that primarily to their chosen homeserver than giving their contacts, etc. to the central Signal server at this point. I'd still say Signal is the best easy E2EE recommendation.
1
5
Getting fed up with Signal's bullshit and I'm increasingly not wanting to recommend it to anyone. It really is the easiest way to onboard people who are totally non-technical and don't want to invest time beyond simply installing an app and getting started, no making account, etc
1
4
Show replies

