But declarativeNetRequest is the alternative to the webRequest API which Chrome is removing. Using declarativeNetRequest means you have to rely on static rules instead of the dynamic logic that the webRequest API allowed. This is extremely trivial to bypass. So much so that it's basically nothing at all. Especially when you take into account the max ruleset sizes
Also in Chrome (and Chrome only) any images or iframes blocked are simply collapsed
Thanks for the correction. you're correct it's 50 rulesets. Originally the limit was 5,000 rules but it seems the Chrome team backed away from that
Regardless it doesn't change the fact that these are static rules. It's trivial for anti-adblockers to dynamically get a url that is not in a ruleset. Without the dynamic logic that is allowed by the webRequest API we are completely dependent on static rulesets that need to be updated by updating the entire extension itself
The size of the rulesets is a distraction from the fact that adblockers can no longer run dynamic logic to filter web requests and block tracking
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...
But declarativeNetRequest is the alternative to the webRequest API which Chrome is removing. Using declarativeNetRequest means you have to rely on static rules instead of the dynamic logic that the webRequest API allowed. This is extremely trivial to bypass. So much so that it's basically nothing at all. Especially when you take into account the max ruleset sizes
Also in Chrome (and Chrome only) any images or iframes blocked are simply collapsed