you are being deliberately deceptive here and I hate people like that
To be fair, you have no idea if they are being deceptive. They might simply not be aware that GrapheneOS chose not to pay to get certified. I certainly didn’t know that, and I’m not at all certain that Google would certify them if they chose to pay. Do you have a source for that?
Any developer can go here to start the process for GMS certification. If the Graphene devs didn’t know this, then they are fucking stupid, which i know they are not. Their TOS provides you the answers:
GMS is only available through a licence with Google and delivers a holistic set of popular apps and cloud-based services.
And I think the costs vary depending on how much bandwidth traffic you will be bringing Google to serve the certified content. Also, they allow you to certify non-Android OSes (such as Tizen and etc).
That’s a very funny post to read. In summary they are demanding Google comply with their own standards they designed. It’s definitely two children yelling “No, you!” at each other.
I like Graphenes standards better, but it looks like Google is sticking with Play Integrity API over hardware-key attestation because it’s less insane to force end users to rely on costly solutions and more compatible with different commercial vendors (looks like some Certificate Authority vendors are effected).
To be fair, you have no idea if they are being deceptive. They might simply not be aware that GrapheneOS chose not to pay to get certified. I certainly didn’t know that, and I’m not at all certain that Google would certify them if they chose to pay. Do you have a source for that?
Any developer can go here to start the process for GMS certification. If the Graphene devs didn’t know this, then they are fucking stupid, which i know they are not. Their TOS provides you the answers:
And I think the costs vary depending on how much bandwidth traffic you will be bringing Google to serve the certified content. Also, they allow you to certify non-Android OSes (such as Tizen and etc).
According to this post, it’s not that they don’t want to, it’s that GrapheneOS can’t be certified:
https://discuss.grapheneos.org/d/475-wallet-google-pay/9
That post implies that there is something Google won’t do which prevents them from certifying, which supports what the OP was saying.
That’s a very funny post to read. In summary they are demanding Google comply with their own standards they designed. It’s definitely two children yelling “No, you!” at each other.
I like Graphenes standards better, but it looks like Google is sticking with Play Integrity API over hardware-key attestation because it’s less insane to force end users to rely on costly solutions and more compatible with different commercial vendors (looks like some Certificate Authority vendors are effected).