3 ms·
> 42% of chrome extensions have abused the web requests API No. The accurate quote is (my emphasis) "According to Google, 42% of MALICIOUS extensions have used
by gorhill 7y ago
> 42% of chrome extensions have abused the web requests API
No. The accurate quote is (my emphasis) "According to Google, 42% of MALICIOUS extensions have used the Web Request API since January 2018".[1]
Note that the source for this quote is Google itself, so they picked this one statistic for publication. We do not know what else they found which is not published, i.e. it's potentially conveniently self-serving toward their manifest v3 narrative.
I reiterate: deprecating the blocking ability of the webRequest API will break key parts of uBlock Origin ("uBO"), and will break uMatrix completely, because of the hard-coded matching algorithm of declarativeNetRequest (there are other issues) which is merely an implementation to enforce EasyList-like rules.
I know how uBO/uMatrix extensions work, I wrote them from scratch. If you want to argue why they will work fine, you will have to do better they merely repeating Google's narrative regarding changes in manifest v3.
ABP will be fine because the primary purpose of ABP is to serve as a revenue source for Eyeo GmbH through its "Acceptable Ads" product (of which Google is a partner), which can still function just fine with the declarativeNetRequest API -- as shown by it's Safari iOS version.
I am not alone in my criticism, for instance the EFF:
https://www.eff.org/deeplinks/2019/07/googles-plans-chrome-extensions-wont-really-help-security https://www.eff.org/deeplinks/2019/07/googles-plans-chrome-e...
Chrome Web Store allows extensions with remote code execution capability[2], this is the foremost issue and it's the one they could have fixed a long time ago with no API changes. That it has not been fixed is what you should be questioning.
* * *
[1] https://www.xda-developers.com/google-chrome-manifest-v3-ad-blocker-extension-api/ https://www.xda-developers.com/google-chrome-manifest-v3-ad-...
[2] https://twitter.com/gorhill/status/1139306139072507906 https://twitter.com/gorhill/status/1139306139072507906