5 ms·

I work on adblocking at Brave. 1. Brave, Vivaldi, and Opera have all announced they'd maintain support for Mv2 past Google's deprecation date [1]. 2. Your gue

I work on adblocking at Brave. 1. Brave, Vivaldi, and Opera have all announced they'd maintain support for Mv2 past Google's deprecation date [1]. 2. Your guess is correct - one of Google's stated motivations is to make the extension review process easier and less error-prone; having a way to opt-out would be counterproductive in that regard. I strongly doubt they'd accept the PR upstream; there is a chance other players could maintain patches to modify Mv3 but the effort of designing and implementing a new spec around the Mv3 spec and convincing extensions to maintain yet another platform means this is unlikely to happen in practice. Keeping Mv2 around is a more reasonable approach (and one that is compatible with Firefox, as well). [1] https://www.zdnet.com/article/opera-brave-vivaldi-to-ignore-chromes-anti-ad-blocker-changes-despite-shared-codebase/ https://www.zdnet.com/article/opera-brave-vivaldi-to-ignore-...

Vinnl 3y ago
Will you be working together with Vivaldi and Opera to maintain the fork of MV2's request interception, or will we have multiple independent implementations?
- antonok 3y ago
  Nothing coordinated so far, but keep in mind Mv2 code will still exist behind a policy flag in Chromium until at least June 2025; there's still quite some time.
bensecure 3y ago
> there is a chance other players could maintain patches to modify Mv3 but the effort of designing and implementing a new spec around the Mv3 spec and convincing extensions to maintain yet another platform means this is unlikely to happen in practice. The design has already been completed, in that mozilla has already done this in their implementation of manifest v3. The difficulty of convincing extension developers to support it should thus be no more difficult than convincing them to ship a firefox version of their extension. > Keeping Mv2 around is a more reasonable approach (and one that is compatible with Firefox, as well). This isn't a long term solution. Brave for example has only committed to maintaining mv2 support as long as chrome continues to support it internally. If chrome removes it, the work of continuing to support it would become untenable. https://blog.mozilla.org/en/products/firefox/extensions-addons/heres-whats-going-on-in-the-world-of-extensions/ https://blog.mozilla.org/en/products/firefox/extensions-addo... https://twitter.com/BrendanEich/status/1684654531723026434 https://twitter.com/BrendanEich/status/1684654531723026434
- asddubs 3y ago
  so in summary, all the clonium browsers depend on the company who is currently in the process of removing mv2 to not remove mv2 in their repo. good luck with that

Vinnl 3y ago

Will you be working together with Vivaldi and Opera to maintain the fork of MV2's request interception, or will we have multiple independent implementations?

antonok 3y ago
Nothing coordinated so far, but keep in mind Mv2 code will still exist behind a policy flag in Chromium until at least June 2025; there's still quite some time.

bensecure 3y ago

> there is a chance other players could maintain patches to modify Mv3 but the effort of designing and implementing a new spec around the Mv3 spec and convincing extensions to maintain yet another platform means this is unlikely to happen in practice. The design has already been completed, in that mozilla has already done this in their implementation of manifest v3. The difficulty of convincing extension developers to support it should thus be no more difficult than convincing them to ship a firefox version of their extension. > Keeping Mv2 around is a more reasonable approach (and one that is compatible with Firefox, as well). This isn't a long term solution. Brave for example has only committed to maintaining mv2 support as long as chrome continues to support it internally. If chrome removes it, the work of continuing to support it would become untenable. https://blog.mozilla.org/en/products/firefox/extensions-addons/heres-whats-going-on-in-the-world-of-extensions/ https://blog.mozilla.org/en/products/firefox/extensions-addo... https://twitter.com/BrendanEich/status/1684654531723026434 https://twitter.com/BrendanEich/status/1684654531723026434

asddubs 3y ago
so in summary, all the clonium browsers depend on the company who is currently in the process of removing mv2 to not remove mv2 in their repo. good luck with that