4 ms·
> One thing that I'm sure about V3 is that it isn't well thought-out at all. that's because it's been invented for the sole purpose of making "breaking effecti
by blibble 4y ago
> One thing that I'm sure about V3 is that it isn't well thought-out at all.
that's because it's been invented for the sole purpose of making "breaking effective ad-blocking" look legitimate
- nonbirithm 4y agoAnd similarly, FLoC was invented for the sole purpose of making targeted advertising look legitimate.
- pornel 4y agoThere was also a lot of futile searching for use-cases for Signed Exchange spec, which was just AMP letting Google host and monitor other pages' traffic.
- charcircuit 4y agoFrom what I've seen the main purpose is to increase secruity, privacy, and performance of the extension ecosystem. I have seen no sign of mv3 being for breaking ad blocking. MV3 and other parts of chromium have added features that help ad blockers.
- akomtu 4y agoThat'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 agoMV3 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 agoIf 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 agoTrying 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.