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
Replying to
Once we have our own builds of a few apps like Element in a first party repository, we'll make it easy to install them as recommended apps in the initial setup.
It really doesn't make sense to hard-wire this into the OS. For one thing, it makes it hard to move away from it.
1
1
13
These apps could have their development stall or better options could appear. The app recommendations in the initial setup wizard would be adjusted over time.
Apps hard-wired into the OS are a major hassle to remove. Need to add a warning and get users off it before removal.
1
1
12
When we're developing the app, we know that development isn't going to go completely off the rails in a way that's not focused on privacy and security.
Some things do need to be built into the OS like the keyboard. Plan to replace some of them but we'll be very cautious with it.
1
1
12
Replying to
What are the current major candidates? May I ask? Matrix or Briar or something else from scratch?
1
Replying to
well, what about hosting your own xmpp server, making sure no metadata is collected by the server settings? just add an disclaimer that metadata collection COULD happen by you. also its FOSS. xmpp with omemo is perfect.
1