This CL moves the base::Feature from content_features.h to
a generated feature from runtime_enabled_features.json5.
This means that the base::Feature can be default-enabled
while the web API is co...
Web dev here. It enforces the original markup and code from a server to be the markup and code that the browser interprets and executes, preventing any post-loading modifications.
That sounds a bit dry, but the implications are huge. It means:
ad blockers won’t work (the main reason for Google’s ploy)
many, if not most, other browser extensions won’t work (eg.: accessibility, theming, anti-malware)
people are going to start running into a lot of scam ads that ad blockers would otherwise prevent
malicious websites will be able to operate with impunity since you cannot run security extensions to prevent them
web developers are going to be crippled for lack of debugging ability
These are just a few things off the top of my head. There are endless and very dangerous implications to WEI. This is very, very bad for the web and antithesis of how it’s supposed to be.
TBL is probably experiencing a sudden disturbance in the force.
Wouldn’t it be possible to create some kind of “post-browser” that takes input from the web browser and displays it after passing it through ad blockers and whatever else?
Such an abstraction, while unnecessary, should be possible, providing that Google doesn’t forcibly prevent access to the final markup that coalesces (ie.: view source and web dev tools)
Web dev here. It enforces the original markup and code from a server to be the markup and code that the browser interprets and executes, preventing any post-loading modifications.
That sounds a bit dry, but the implications are huge. It means:
These are just a few things off the top of my head. There are endless and very dangerous implications to WEI. This is very, very bad for the web and antithesis of how it’s supposed to be.
TBL is probably experiencing a sudden disturbance in the force.
Wouldn’t it be possible to create some kind of “post-browser” that takes input from the web browser and displays it after passing it through ad blockers and whatever else?
Such an abstraction, while unnecessary, should be possible, providing that Google doesn’t forcibly prevent access to the final markup that coalesces (ie.: view source and web dev tools)
The only acceptable browser would obviously be ones that restrict that access, how else are they going to force people to see all their ads?
Perhaps, but it’s not as simple as it sounds.
Most of the Web requires js to work. I don’t think the js will work without the DRM.
So the proxy would need to be running the js, and emulate your clicks and so on.