Google has abandoned the “Web Environment Integrity” API that was supposed to allow websites to only allow approved and verified browser environments. The plan would allow websites to reject browser or even OS modifications that were “unattested” for the purpose of supposedly stopping bots, piracy, ad-blocking, and other activity Google deemed to be malicious. However, critics of the plan called it corrupt tyranny in which Google flexes it’s muscles to control the entire internet.
The plan was rejected from Firefox and Brave browsers, and could potentially shut Linux users out of many websites as there would be no telemetry company to “verify” the operating system was not modified. Further, some said it was an outright attempt by Google to force people to submit to the API even if they didn’t want to use Chrome browser.
Now this horrible tyrannical plan from Google was abandoned after severe “community backlash”, however it could see a limited version for Android Chrome only when embedded into apps themselves. Some privacy advocates criticize this move as merely a trial testing ground, where they can prove to websites and services that the concept works and then try to push it to a larger audience. These critics call for a boycott of the apps that use this functionality.
We can only hope these rotten Google executives can abandon their plans for world domination and the submission of all knowledge to pass through their ad tracking software.
https://simplifiedprivacy.com/google-abandons-web-environment-integrity/
I don’t believe them. They will try to do it again, slightly modified, under a different name, but they WILL try to introduce it again.
And for round 2 they’ll try to be sneakier about it
No. That’s round 3. Round 2 is already announced - they are ‘restricting’ environment integrity to multimedia on Android webview. Of course, what they don’t say is that the feature is going to be developed and tested outside the view of the general public - since this doesn’t need to go through a public standardization like web specifications. Once they get that perfected, they will silently expand its scope outside webview and gradually into browsers with a new name. That’s round 3.