I doubt it's the engineers.

Well time learn how to jailbreak web pages now too

Also fun to read this (by Google employee): https://blog.yoav.ws/posts/web_platform_change_you_do_not_like/ I literally snacked popcorn.

If they overcome / disable ad blocking, they will lose browser market share - and people don't design websites for marginal browsers with exotic features.

Can someone explain how the server is going to know whether or not the client browser is showing the ad? A stealthy browser would say, "hey yeah send that ad so I can render it to the user" and the server says, "yeah ok" and then . How is the server going to know whether the ad is displayed or not? Don't current gen adblockers not even retrieve the asset? If the asset was retrieved but not displayed, how (if even) can this be monitored?

Found this lol

I will personally stay on the internet instead of what essentially amounts to google intranet.

As they say, it's for your security and convenience! Honestly!

Well, I guess I'll stop using the internet. F

I swear I was just thinking of this today as the next step in this shitshow

This shouldn't be allowed no matter what

you misunderstood it tbh.
it's supposed to be used as a way to skip bot verification if the requests are signed by a drm system which includes your unique id (coming from google account or google play id), and one of the goals of the actual proposal is keeping existing extension working AND keeping web pages working without drm.
of course i don't want any drm in my browser, but it's kinda already there anyway...
it will likely make the experience worse for non-drm users because they will get hit by more advanced and sensitive bot verification systems or rate limits which is kinda bad but not the end of the world.
y'all are just overreacting and spreading pure bullshit.
it's not even supposed to be used to verify DOM elements, just that the user is using an official Chrome/Chromium browser, and is not automated.
basically it's just SafetyNet.
it will not kill js addons.