4 ms·

> I can appreciate that uBlock Origin wants to be a universal condom that works on every website for everyone, but I also don't think it's so damning if the con

> I can appreciate that uBlock Origin wants to be a universal condom that works on every website for everyone, but I also don't think it's so damning if the content blocker API is sufficient for that. Yet uBlock Origin and its rule lists still fail at this task as well. I'd say it is sufficient for 90% of the websites at the moment. My point is that this is not a constant value. Advertisers adapt and evolve, and content blockers need to do the same. > A website can do any number of annoying things that uBlock Origin cannot block including things that aren't even related to ads. I simply refuse to use such websites. In fact, I want to know that a website does these things rather than remain in blissful ignorance. I don't want to support such a website even with my viewership. This is indeed the best way to let site owners know that this approach is unacceptable. I wish everyone were doing the same. > The rule limit is circumvented by simply bundling multiple rule lists. Sure, but this is a workaround, quite an ugly one in fact. > Also, 80% of Easylist is crap anyways It does contain a lot of redundant rules, maybe 30% of it, but not 80% that's for sure. And what if I want to use more filter lists? The only thing I can do is use the multiple lists workaround. It is simply weird that nothing was done about this limitation in more than 3 years.

hombre_fatal 7y ago
I think the limitation is just the simplest trade-off. For example, an unbounded rule list has unbounded serial compilation time. A 50k rule list recompiles in a couple seconds on my laptop and quite some time on my iPhone, but multiple rule lists can be compiled in parallel. I suppose your response to this would be that content blocker recompilation could be made parallel over a single list or made to support incremental recompilation. And you're probably right. But note that even Chrome's proposed content blocker system has the same limitation. Perhaps it's not as straightforward as it seems and it's not just a result of neglect/abandonment. I mainly responded because the language you used seemed more damning than necessary. But have you tried 1Blocker X[1] which is built on the content blocker API? It's hard to condemn the content blocking system too much when there's an app that utilizes it to such great effect. You are right about Apple/Webkit moving slowly on community feedback and bug reports though. I suppose I'm used to the glacial pace of non-critical-path browser issues after my Firefox bug went three years without response until it was fixed after Quantum's release. You are probably more critical here than I am. At Amazon, anything sev3 to sev5 went into a heap so large it was a miracle if anyone opened it again. [1]: https://itunes.apple.com/us/app/1blocker-x-adblock/id1365531024 https://itunes.apple.com/us/app/1blocker-x-adblock/id1365531...

hombre_fatal 7y ago

I think the limitation is just the simplest trade-off. For example, an unbounded rule list has unbounded serial compilation time. A 50k rule list recompiles in a couple seconds on my laptop and quite some time on my iPhone, but multiple rule lists can be compiled in parallel. I suppose your response to this would be that content blocker recompilation could be made parallel over a single list or made to support incremental recompilation. And you're probably right. But note that even Chrome's proposed content blocker system has the same limitation. Perhaps it's not as straightforward as it seems and it's not just a result of neglect/abandonment. I mainly responded because the language you used seemed more damning than necessary. But have you tried 1Blocker X[1] which is built on the content blocker API? It's hard to condemn the content blocking system too much when there's an app that utilizes it to such great effect. You are right about Apple/Webkit moving slowly on community feedback and bug reports though. I suppose I'm used to the glacial pace of non-critical-path browser issues after my Firefox bug went three years without response until it was fixed after Quantum's release. You are probably more critical here than I am. At Amazon, anything sev3 to sev5 went into a heap so large it was a miracle if anyone opened it again. [1]: https://itunes.apple.com/us/app/1blocker-x-adblock/id1365531024 https://itunes.apple.com/us/app/1blocker-x-adblock/id1365531...