4 ms·

I would be interested to see a list of capabilities and features lost in MV3. For example, do we lose CNAME filtering or strict-blocking? It's not clear what we

by e2le 3y ago

I would be interested to see a list of capabilities and features lost in MV3. For example, do we lose CNAME filtering or strict-blocking? It's not clear what we are losing.

ghostwords 3y ago
We lose the ability to innovate. The browser (Google) becomes the gatekeeper. And yes, we lose CNAME filtering.[1] https://github.com/w3c/webextensions/issues/151#issuecomment-1018778881 https://github.com/w3c/webextensions/issues/151#issuecomment... Google is an advertising company. Chrome extensions already experienced a lost decade, where nothing much happened until the Manifest V3 "proposal". It's not a good idea to let Google hold the keys to anti-tracking tech. [1] I stand corrected, DNS lookups are not part of webRequest in MV2 Chrome either. This doesn't change my larger point.
- magicalist 3y ago
  > And yes, we lose CNAME filtering But Chrome never had CNAME filtering before either
  - deleted 3y ago
    [deleted]
madars 3y ago
CNAME uncloaking does not work in Chrome: https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-best-on-Firefox https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...
bluish29 3y ago
The last time I check a couple of months ago these was the list of things that we lose (Things might have changed so I welcome correction from any kind) - Now any block filter list will have be updated with a plugin update. So no fetching lists from links directly. - strict blocking ability [1] - No dynamic filtering [2] - No Custom lists (own or third party by the user) - Element Picker [3] [1] https://github.com/gorhill/uBlock/wiki/Strict-blocking https://github.com/gorhill/uBlock/wiki/Strict-blocking [2] https://github.com/gorhill/uBlock/wiki/Blocking-mode https://github.com/gorhill/uBlock/wiki/Blocking-mode [3] https://github.com/gorhill/uBlock/wiki/Element-picker https://github.com/gorhill/uBlock/wiki/Element-picker

by e2le 3y ago

I would be interested to see a list of capabilities and features lost in MV3. For example, do we lose CNAME filtering or strict-blocking? It's not clear what we are losing.

ghostwords 3y ago

We lose the ability to innovate. The browser (Google) becomes the gatekeeper. And yes, we lose CNAME filtering.[1] https://github.com/w3c/webextensions/issues/151#issuecomment-1018778881 https://github.com/w3c/webextensions/issues/151#issuecomment... Google is an advertising company. Chrome extensions already experienced a lost decade, where nothing much happened until the Manifest V3 "proposal". It's not a good idea to let Google hold the keys to anti-tracking tech. [1] I stand corrected, DNS lookups are not part of webRequest in MV2 Chrome either. This doesn't change my larger point.

magicalist 3y ago
> And yes, we lose CNAME filtering But Chrome never had CNAME filtering before either
- deleted 3y ago
  [deleted]

madars 3y ago

CNAME uncloaking does not work in Chrome: https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-best-on-Firefox https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...

bluish29 3y ago

The last time I check a couple of months ago these was the list of things that we lose (Things might have changed so I welcome correction from any kind) - Now any block filter list will have be updated with a plugin update. So no fetching lists from links directly. - strict blocking ability [1] - No dynamic filtering [2] - No Custom lists (own or third party by the user) - Element Picker [3] [1] https://github.com/gorhill/uBlock/wiki/Strict-blocking https://github.com/gorhill/uBlock/wiki/Strict-blocking [2] https://github.com/gorhill/uBlock/wiki/Blocking-mode https://github.com/gorhill/uBlock/wiki/Blocking-mode [3] https://github.com/gorhill/uBlock/wiki/Element-picker https://github.com/gorhill/uBlock/wiki/Element-picker