They updated the app to use the “Play Integrity[sic] API,” which actively blocks GOS.
“Does not meet” implies there is something reasonable GOS could do to “fix” it, which untrue and misleading. The malice on Google’s and Volkswagen’s part is an important part of the story.
Big companies have been trying to lock out custom ROMs for years, it’s a giant cat and mouse game. The integrity bullshit thing is just another move. And the fascists in charge have been stripping regulations which is allowing these companies to make such bold moves.
I think we’re on the same page here. I apologize for coming off so harsh.
That is until the official Motorola partnership happens with GoS and Motorola. It’s the missing piece for integrity verification as of current listed requirements on Google’s documentation. They needed to have first class support from a major OEM. Looking forward to seeing how Google will change that maliciously. This includes attestation.
The pessimist in me thinks the GrapheneOS Motorola partnership won’t happen, Google will put pressure on Motorola and make it fail. I really hope I’m wrong though.
That is until the official Motorola partnership happens with GoS and Motorola. It’s the missing piece for integrity verification as of current listed requirements on Google’s documentation. They needed to have first class support from a major OEM. Looking forward to seeing how Google will change that maliciously. This includes attestation.
Good point, I didn’t think about that. It will be very interesting to see what happens.
They updated the app to use the Play Integrity API, which GOS does not meet.
Not that it means anything, of course. GOS is far more secure than Google’s laughable excuse of a certification.
Far more secure for the user. Which infringes upon the supreme inalienable rights of corporations.
They updated the app to use the “Play Integrity[sic] API,” which actively blocks GOS.
“Does not meet” implies there is something reasonable GOS could do to “fix” it, which untrue and misleading. The malice on Google’s and Volkswagen’s part is an important part of the story.
Requiring a valid Play Integrity API response is a blanket enforcement on all custom ROMs, regardless of security measures.
This was not a targeted attack on Graphene. GOS users just tend to be more vocal and…paranoid.
“Does not meet” has more than one meaning. Don’t play dumb.
I didn’t say the attack was “targeted” only on GOS; you made that up yourself. But it is an attack, as opposed to something with a valid excuse.
Also: it’s only paranoia if they aren’t actually out to get you.
Big companies have been trying to lock out custom ROMs for years, it’s a giant cat and mouse game. The integrity bullshit thing is just another move. And the fascists in charge have been stripping regulations which is allowing these companies to make such bold moves.
I think we’re on the same page here. I apologize for coming off so harsh.
That is until the official Motorola partnership happens with GoS and Motorola. It’s the missing piece for integrity verification as of current listed requirements on Google’s documentation. They needed to have first class support from a major OEM. Looking forward to seeing how Google will change that maliciously. This includes attestation.
The pessimist in me thinks the GrapheneOS Motorola partnership won’t happen, Google will put pressure on Motorola and make it fail. I really hope I’m wrong though.
Good point, I didn’t think about that. It will be very interesting to see what happens.
It won’t they won’t meet all the requirements if the partner ship even happens.
Yeah it’s dubious at best. Daniel will probably try to torpedo it somehow.
Interesting indeed. I know I’ll be buying one pretty much no matter what as long as reasonably priced.
I’m definitely watching from a distance 😅