Hacker News Reader

Comment by anilshanbhag | Hacker News Reader

This is a manifest V2 extension. Unless someone converts it to V3, it will stop working end of this year.

I don't believe Firefox has announced a discontinuation date for V2. If your browser vendor breaks your stuff perhaps you should consider switching browsers ...

Deprecating a manifest standard isn’t breaking stuff if the apps don’t work it’s on them not the vendor (obviously within reason.)

If I take your API away, I am breaking your app.

They are working on that: https://github.com/OhMyGuus/I-Dont-Care-About-Cookies/pull/9

Not a problem on Firefox and its derivatives

Does anyone know if Brave will still support v2?

It's based on Chromium, so no.

Come on, you could have googled it instead of just guessing.

Eg https://github.com/brave/brave-browser/issues/20059

> Yes - manifest v2 extensions will be supported by Brave We'll be taking steps as V2 is sunset by Chromium team (https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/)

>During the deprecation period, we can keep this functionality via patch (since it's there for Enterprise). After V2 is pulled from store, we'll need to stand up our own extension store for manifest v2

Is it that simple? Brave has various proprietary bits, so it's possible they could maintain v2 support. Perhaps others know if this is feasible, from a technical perspective.

Until a chromium browser let's you use arbitrary extension stores, I don't think there's any fork that's divergent enough. And I haven't found one after months of searching.

I'm almost to the point of trying to do it myself.

only if you're using user hostile browsers.

Reply on news.ycombinator.com