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.

>But as a software creator, it's up to you to determine what is best for your customers.

Absolutely zero large web properties do anything based on what's best for users. If this gains traction, Google will simply deny adsense payments for impressions from an "untrusted" page, and thus all the large players that show ads for revenue will immediately implement WEI without giving a single flying shit about the users, as they always have and always will.

Are you sure about that? I am quite optimistic, it's not the first dominant-position abusing crap from Google, they also tried to impose AMP and to rank sites without it at lower positions, but AMP was ultimately fined out of existence. I am all for regulations and fining google out of existence, but I am thinking that maybe this is another product that serves to make shareholders sleep well and will not really see any significant adoption

AMP is gone? Wow, good news is rare these days, so thank you very much for the update.