-
(transferred from internal discussion https://github.com/orgs/uBlockOrigin/teams/ublock-filters-volunteers/discussions/423 so some details are outdated) krystian3w notified me that AG is implementing this: AdguardTeam/CoreLibs#1550 I think this will be game changer, for example we'll be able to address those pixsera crap like
The format is just my example idea, AG seems to be going with the same format as $path but we don't have to follow. Although I expect pixsera will then fully randomize domain, the regex will also be useful to other cases such as xhamster proxy sites or some pirate sites. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 13 replies
-
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I guess "negated" regex don't allow example.*,~/example\.([a-z]{1,2}|[a-z]{4,16})/##body > * Workaround can be: example.*##body > *
/example\.([a-z]{1,2}|[a-z]{4,16})/#@#body > * by virtue of the fact that the parser does not have a noop state for cosmetic filters like other silinics. and maybe $all,~doc,domain=example.*|~/example\.([a-z]{1,2}|[a-z]{4,16})/ Lack of workaround to avoid mark allowed to load and block latter with |
Beta Was this translation helpful? Give feedback.
-
Currently when I use Steps to reproduce:
*$frame,from=plainlight.com,to=~/youtube/
*$frame,from=plainlight.com,to=~~/youtube/ and cannot exclude If I use *$frame,from=plainlight.com,to=/youtube/ then it blocks the |
Beta Was this translation helpful? Give feedback.
gorhill/uBlock@b1de8d3