Category: Google|Jan 29, 2019 | Author: Admin

Chrome API Update Kills Ad Blockers Along With Numerous Other Extensions

Google has announced making some changes in their Chrome API that (in a way) threatens user privacy. As per its planned API update, it will restrict ad blockers. In fact, the upcoming Chrome API update will not only limit ad blockers but may also kill numerous other plugins and extensions.

Google has announced making some changes in their Chrome API that (in a way) threatens user privacy. As per its planned API update, it will restrict ad blockers. In fact, the upcoming Chrome API update will not only limit ad blockers but may also kill numerous other plugins and extensions.

 

Chrome API Update Cracking Down Ad Blockers
Last year, Google publicly shared its plan regarding some changes in the Chrome API.

 

This Chrome API update plan revealed changes in the Chrome Extensions platform that would kill ad blockers. Precisely, the changes referred to restricting various extensions’ capabilities. According to Google, the changes aim at providing better security, privacy, and performance.

 

These details are outlined in Google’s Manifest V3 document. It states

 

In Manifest V3, we will strive to limit the blocking version of webRequest, potentially removing blocking options from most events (making them observational only).  Content blockers should instead use declarativeNetRequest… The new declarativeNetRequest API will be used as the primary content-blocking API in extensions.

 

Google deems declarativeNetRequest API offers better privacy and performance.

While this seems pretty simple, Raymond Hill, the one behind uBlock Origin and uMatrix ad blockers, has raised concerns about this policy. He fears that the API update will eventually kill both uBO and uMatrix ad blockers. In addition, this modification also threatens other extensions.

 

Beside causing uBO and uMatrix to no longer be able to exist, it’s really concerning that the proposed declarativeNetRequest API will make it impossible to come up with new and novel filtering engine designs, as the declarativeNetRequest API is no more than the implementation of one specific filtering engine, and a rather limited one.

 

The Change May Reverse
It isn’t about Raymond Hills only, rather various developers have expressed similar concerns. Andrey Meshkov, the AdGuard developer, also endorsed Hill’s concerns. He said

 

The proposed change will be even more crippling to all ad blockers… there’s another serious change that needs attention.

The proposed change to hosts permissions (either using activeTab or requesting access on every new website) basically means that every time users navigate to a new website, nothing is blocked there. Ok, maybe something is blocked by declarative rules, but blocking web requests is just a tiny part of what ad blockers do.

 

Nonetheless, as revealed in a response to Hill’s bug report, Google may reverse these changes.

 

The webRequest API is not going to go away in its entirety.  It will be affected, but the exact changes are still in discussion.

This design is still in a draft state, and will likely change. Our goal is not to break extensions.  We are working with extension developers to strive to keep this breakage to a minimum, while still advancing the platform to enhance security, privacy, and performance for all users.

 

Take your time to comment on this article.

Comments: