Comment by culi
1 year ago
They can still block elements from appearing on your browser but in the background the network calls are still being made. That means you are no longer being protected from tracking and your internet is once again being slowed down by the loading of ads
That's not true. The requests themselves are blocked:
https://developer.chrome.com/docs/extensions/reference/api/d...
Lol yeah with a max number of rules being 50
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
330k, not 50 https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...
I try to assume good intentions, but at this point you seem to be simply trying to spread misinformation, and I don't know why.
The maximum number of rule sets is 50, not rules, as your own link clearly and unambiguously states.
The actual minimum (not maximum) number of supported rules is 30,000:
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...
In reality, Chrome supports over 10x that. And UBOL doesn't even use/need the minimum, sticking to around 17,000.
1 reply →