Post #4146977

2026-07-27 19:45 UTC

@tranquil_cassowary@infosec.exchange no, it's grapheneOS's fault. they decided to base off of android and this limitation was already known. in fact, it's even more their fault because by basing off of android, they help keep the whole ecosystem a monoculture. i know the arguments for and against this decision already. it's still their fault. compatibility won out over user privacy and freedom. android is not an open operating system, even if lots of the source is published.

Replies (1)

@tranquil_cassowary@infosec.exchange 2026-07-27 21:05

@tyzbit@toot.now Play Integrity didn't exist yet when they started the GrapheneOS project in 2014. What alternative was and is there to basing yourself on Android that is equally secure and private? AOSP is a FOSS project and was made to be an open project and the ecosystem and Google as well benefited a lot from it being open because it made the OS attractive to OEMs. Why are you blaming @GrapheneOS@grapheneos.social for being the victim of Google increasing its anticompetitive actions? What Google does is likely illegal in the context of anti-trust laws. Also most things are compatible still and GrapheneOS and the community have been able to convince some developers to allow GrapheneOS after first blocking it. GrapheneOS hasn't sacrificed privacy for compatibility. It offers various exploit protection settings to make the trade-off between compatibility and privacy as you see fit. Your comment is also very dismissive of the privacy benefits of the compatibility for Google Mobile Services that GrapheneOS has created.

Open ##4146976