> I expect that it will initially not use it
replyit's boiling the frog method. Moving too fast means backlash, but a slow, step by step transition where each step seems reasonable, but ultimately end up with a locked down device, is how they aim to achieve it. And people would be too lazy to complain until the last few steps, by which time it would be too late.
FWIW, “boiling the frog” is the example of false reasoning about slippery slopes (the frog in actuality always left)
replyYour larger point still stands though of normalizing changing expectations by slow degrees
Good metaphor. On the one hand, Google increasingly cooperates and makes deals with militaries and governments. On the other hand, it increasingly locks down its customers and eliminates their privacy and freedoms.
replyGoogle has just about got the pot boiling. They win, we lose.
>that implies that a "certified Android" device capable of Play Integrity attestation is required
replyNo, it doesn't. It implies that the app for handling the deeplink lives within GMS as opposed to needing to manually install a separate app like you do on iOS. GMS does not have a hard dependency on device integrity APIs being supported.
They said "capable of Play Integrity attestation". It's a weasel statement. If you have GMS, you're capable of performing PIA attestation, you just might fail. So it's strictly true, but doesn't tell us anything about whether it requires PIA.
reply