Hacker News new | ask | show | jobs
by bensecure 934 days 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-addo...

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

1 comments

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