Manifest V3 will affect on UX of many extensions. For an instance, i've built a Linguist, is a full featured translation in browser that may translate even off

Manifest V3 will affect on UX of many extensions. For an instance, i've built a Linguist, is a full featured translation in browser that may translate even offline (with embedded Bergamot translator of Mozilla) https://github.com/translate-tools/linguist https://github.com/translate-tools/linguist One of important Linguist features is that user able to use custom translators, it means user may insert their javascript code that implements a translator class, and then use their custom translator. So it is possible to use ChatGPT as translation module in Linguist, or even local instance of LLAMA, any proprietary translation service API, etc. But with manifest V3, google also ban RCE (remote code execution), so probably when i will implement a feature "custom translators store" where will be present a lot of custom translators from a github, and this feature will fetch their code when user press "install", a google will ban this version, and i will be forced to roll back this feature for chrome, and leave it as is in Firefox. As result, a Chrome users will always have a "simplified" versions of features and we will have inversed case with Browser API features (when site tell you "go chrome to run my features"). An extensions will notify their users "go firefox to have all features like a custom translators store or ads blocker". Is this a distributed and balkanized web3?