It looks like Google, now that an anemic Firefox is the last other browser standing, will cripple ad blockers in Chrome.
What a surprise, an advertising company who dominates the browser market is crippling ad blockers:
Google engineers have proposed changes to the open-source Chromium browser that will break content-blocking extensions, including ad blockers.
If the overhaul goes ahead, Adblock Plus and similar plugins that rely on basic filtering will, with some tweaks, still be able to function to some degree, unlike more ambitious extensions, such as uBlock Origin, which will be hit hard. The drafted changes will limit the capabilities available to extension developers, ostensibly for the sake of speed and safety. Chromium forms the central core of Google Chrome, and, soon, Microsoft Edge.
In a note posted Tuesday to the Chromium bug tracker, Raymond Hill, the developer behind uBlock Origin and uMatrix, said the changes contemplated by the Manifest v3 proposal will ruin his ad and content blocking extensions, and take control of content away from users.
………
“If this (quite limited) declarativeNetRequest API ends up being the only way content blockers can accomplish their duty, this essentially means that two content blockers I have maintained for years, uBlock Origin and uMatrix, can no longer exist,” said Hill.
The proposed changes will diminish the effectiveness of content blocking and ad blocking extensions, though they won’t entirely eliminate all ad blocking. The basic filtering mechanism supported by Adblock Plus should still be available. But uBlock Origin and uMatrix offer far more extensive controls, without trying to placate publishers through ad whitelisting.
“Users should have increased control over their extensions,” the design document says. “A user should be able to determine what information is available to an extension, and be able to control that privilege.”
But one way Google would like to achieve these goals involves replacing the webRequest API with a new one, declarativeNetRequest.
The webRequest API allows browser extensions, like uBlock Origin, to intercept network requests, so they can be blocked, modified, or redirected. This can cause delays in web page loading because Chrome has to wait for the extension. In the future, webRequest will only be able to read network requests, not modify them.
The declarativeNetRequest allows Chrome (rather than the extension itself) to decide how to handle network requests, thereby removing a possible source of bottlenecks and a potentially useful mechanism for changing browser behavior.
“The declarativeNetRequest API provides better privacy to users because extensions can’t actually read the network requests made on the user’s behalf,” Google’s API documentation explains.
………
“If this (quite limited) declarativeNetRequest API ends up being the only way content blockers can accomplish their duty, this essentially means that two content blockers I have maintained for years, uBlock Origin and uMatrix, can no longer exist,” said Hill.
The proposed changes will diminish the effectiveness of content blocking and ad blocking extensions, though they won’t entirely eliminate all ad blocking. The basic filtering mechanism supported by Adblock Plus should still be available. But uBlock Origin and uMatrix offer far more extensive controls, without trying to placate publishers through ad whitelisting.
………
Hill observes that several other capabilities will no longer be available under the new API, including blocking media elements larger than a specified size, disable JavaScript execution by injecting Content-Security-Policy directives, and removing the outgoing Cookie headers
This means that it is almost certain that NoScript, for example, whose security bona fides are such that it is distributed with the TOR browser, will never work effectively on Chromium based browsers.
This does not help user privacy or security, it’s just Google being evil, again.