Hacker News Reader

Comment by lapcat | Hacker News Reader

It doesn't seem to be mentioned by the EFF, but coincidentally, January 2023 is when Manifest v2 extensions stop working in Google Chrome: https://developer.chrome.com/blog/mv2-transition/

View on HN

And its going to be a very big moment, since V3 effectively bans Adblockers and website redirect extensions.

It might increase Firefox adoption if it actually happens.

- bans adblockers that use their own matching engine

- bans website redirect extensions that can't use declarativeNetRequest action.redirect https://stackoverflow.com/a/66394857/3878893

The api provided with v3 is not sufficient to create an adblocker with the same privacy protections as is currently possible with v2 https://github.com/uBlockOrigin/uBlock-issues/issues/338

You do realize Firefox is going to V3 as well?

Firefox is adding V3 support for compatibility with Chrome but not removing V2 support: https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-fi...

That's what they say now, they don't exactly have a good extension record themselves.

I operate some popular extensions and I now maintain a v2 and v3 build (make file). I'd love to nuke the v2 build tasks and only operate in v3. Most users are on Chrome anyway.

If you're lucky, v2 will be kept around for legacy extensions that are rarely if ever updated.

V3 and request modification banned are two different things. The chrome still support request modification in v3 but disallow extension to use it(only allow enterprise policy or whatever to enable it). While firefox don't have plans like this (so far).

Reply on news.ycombinator.com