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)
I like how it is opt-in.
Self-hosted and locally run models also goes a long way. 90% of LLMs applications don’t require users to surrender their devices, data, privacy and security to big corporations. But that is exactly how the space is being run right now.
deleted by creator
The alternative is only supporting self hosted LLMs, though, right?
Imagine the scenario: you’re a visually impaired, non-technical user. You want to use the alt-text generation. You’re not going to go and host your own LLM, you’re just going to give up and leave it.
In the same way, Firefox supports search engines that sell your data, because a normal, non-technical user just wants to Google stuff, not read a series of blog posts about why they should actually be using something else.
deleted by creator
Ah, I missed that alt text specifically is local, but the point stands, in that allowing (opt-in) access to a 3rd party service is reasonable, even if that service doesn’t have the same privacy standards as Mozilla itself
To pretty much every non-technical user, an AI sidebar that won’t work with ChatGPT (Google search’s equivalent from my example previously) may as well not be there at all
They don’t want to self host an LLM, they want the box where chat gpt goes
deleted by creator
deleted by creator
deleted by creator
The extension API doesn’t have enough access for this.
While it is opt-in and disabled by default, this is the real problem.
deleted by creator
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.