Tldr: Theyre adding an opt-in alt text generation for blind people and an opt-in ai chat sidebar where you can choose the model used (includes self-hosted ones)
Tldr: Theyre adding an opt-in alt text generation for blind people and an opt-in ai chat sidebar where you can choose the model used (includes self-hosted ones)
If it was truly opt-in, it could be an extension. They should not be bundling this with the browser, bloating it more in the process.
AI already has ethical issues, and environmental issues, and privacy issues, and centralization issues. You technically can run your own local AI, but they hook up to the big data-hungry ones out of the box.
Look at the Firefox subreddit. One month ago, people were criticizing the thought of adding AI to Firefox. Two months ago, same thing. Look at the Firefox community. See how many times people requested AI.
The extension API doesn’t have enough access for this.
While it is opt-in and disabled by default, this is the real problem.
What are they missing? So far, all they’ve added is a sidebar and a couple extra right-click menu additions. Both of these are available for all extensions.
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.
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.
Yeah, just create an entirely new, incompatible extension engine from scratch for this one feature specifically!
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.
I believe what most people are concerned about, including myself, was the AI features being enabled automatically and then having to disable it like every other application would do to inflate metrics.
Because this is opt in like it says in the blog I am ok with it there and disabled.