Mozilla isn’t in charge of the extension API, it uses Chromium’s WebExtensions API
No. They are basing their implementation on that of Chrome, but nobody is forcing Mozilla to do this … So yes, Mozilla is responsible for all the APIs they integrate. Of course.
Like yea, it’a technically a levie, not a tax. This whole “it’s different because it does not go through the budget” is such a learned talking point. We have it in Germany as well with our state funded public media houses. You say something about their bias, count to five and suddenly someone appears and tells you that same story of fictional independence through funding through levie.
deleted by creator
The extension APl doesn’t have enough access for this.
If that’s the case, then it’s pretty great that Mozilla is also the exact company in charge of the extension API.
I have only one extension, and I use it longer than I use Firefox. I also trust the developer a lot more than I trust Mozilla.
This is absolutely not how any of this works.
While Mozilla implements the WebExtensions API based on the W3C standard, they are not bound to a 100% verbatim implementation. Like other browser vendors, Mozilla has the flexibility to extend or modify the API as needed, as long as they maintain compatibility with the core standard. Adding new APIs or features to the extension system does not require creating an entirely incompatible engine. Browser vendors often add non-standard extensions to APIs, which can later be proposed for inclusion in the next version of the standard if they prove useful. So, Mozilla can certainly add new APIs to their extension system without making it incompatible with the existing WebExtensions ecosystem. This is not difficult to understand.