Important:
The gnuzilla.org filter list "Block all well known privacy trackers" has been removed, due to it's high likelihood of breaking web pages. The filter list I learned is made from piecing together already existing filter lists, i.e. EasyList, EasyPrivacy, Fanboy Social, except that all exception filters to ensure no page breakage are removed.
Two alternatives for those who really want to use that list:
Non-recommended: Use
http://gnuzilla.gnu.org/filters/blacklist.txt as custom filter list.
Recommended: if privacy is a top concern and you do not mind page breakage, use uBlock's dynamic filtering in default-deny mode.
This will be even much more strict than the gnuzilla.org filter list can ever be.
You gain the ability to very easily un-break web pages through simple point-and-click.
New:
Cosmetic filters are now reported in the logger (related long-standing issue: chrisaljoudi#308).
Whatever added overhead incurred as a result of surveying active cosmetic filters exists if and only if the logger is opened, and only for whatever tab is being logged.
Tool added to logger: ability to manually evaluate static filters (related long-standing issue: chrisaljoudi#10).
Mostly useful to advanced users for when trying to diagnose filtering issues.
Example: a user complained of non-blocked popups.
I could not reproduce the issue, as the web site was not serving me the specific popup which was reportedly not blocked.
However now I can enter manually the URL, and other relevant parameters.
Result: within seconds I could identify what was the issue.
No internationalization available yet (please do not file an issue).
Various other trivial improvements to the logger.
Fixed regression bug: Console error when you clear request log and try to reload
The derivation of synthetic hostnames for special pages has been extended to enable more specific rules. For examples:
Whitelist only Firefox Hello: loopconversation.about-scheme (derived from about:loopconversation).
Whitelist only about:blank: blank.about-scheme (derived from about:blank).
Whitelist uBlock's own pages (Firefox): ublock0.chrome-scheme (derived from chrome://ublock0/[...]).
Whitelist uBlock's own pages (Chromium): cjpalhdlnbpafiamejdnhcphjbkeiagm.chrome-extension-scheme (derived from chrome-extension://cjpalhdlnbpafiamejdnhcphjbkeiagm/[...]).
Whitelist all extensions' pages (Chromium): chrome-extension-scheme (derived from chrome-extension://[...]).
Etc.
All these synthetic hostnames can also be used in dynamic filtering rules.
Closed as fixed:
Chromium
Detect ublock by sending ajax
Firefox
uBlock is blocking Firefox Hello
Firefox Hello widget is embedded in a tab which URL is about:loopconversation#[...], so this means you need to whitelist about-scheme in the Whitelist pane.
Core
Cosmetic filters not always applied on specific website
http://honyaku.yahoo.co.jp/Filter misinterpretation?
Strange bug with specific website
Definitely a bad bug which was still lingering in uBlock.
The bug surfaced only for when a user created custom filters using the element picker.
It was only a runtime bug, i.e. it disappeared when reloading the filter lists or rebooting uBlock.
