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
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
This Tweet was deleted by the Tweet author. Learn more
This Tweet was deleted by the Tweet author. Learn more
github.com/florisboard/fl has to be implemented or users with a passphrase can't do the first unlock without AOSP keyboard still enabled. It's why we turned off disabling AOSP keyboard via Settings GUI. It's a common mistake people make otherwise.
1
1
I commented there explaining to them what they have to do. We could get it done ourselves but we'd need to find someone to pay to do that. We'd also want at least a quick audit of all the IPC APIs it exposes and other attack surface to make sure there aren't any blatant issues.
1
1
> patrickgold changed the title Enable keyboard at startup. Enable keyboard at startup (Direct boot mode) 9 days ago
Can see they know what they have to do now.