There are situations when it is difficult or at leas annoying: sometimes blocking rules are too loose that generates false positives. Few examples from my perso

There are situations when it is difficult or at leas annoying: sometimes blocking rules are too loose that generates false positives. Few examples from my personal memory: - "Block any image on any domain that has `/ad/` in its path." (Encountered in certain local block list, not present in such pure form at time of writing.) Found this one while inspecting bugreport of our client who complained he cannot see some images on his presentation we maintained. Our CMS serves static binary data with "folderized hash paths" where occurrence of `/ad/` is not completely avoidable. Even now Easylist [1] inludes many general `adsomething` rules that FMOPW could do many false positives. - "Block any flash that has `clickthru` parameter." This rule is still present in aforementioned easylist [1]: `.swf?clickthru=`, but amusingly is very easily avoidable (rule insists that this parameter is first). Back in times this parameter was de facto standard for embedded flash serving as hyperlink to tell it where to link to. Found this one when another client complained that his flash-based part of main navigation (supplied by third party studio) does not work. - Even now the question "Have you disabled your adblocker?" often relevant response to general WTFs during web-development. [1] https://easylist-downloads.adblockplus.org/easylist.txt https://easylist-downloads.adblockplus.org/easylist.txt