Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.
-
Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.
They're not LLMs. They're trained on open data.
Should translation be disabled if the AI 'kill switch' is active?
@firefoxwebdevs I use Firefox, because it is a decent, secure browser with a nice plugin system. I want a browser to be a browser. If I wanted it to be AI, or I wanted it to mine Bitcoins, or spy on me and show me ads, or have 1001 other useless features, I'd choose from a number of other alternatives. When you start pushing useless features like this, I am seriously considering switching the browser. This is how many browsers died, you didn't do your homework. *Nobody* prohibits you from creating useless AIs and serving them as extensions.
-
Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.
They're not LLMs. They're trained on open data.
Should translation be disabled if the AI 'kill switch' is active?
@firefoxwebdevs Be a browser, let translation services do translation. If people have need for translation MLs they can get them on their own. -
@firefoxwebdevs @noah We also don't trust to you keep your word.
-
@firefoxwebdevs I voted in the poll for the least bad option, but I now regret that. Because it’s all so pointless isn’t it? You don’t actually care what I think or what the other users think. If you did you would have asked if we wanted ai slop at all, not what flavour of slop we preferred.
@Abigyil I've already used the results of this poll to push for change in the AI kill switch feature. The feedback has been really useful, and I'm grateful for it.
-
Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.
They're not LLMs. They're trained on open data.
Should translation be disabled if the AI 'kill switch' is active?
@firefoxwebdevs Way to manually enable and disable extensions from toolbar would be good -
Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.
They're not LLMs. They're trained on open data.
Should translation be disabled if the AI 'kill switch' is active?
@firefoxwebdevs yes but let users enable just translations. Rationale: if they're disabled unconditionally, you're holding useful functionality hostage until the user disables the killswitch. If they're enabled unconditionally, they set a precedent that "AI" features disregarding the killswitch is sometimes okay, and then we're back to arguing with you about what "sometimes" means. Let the user decide by *explicitly* overriding the killswitch for whatever features they actually want.
-
Let's ask the real question:
Firefox users,
do you want any AI directly built into Firefox, or separated out into extensions?
@duke_of_germany I ditched Firefox for a combo of Waterfox and Librewolf long enough ago that I forget what it was that made me do so, it was before they started playing footsie with AI... probably the baked-in telemetry, or something like that... whatever it was, it made me ditch T-bird as well.
AND yes, Mozilla should not be messing with AI _at all_.
-
Just give me an easy to find switch that removes _all_ LLM and "AI"-features in Firefox, thank you.
-
@duke_of_germany @firefoxwebdevs @davidgerard @tante BOTH (2) and (3).
The Mozilla I want is one that would pre-install uBlock Origin. An effective adblocker furthers Mozilla's purported mission of "put[ting] control of the internet back in the hands of the people using it" way more than any LLM nonsense.
@tommorris @duke_of_germany @firefoxwebdevs @davidgerard @tante
LibreWolf is a popular fork that pre-installs UBO
I've been using it daily for months
-
@tommorris @duke_of_germany @firefoxwebdevs @davidgerard @tante
LibreWolf is a popular fork that pre-installs UBO
I've been using it daily for months
@rzeta0 @duke_of_germany @firefoxwebdevs @davidgerard @tante yup, I like LibreWolf a lot, although I'm testing out Zen more at the moment.
-
@m0rpk @firefoxwebdevs you have it completely backwards, AI should be opt in not opt out
@redfernmike @m0rpk @firefoxwebdevs But that way they can't validate their CEOs ego by telling them how many people are "using" the Clanker.
-
Let's ask the real question:
Firefox users,
do you want any AI directly built into Firefox, or separated out into extensions?
@duke_of_germany @firefoxwebdevs @davidgerard @tante It depends...
Stuff like the small model they have for language translations, it's ok to be built in, this is a major accessibility feature.Third party models that are subscription services, or running as self hosted services, but that require user to acquire and configure on the browser for it to work (off by default), can be integrated within the browser, as long as they are extensions to other non-ai browser features.
-
@joepie91 I think a lot of people in the replies would consider this sneaky. It's a tricky UX problem. But yes, granular control needs to be part of the solution, along with a kill switch.
-
@duke_of_germany @firefoxwebdevs @davidgerard @tante It depends...
Stuff like the small model they have for language translations, it's ok to be built in, this is a major accessibility feature.Third party models that are subscription services, or running as self hosted services, but that require user to acquire and configure on the browser for it to work (off by default), can be integrated within the browser, as long as they are extensions to other non-ai browser features.
@duke_of_germany @firefoxwebdevs @davidgerard @tante
Other AI features that are not extensions to non-ai features, and are not similar to the language translation feature using a local small model, should definitively be a browser extension.
-
Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.
They're not LLMs. They're trained on open data.
Should translation be disabled if the AI 'kill switch' is active?
@firefoxwebdevs Translation models are language models.
The way I see it, there are two types of AI things in the Firefox product:
• User-helping features: translation, captioning, … Those don’t even need AI in the name, it's clear what they do, and the underlying tech only sets how good they are at their job.
• Buzzword features: AI sidebar, AI window. Those don’t have a user-facing goal, and are essentially a marketing gimmick. -
@firefoxwebdevs Translation models are language models.
The way I see it, there are two types of AI things in the Firefox product:
• User-helping features: translation, captioning, … Those don’t even need AI in the name, it's clear what they do, and the underlying tech only sets how good they are at their job.
• Buzzword features: AI sidebar, AI window. Those don’t have a user-facing goal, and are essentially a marketing gimmick.@espadrine I personally agree with you, but most respondents to the poll do not. It seems like, if the AI switch did not disable translations, folks would not have trust in the setting.
-
Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.
They're not LLMs. They're trained on open data.
Should translation be disabled if the AI 'kill switch' is active?
@firefoxwebdevs "Hey, we pooped in your cake. Do you want us to add inclusive topping : yes, yes but just a bit, no no topping on my poopoo cake, emoji idunnolol"
-
@firefoxwebdevs nobody wants LLMs in our browser. do something useful instead
-
Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.
They're not LLMs. They're trained on open data.
Should translation be disabled if the AI 'kill switch' is active?
@firefoxwebdevs Just keep in mind to keep all AI features off by default no matter what.
-
@firefoxwebdevs We don't want a "kill switch" aka Opt-Out, we want a "live switch" aka Opt-In!
I think it should be very clear by now that most people don't want slop by default.
What is so complicated to understand that?Opt-Out == bad
Opt-In == okay
slop as add-on == best option@CyberPunker @firefoxwebdevs kill switch doesn't mean opt-out, it means have a single button to disable it.
The thing is that an user might have switched on a couple of AI features, and might have changed its mind, and wanted to disable it all permanently or temporarily, and having a single button to do that is very useful.
