> GrapheneOS does not include any form of Play services and has no support for the OS using it. If a user installs Play services, the OS detects it and intercepts the attempts it makes to use privileged APIs and instead returns placeholder data.
Isn't that shipping an integration for a proprietary service?
How can you claim that we're the ones shipping proprietary service integrations when we ship an open source implementation, and you're the ones shipping an integration for the proprietary implementation.
I'm done here, there's no point arguing with you, you don't see reason.
> Not actually true. Do you claim that stuff like firmware cannot be shipped too?
It's the sole reason why there exists the concept of flashing gapps are installing other custom ROMs, and that cannot be supported without verified boot.
The other way is what you're doing, which is impressive, not questioning the code / implementation, just the way you're trying to present it here.
>How can you claim that we're the ones shipping proprietary service integrations when we ship an open source implementation, and you're the ones shipping an integration for the proprietary implementation.
Play Services is not integrated into GrapheneOS at all. It only has a few shims that, as strcat explained several times, return placeholder data. Play Services has no special permissions, and using it on GOS is the same as installing any other app.
microG is integrated into your OS. It's a partial reimplementation of proprietary Play Services.
That was for distributing Google apps, not for shipping firmware updates. You're making a false comparison.
As you could see if you had read strcat's comments and the documentation, GrapheneOS doesn't ship Play Services but only some compatibility shims, otherwise Play wouldn't know how to work. Users must manually install Play and associated apps.
> GrapheneOS does not include any form of Play services and has no support for the OS using it. If a user installs Play services, the OS detects it and intercepts the attempts it makes to use privileged APIs and instead returns placeholder data.
Isn't that shipping an integration for a proprietary service?
How can you claim that we're the ones shipping proprietary service integrations when we ship an open source implementation, and you're the ones shipping an integration for the proprietary implementation.
I'm done here, there's no point arguing with you, you don't see reason.
> Not actually true. Do you claim that stuff like firmware cannot be shipped too?
There is precedent here, https://phandroid.com/2009/09/25/cyanogen-gets-cd-from-googl...
It's the sole reason why there exists the concept of flashing gapps are installing other custom ROMs, and that cannot be supported without verified boot.
The other way is what you're doing, which is impressive, not questioning the code / implementation, just the way you're trying to present it here.