And since you won’t be able to modify web pages, it will also mean the end of customization, either for looks (ie. DarkReader, Stylus), conveniance (ie. Tampermonkey) or accessibility.
The community feedback is… interesting to say the least.
And since you won’t be able to modify web pages, it will also mean the end of customization, either for looks (ie. DarkReader, Stylus), conveniance (ie. Tampermonkey) or accessibility.
The community feedback is… interesting to say the least.
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 <doesntRenderAdOnClientDevice>. 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?
The point of the proposal is to allow servers to be sure the software (ie browser) running on the device is what it says it is, and take away the ability to spoof what browser you’re running (which is currently fairly trivial).
So if someone makes a browser that doesn’t allow adblockers and always shows ads, the server can do things like only serve content to that browser.
Imho, without hardware support they won’t be able to keep up against the hackers. In the end it’s software and it’s running on hardware outside of the control of the server. There are millions of possible attacks to break/bypass this.