Google Chrome users will soon have no use for their ad-block extensions. According to Raymond Hunt, the developer of the extension uBlock Origin, Google might no longer support the webRequest API, also affecting all API developers that created ad-blocks for the platform. The only ad-block that will not be affected is the one which Google reportedly pays to whitelist its ads – Adblock Plus.
Adblock Plus is a popular ad-block extension that lets companies like Google pay to whitelist “non-obtrusive” ads. This extension doesn’t rely on the webRequest API, but on the DeclarativeNetRequest API – which works differently from the other, allowing the web browser more control over what it can block.
The webRequest API will have the information flow through the extension and lets it select what there is to show on a webpage. On the other hand, the DeclarativeNetRequest API notifies Google about removing ads, and the browser decides what to keep.
Increased Speed and Security or a Way To Push More Ads from Google?
Seeing that the new API works efficiently on Chrome and doesn’t need extensions to process data before being sent, the company decided to no longer support the old one. Moreover, they explain that the new API is also more secure, as the request no longer passes through an extension.
But what about these changes? Is Google going to be too much in control with this API and if yes, will it no longer allow other ad-block systems to block ads? Will extensions be allowed and adjust to these changes?
The only users that won’t be bothered by the change are those accustomed with Adblock Plus
We will see soon enough if this change brings a faster and more secure Chrome or a tool for Google Ads.
Nora Reynolds is a major in biology and a minor in Biological Basis of Behavior, writing about science in general. She also likes to try new gadgets and sports about the AI new era.
