I did a quick survey of some subscription lists, counting the lines beginning with @@ (exception rules) and separately counting the lines containing a single @ (apart from a few special cases, these are element hiding exceptions are they not?). From a protection POV I'm not sure how much of a problem element hiding exceptions could be but I figured I'd count those while I was at it. Results:
- Code: Select all
List @@ lines @ lines
EasyPrivacy+EasyList.txt 2162 489
easylist.txt 2162 489
easyprivacy.txt 486 0
fanboy-annoyance.txt 157 68
fanboy-social.txt 124 60
Antisocial.txt 9 0
malwaredomains_full.txt 0 0
I quickly scanned all of the EasyPrivacy+EasyList @@ exceptions lines (extremely tedious) and spotted roughly two dozen lines that appeared to make sense for my context. IOW, rules which might break something at a site I would both a) visit and b) care about in terms of breaking things. So for some aggressive blockers I think this is a needles in haystack situation.
In addition to the "identify encountered exceptions by browsing with blockable items open" approach mentioned by mapx, I thought of another approach. Enable Count Filter Hits. Browsing the sites where you might care about something being broken. Then go into Filter Preferences and sort subscription list rules in order of decreasing hits. Scan down that list looking for exception rules that were hit. You can try disabling ones you don't think are necessary for your context and see if you run into any problems.
I don't see a way to disable multiple selected rules in one shot. A context-menu option to do this would be nice. So if you want to disable very many exception rules other than a select few, I think you'd want to create a helper script. From within Blockable Items or Filter Preferences, copy the desired exception rules to a keepers file. Via custom program or script, you can modify an Adblock Plus backup file (disable the @@ exception rules that aren't in the keepers file). Afterwards, import that modified backup file. Some work, and you'd still have to be on the lookout for new exception rules being included in updates.