News for hackers. Stuff that matters.
Re:Proxy Chrome extensions are not going to be usable in MV3 by imbnwa on Monday September 19, 2022 @02:07PM (#32901782)
Brave has publicly declared support for Manifest v2 in perpetuity, no? They even seem to be pondering how to distribute v2 extensions post-sunset in Google Chrome[0]

[0]https://github.com/brave/brave-browser/issues/15187

Re:Proxy Chrome extensions are not going to be usable in MV3 by Caspy7 on Monday September 19, 2022 @02:53PM (#32902351)
https://twitter.com/BrendanEich/status/1534893414579249152

> Brave will support uBO and uMatrix so long as Google doesn’t remove underlying V2 code paths (which seem to be needed for Chrome for enterprise support, so should stay in the Chromium open source). Will Google Chrome Web Store really kick them out over V2? We will host if needed.

https://twitter.com/BrendanEich/status/1534905779630661633

> > I’d be interested to hear a plan for Brave on what will happen if upstream removes the code paths needed for pre-v3 ad blockers.

> We could fork them back in at higher maintenance cost. No point in speculating — I don’t write checks of unknown amount and sign them, and Google looks likely to keep V2 support for a year (thanks be to “enterprise”).

Re:Proxy Chrome extensions are not going to be usable in MV3 by imbnwa on Monday September 19, 2022 @03:03PM (#32902477)
I see my misunderstanding, they're specifically maintaining the webRequest interface
Re:Proxy Chrome extensions are not going to be usable in MV3 by yoasif_ on Monday September 19, 2022 @04:37PM (#32903599)
> I see my misunderstanding, they're specifically maintaining the webRequest interface

They aren't specifically maintaining anything. Brave's CEO doesn't "write checks of unknown amount[s] and sign them".

Re:Proxy Chrome extensions are not going to be usable in MV3 by Caspy7 on Monday September 19, 2022 @05:07PM (#32903972)
I think you're thinking of Firefox.
Re:Proxy Chrome extensions are not going to be usable in MV3 by cpeterso on Monday September 19, 2022 @02:30PM (#32902049)
Maintaining out-of-tree patches for a project as large and quickly-changing as Chromium will be a lot of work. I know someone who worked on Amazon's Silk browser team and they had an engineer (rotation) working working full-time to keep their Chromium fork up to date within Google's upstream. Brave doesn't have nearly the resources that Amazon does.
Re:Proxy Chrome extensions are not going to be usable in MV3 by UberFly on Monday September 19, 2022 @03:33PM (#32902842)
Yea you've seen it tried in projects like Waterfox and Palemoon and it eventually becomes too much to deal with. (Following the old Firefox addons system that is)
Re:Proxy Chrome extensions are not going to be usable in MV3 by TremendousJudge on Monday September 19, 2022 @04:07PM (#32903208)
Yeah it's clear that was never going to work -- the whole point of dropping the old addons was making big architectural changes that weren't possible with the old APIs. You can't merge the new architectural changes and the old APIs without running into the issues they were trying to avoid by removing the old APIs in the first place.
Re:Proxy Chrome extensions are not going to be usable in MV3 by marwis on Monday September 19, 2022 @03:36PM (#32902883)
There are few projects and companies that do exactly that, including CEF open source project. Perhaps they should join forces and make a joint OpenChromium project.