Google Chrome: "Our goal has never been to break the blockage of content"

Google has returned to its Manifest V3 which has been the subject of so much ink confirming its desire not to go against advertising blockers. The interest is to make the web better without destroying the work of many developers.
Image credit: WhoTracksMe
At the beginning of the year, the release of version 3 of the Google Chrome Manifesto had provoked an outcry from some developers of extensions to block advertisements during browsing. In a message to his community, Google confirmed Friday, February 15 that his intention was not to harm the extensions and that changes will be made to his manifesto.
The negative impact on the user experience
In its V3, Google explains that some third-party software may have "a negative impact on the user experience" and therefore proposed to correct this "the restriction of blocking capabilities [des requêtes HTTP] the webRequest API. " A point that would have prevented some extensions like uBlock Origin from working properly.
To this, Cliqz, owner of the Ghostery extension, has published a study on the impact of ad blockers on performance based on the most popular blockers, namely AdBlock Plus, uBlock Origin, Brave, DuckDuckGo and well sure Ghostery. The study shows that aside from DuckDuckGo, the median time allowed for blocking a query is less than millisecond:

This study aims to demonstrate that the impact of advertising blockers is not so negative as that on the user experience.
Google listening
Google has therefore listened to the many remarks and said that "the goal is not, and never was, to prevent or break the blockage of content," but to modernize the platform. In addition, Google recalls that the webRequest API will not be removed (even if strongly limited) and that a new API (declarativeNetRequest) has been implemented in order to replace its features.
If this is still considered insufficient by the developers of ad blockers, Google recalls that this V3 Manifesto is not yet finalized and that this API is still under development, which could allow it to perfectly fulfill its role in the end.
The V2 still relevant
If this V3 of the manifest is in development, the V2 still has some time ahead. Not only is it still relevant as long as the V3 is not finalized, but it will also be supported after the V3 has been deployed until the full migration is done, which will allow developers to bring their feedback. work on a new version of their extensions as needed.

Laisser un commentaire

Votre adresse de messagerie ne sera pas publiée. Les champs obligatoires sont indiqués avec *