-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unblock rules too unspecific for certain sites #13
Comments
Rule conflicts sound like an upstream issue. Does anyone know how ab2p or EasyList handle conflicts? |
I may be wrong, but IMHO it is not about rule conflict, but about missing feature in a2p. If rule uses That is why following in this case is right to have it in |
This bug is related to the #17 and basic fix is rather simple as it requires only change in templates ab2p.system.action should add new filter which by default could be used for all sites
ab2p.system.filter - separate filters. this allows easy possibility to add exceptions
Now one can easily add sites which do not work with
In second step which would require more work it would be beneficial to add new feature which would convert all rules containing hosts with |
The CSS |
https://easylist-downloads.adblockplus.org/easyprivacy.txt uses
||ria.ru/js/counter.js
whilehttps://easylist-downloads.adblockplus.org/advblock.txt uses
@@||ria.ru^$generichide
This leads to following combination
Converter works fine for both as rules get created as intended for both records. Problem is however that using whitelist is meant only for element hidding while generated privoxy record allows all traffic for that site including counter which should be blocked as easyprivacy.txt record intended.
In case like that seems it is better to not create / remove
ru/ria/ab2p.css
instead creating too generic filter which would also disable other filters.Workaround before using that filter with adblock2privoxy hashout all generichide whitelistings from the filter list using
sed -i -e '/@@||/{/generichide/s/^/#/}' advblock.txt
The text was updated successfully, but these errors were encountered: