Unpacking Google’s Web Environment Integrity specification

    > Can we just refuse to implement it?
    > Unfortunately, it’s not that simple this time. Any browser choosing not to implement this would not be trusted and any website choosing to use this API could therefore reject users from those browsers. Google also has ways to drive adoptions by websites themselves.

This is true of any contentious browser feature. Choosing not to implement it means your users will sometimes be presented with a worse UX if a website's developers decide to require that feature.

But as a software creator, it's up to you to determine what is best for your customers. If your only hope of not going along with this is having the EU come in and slapping Google's wrist, I'm concerned that you aren't willing to take a hard stance on your own.

Well hold on. The problem with attestation is you're damned if you do and damned if you don't.

If you use a browser which supports attestation you will be denied service by companies who disapprove of what you run on your computer.

If you don't use a browser which supports attestation you will be denied service by companies who disapprove of what you run on your computer.

So everyone loses. If this goes live everyone in the world loses.

It is an utterly heinous proposal. It is perhaps the worst thing Google has ever produced. I use Firefox and will never use any browser that implements attestation, even if I have to stop using most of the WWW one day.

But unfortunately individual action is not going to be enough here, because no matter what you do, you lose.