You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
About half of my dynamic filtering noop rules have hostnames that end with the strings assets|cdn|static followed by their TLDs. Most of the time I find a broken page, those are also the strings I look for to unblock the right domain with the extension popup. I believe that's the case with all users who block third-party scripts and/or frames by default.
Back in 2014, when uBlock Origin was created by @gorhill, these weren't so common, but now all kinds of websites use secondary "CDN" domains with such patterns, and require them to work properly.
noop'ing them has become a tedious time-taking process that could be simplified if it was possible to add basic wildcards to rules. This would allow one could keep blocking the majority of third-party scripts and frames by default, but also write filters with simple wildcards like this (or any other more appropriate syntax):
* *cdn.com * noop
These wildcards, like all dynamic rules, would still have to be entered manually by the user, who's always responsible for his/her own rules and blocking options.
Using static filters isn't an option because we still want all regular filters to apply to these domains, and not to whitelist them altogether. The point is to reduce user fatigue and make the use of dynamic filters and the "medium mode" more convenient and attractive.
The text was updated successfully, but these errors were encountered:
About half of my dynamic filtering
noop
rules have hostnames that end with the stringsassets|cdn|static
followed by their TLDs. Most of the time I find a broken page, those are also the strings I look for to unblock the right domain with the extension popup. I believe that's the case with all users who block third-party scripts and/or frames by default.Back in 2014, when uBlock Origin was created by @gorhill, these weren't so common, but now all kinds of websites use secondary "CDN" domains with such patterns, and require them to work properly.
noop
'ing them has become a tedious time-taking process that could be simplified if it was possible to add basic wildcards to rules. This would allow one could keep blocking the majority of third-party scripts and frames by default, but also write filters with simple wildcards like this (or any other more appropriate syntax):These wildcards, like all dynamic rules, would still have to be entered manually by the user, who's always responsible for his/her own rules and blocking options.
Using static filters isn't an option because we still want all regular filters to apply to these domains, and not to whitelist them altogether. The point is to reduce user fatigue and make the use of dynamic filters and the "medium mode" more convenient and attractive.
The text was updated successfully, but these errors were encountered: