People are currently reading this guide.
 |
| Image Credits: ZenSEM |
A comment from a Google engineer threw new fuel to block Google Chrome ads.
In January, Google started a whirlwind by announcing its intention to revoke the webRequest API, which is used by ad blockers to ensure that the browser does not download advertisements.
Google's replacement should be far more efficient, offering a rule-based system that only stores 30,000 rules, when many block extensions use more than 75,000.
Google claims this limit for performance reasons, even though end users and developers see that advertisements and followers slow down more web pages. In its response, Google said it could increase the number of rules permitted, based on their own performance tests.
Today, Google has actually revealed that it does not denounce the webRequest API, but only blocks elements (clearly stating that they are targeting ad blockers), but also reveals that Google Suite business customers will not be overloaded.
Simeon Vincent, developer advisor for Chrome extensions on Google, said on Google Chrome for extension developers:
Chrome has revoked the webRequest API blocking functionality in Manifest V3, and not the entire webRequest API (although blocking is still available for enterprise implementation).
This disclosure makes experts note that blocking effective advertising is an existential threat for Google, which still largely depends on revenue from display ads.
Raymond Hill, the main developer of uBlock Origin, noted a little:
Google's core business is not compatible with blocking non-blocked content. Now that Chrome products have achieved significant market share, concerns about blocking content, as noted in 10K archiving, are being handled.
At SEC 10-K, Google recently noted:
New and existing technologies could affect our ability to customize ads and/or could block ads online, which would harm our business.Source: SEC
The news revealed a conflict of interest between Google that has content and a browser that presents universal content (browsers) and uses one to support another.
References:
Via 9to5Google