This will be a temporary account, just letting
@Marko :) to know I provide such
rules (CDNs included in Decentraleyes but not in my rules are Chinese ones, no need unless you visit Chinese sites). Sad nobody mentioned it as it's brought up on Wilders very recently where some ppl here are members. A few comments before leaving:
@Marko :) They're not for other ad-blocker but for uBO - some filters are excluded by NOT_PLATFORM directive and others are commented out while a few issues are specifically addressed for uBO. There are still incompatible filters left but you can see which are them by opening the logger and adding/updating the filter. Some filters are not in stock lists but you can direcly type URL of the filter you want, say, optimized Annoyances filters is
here. I PERSONALLY do not recommend subscribing too many annoyances filters because in many cases they hide the same elements by different rules - unlike network rules they are not discarded by uBO and having too many cosmetic filters injected into a page is not good in terms of performance.
@JohnR There is no difference in speed by having less or more rules, it's provable both by theory (computational complexity) and by measurements (use dev tools or a benchmark tool, never rely on human perception - you also need to know how to measure it properly, network latency affects much more than rule matching). More rules causes more memory consumption, but what causes slowdown is NOT the number of rules but that of inefficient rules (1). Also the number of cosmetic filters injected to the page can affect performance, more so if they're inefficient. The main point of having less filters is to reduce FPs and anti-adblock warnings - for these and also for really better performance turning generic cosmetic filters off is the most effective way (2) but you may need to replace these rules by yourself, a reason I provide Placeholder Hider but it's not very comprehensive. Another point is stricter blocking - piling many filters up also piles whitelists up which have precedence over blocking filters. I have been reporting unnecessary whitelists to major lists and even provide Anti-whitelist but I don't look at other lists enough, and occasionally see loose whitelists in some minor lists. One should really be careful before subscribing unpopular lists, Internet is full of low-quality lists.
(1) Efficient rules are tokenizable, or at least well narrowed-down by request types, origin, domains etc. The number of tokenizable rules doesn't affect speed but for this tokenization what holds on ABP syntax does not always holds on uBO.
(2) The most common trigger for anti-adb is cosmetic filtering (particularly ##.adsbygoogle), just see how many $generichide or $ghide (and #@#.adsbygoogle) are included in EL, uBlock filters, or AG Base. Ofc others are triggered by network rules (the champion in this part will be pagead2.googlesyndication.com/*/adsbygoogle.js but there are really many patterns.).
@oldschool 23 probably means you write cosmetic filters by your own, that's no bad. Just saying while writing cosmetic filters is so easy that even the picker can do it for you, writing efficient cosmetic filters is not. If one ends up creating hundreds of cosmetic filters without understanding how to write efficinet filters it will probably be better to subscribe good lists.
@SeriousHoax Just two rules in EP
/b/ss/*&aqe=
/id?d_visid_
have been blocking hundreds if not thousands of CNAME trackers and it's really rare Frogeys's list catches anything missed by EP (tho in the logger simple hostname rules have precedence). This is another reason you shouldn't only look at the number of rules.
@Lenny_Fox I haven't looked MT for a while but ty for crediting me in another thread, however, you forgot the most important part - prefix with | for rules starting from http or https, otherwise such rules are slow and can cause FPs. BTW in the last few months I've seen even common bad actors have been switching to https (
accroding commit in my list) so I think the relevance of the rules is decreasing, tho http was still used in redirect chain and also I've found a few hijacked http sites (haven't reported to AG except one case because in the rest of cases malicious scripts were blocked by EL rules such as &prvtof=*&poru=).
@Tiamati (Related to the comment to Lenny) Why ||* ? If you don't specify a domain, just use * like *$object,ping,popunder. I'd warn *$popunder may prevent some legitimate action, just for demonstration set Google search not to open in a new window, middle-click a link first then left-click the same or another link. Note the rule is not tokenizable tho still get benefit of request-type optimization; usually such rules are narrowed down by $domain=. For this kind of control I rather recommend dynamic filtering - having GUI only for some request types doesn't mean other types are not supported.
Will leave here but please don't take it as a spam - I decided to spent my spare time in contribuing to uAssets/AG/EL/Brave than discussion, thus left Wilders.