5 ms·

That's lie pushed by Google. MV3 removes the ability to block requests, but keeps the ability to observe requests. Great for ads-related spying.

• charcircuit 4y ago
  MV3 is more than declarativeNetRequest and the reason why declarativeNetRequest improves privacy is that users are not giving out as overly broad permission. A user may want to block ads, but may also want to not give the ad blocker the ability to observe the requests. Even if the user trusts the developer of the adblocker, there is always the chance they get hacked. The average user should not be giving out the webRequest enabled for every website to an extension. It makes sense for the chromium team to periodically evaluate the use cases of extensions and see if there are better APIs that it could offer to move the ecosystem forward.
  • akomtu 4y ago
    If that was the case, mv3 would let extensions block arbitrary requests on a subdomain, e.g. "uBO wants to block requests on *.com, Yes/No".
    • charcircuit 4y ago
      Trying to keep webRequestBlocking around would mean that the performance benefits of declareNetRequest wouldn't propogate an well as it could. The worst offendors of being slow to block requests are likely to be the same extentions who wouldn't migrate to declareNetRequest.
      • blibble 4y ago
        you know what's even slower? pulling down 15mb of bullshit ads on every single page
      • akomtu 4y ago
        There are no performance benefits of declareNetRequest. One regex is faster than matching against tens of thousands of urls.