It turns out that Chrome's 'ad blocking plan' is still in progress


by

Deepanker Verma · Photography

In January 2019, it became clear that Google was trying to convert the API with the goal of limiting the ad block extension. This has been a big backlash from users and developers of extensions, but Google does not withdraw its plans and is pushing for feature implementations.

Manifest V3: Web Request Changes-Google Groups
https://groups.google.com/a/chromium.org/forum/m/#!msg/chromium-extensions/veJy9uAwS00/9iKaX5giAQAJ

Chrome to limit full ad blocking extensions to enterprise users-9to5 Google
https://9to5google.com/2019/05/29/chrome-ad-blocking-enterprise-manifest-v3/

Google still plans to kill Chrome's existing adblock APIs
https://www.androidpolice.com/2019/05/29/google-still-plans-to-kill-chromes-existing-adblock-apis/

Many of the services on the Internet generate revenue from ads displayed on the page, and Google, a large company, is no exception. As a result, many companies are plagued by the presence of extensions that remove ads from the Internet, and more news sites are blocking users who use the ad block extension to make more money. And it became clear in January 2019 that Google, which is 90% of the revenue from advertising, is also planning to disable the ad block extension feature in Google Chrome using an in-house developed web browser.

Go ahead with measures to disable Google's ad blocking feature for Google to hide ads on the web-GIGAZINE



Google has launched a policy to eliminate some of the ad blocking features in version 3 of the manifest that lists the resources and features available as Chromium extensions, but users who dislike ads when this becomes clear And critics of the ad block extension developers have attracted great criticism.

The strategy was to replace the existing web Request API used in the Chrome content block with a more restrictive declarativeNetRequest API. This will give the list of filters that Chrome has analyzed itself rather than the extension doing the filtering. Therefore, developers of the ad block extension were opposed to this initiative.

However, even after the facts were revealed in January 2019, Google has continued to make API change measures, and it turned out that this plan has been retained as of the end of May. Google developers have posted to the forum that 'Chrome is going to abolish the webRequest API with manifest version 3. Ad blocking is still possible in corporate development, not all webRequest APIs.' From the above, it can be read that the transition plan to the new API is continued and general users are subject to the ad block extension restriction.


by PhotoMIX-Company |

It should be noted, webRequest API in the article currently created can be specified 30,000 of the rules at the time of installation, the 5000 rules of the addition to it when running the extensions can be applied looks like. In other words, Ad block tools like EasyList , which use more than 75,000 rules, are expected to be greatly affected. On the other hand, Google also said that it is considering raising the upper limit of such application rules depending on the performance.

However, even if Google changes the API in manifest version 3, there are still several months left to implement, and it does not mean that version 2 will soon become unusable. From this, the news site Android Police says, 'We still have enough time to switch to Firefox blocking the tracking script by default.'

in Software, Posted by logq_fa