Google Proposes Changes to Chromium to Kill uBlock Origin and uMatrix →
From the comments section:
From the description of the declarativeNetRequest API, I understand that its purpose is to merely enforce Adblock Plus (“ABP”)-compatible filtering capabilities. It shares the same basic filtering syntax: double-pipe to anchor to hostname, single pipe to anchor to start or end of URL, caret as a special placeholder, and so on. The described matching algorithm is exactly that of a ABP-like filtering engine.
If this (quite limited) declarativeNetRequest API ends up being the only way content blockers can accomplish their duty, this essentially means that two content blockers I have maintained for years, uBlock Origin (“uBO”) and uMatrix, can no longer exist.
Please don’t use Chrome (or Chromium unfortunately). Just switch to Safari or Firefox (I use it as my second browser and it’s fine).
And while you’re at it, switch out your search engine to DuckDuckGo — it works surprisingly well, even in Poland when searching for Polish content.
via @khron
