V3 doesn't allow network calls to be modified, for privacy reasons. It still allows them to be blocked, which is how the adblocking works in the first place.
Contrary to what you say, v3 does block the tracking in the ad request as well as the bandwidth.
It only allows them to be blocked with static rulesets. And these rulesets have a maximum size of 50. There's no way this is large enough to cover all your websites. It's also trivial for an anti-adblock script to try a few different urls until it finds one that isn't in your static ruleset
I'm not well versed into adblocking, but shouldn't the extension also get access to the content of the request as well, to be able to either improve it's blocking accuracy (e.g. detect if the whitelisted content matches blocked content patterns) or decide to hide a resource after it was fetched ?
V3 doesn't allow network calls to be modified, for privacy reasons. It still allows them to be blocked, which is how the adblocking works in the first place.
Contrary to what you say, v3 does block the tracking in the ad request as well as the bandwidth.
https://developer.chrome.com/docs/extensions/reference/api/d...