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 the AI kill switch could be better rebranded as the GenAI kill switch (I get that marketing has muddied the water here).
ML models like translations are very much not the same thing as the LLMs being pushed at the moment and should be treated separately.
And I truly appreciate the work out into getting it performant and accurate enough for my needs.
For me, ensuring that the browser isn't leaking what I'm reading is an important privacy control, and I wouldn't trust a 3rd party plugin or an online translator service (or Google translate in Chrome).
-
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?
donate to servo if you can
https://opencollective.com/servo
they have a roadmap that is dedicated to making an actual browser engine, not a collection of browser features on top of one
-
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 The problem is "AI" is a meaningless marketing term, and if you have to pose a question using it, then you aren't being specific enough about what you're asking. More generally, if you find you have to pose an ethical question at all to the public, it's a big signal that you shouldn't be doing what you're doing.
-
@firefoxwebdevs going through all the other replies and your lack of response to any of them..
“why are there flaming bags of poop on my porch, and why do they all have different postmarks”
-
@funkylab @flxtr @firefoxwebdevs there's no such thing as good machine translation
-
@twifkak Also notice that Mastodon instances are using LibreTranslate.
Has that been debated as well?
-
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've only got one more firefox uninstall before all my machines and devices are completely free of your AI, ML or whatever you're branding the scraped, stolen data, trained models you see fit to use now and in the future.
-
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 the language and framing of this poll is misleading. i voted for "re-enable translations", but after reading more of the discussions happening in the comments i would have rather voted for "yes". what kind of open data are we talking about? why does this need to be built into the browser instead of being available as an optional 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?
There should be an option to enable/disable translation regardless of any other feature.
-
potayto, potahto
-
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 Is it an off-switch, or isn't it?
"Off-switch except for this PM's pet project" is not an off-switch.
-
@mdavis @firefoxwebdevs I don't like the word "idiot". But a programmer who would use LLM codegen is a programmer with bad judgement. A programmer who has bad judgement cannot spot the errors made by LLM codegen. QED.
Anyway I already got what I wanted: Servo, the web browser which will replace Firefox, has *already* banned "AI" code contributions. So it's only a matter of time before Servo is complete enough for day to day use, and I can delete the AI-infected Firefox from my computer.
Points for "AI infected". Treating AI like a computer virus is a helpful concept.
-
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?
The translation models are opt-in, because each language must be individually loaded. The same approach should apply to every other AI-adjacent function - those using remote services included. Especially those.
@firefoxwebdevs -
@chillicampari @joepie91 fwiw I asked about translation because we're figuring out what to do specifically about translation.
@firefoxwebdevs @chillicampari @joepie91 I don’t think ML translation is what most people are thinking of when they’re complaining about AI. Machine translation has been around for over 20 years at this point, is fairly efficient, and while it makes mistakes (and those mistakes keep real translators if business for things that matter), it’s not the carbon spewing plagiarism machine that generative AI is. When I want an AI kill switch, I mean I don’t want my queries to create “summary” responses, or to add to a corpus that leaks my private information. Similarly, I want my radiologist’s CT software to flag potential issues, but I don’t want it to make up phantom blood clots, either.
-
@mdavis @firefoxwebdevs I don't like the word "idiot". But a programmer who would use LLM codegen is a programmer with bad judgement. A programmer who has bad judgement cannot spot the errors made by LLM codegen. QED.
Anyway I already got what I wanted: Servo, the web browser which will replace Firefox, has *already* banned "AI" code contributions. So it's only a matter of time before Servo is complete enough for day to day use, and I can delete the AI-infected Firefox from my computer.
@mcc @firefoxwebdevs It is a shame that we’ve come to having to ban the use of some tools.
I used an unfortunate word choice, despite an apropos meaning in this context: an idiot is an utterly foolish or senseless person. Programmers should know how to properly use the tools they have. That’s why I’m not all against AI codegen. In the right hands, a tool can create something beautiful and useful. In foolish hands, it can damage.
Learn your craft first. Then use tools properly to enhance it.
-
@firefoxwebdevs @joepie91 i'm a "tech folk". Just give us a version of firefox with zero AI. Translation can either be an extension or not there. We ask of you to supply a base for broSing the web, the rest is what the community delivers.
We won't ask you to integrate ad blockers, but we have them.
We won't ask you to integrate quick procy switchers, but we have them.Stop the feature creep and go back to the roots, make a very good browser with extension support and let people make the rest.
@Fooker @firefoxwebdevs at this point unfortunately I have given up on the main Firefox and switched to Zen Browser (a fork). It's a shame and honestly no shade to the devs bc my decision was made when Mozilla's CEO(s) keep doing dumb stuff.
-
@mdavis it's definitely a complicated topic! I guess it's down to us to figure out a model that best serves most people, while providing options to cover the rest.
@firefoxwebdevs @mdavis small clarification
@firefoxwebdevs introduced the concept of an "AI kill switch"
the "AI kill switch purists" you're talking about don't exist.
No serious person would think this is a good idea because it doesn't make sense. Evident by this "design" stumble at the start line
-
@mcc @firefoxwebdevs It is a shame that we’ve come to having to ban the use of some tools.
I used an unfortunate word choice, despite an apropos meaning in this context: an idiot is an utterly foolish or senseless person. Programmers should know how to properly use the tools they have. That’s why I’m not all against AI codegen. In the right hands, a tool can create something beautiful and useful. In foolish hands, it can damage.
Learn your craft first. Then use tools properly to enhance it.
@mdavis @firefoxwebdevs Well, if LLMs are a tool you use as part of your process of writing code, then I don't want to use any code you created
-
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 don’t think you can make any assumptions then without granular switches that let the user control every facet. In which case, this kill switch is probably less a binary checkbox and more a slider or a series of discrete options. And as a Firefox and Thunderbird user, we are used to lots of toggles and switches under the hood, so I’m fine with that kind of control.
The Firefox AI "kill switch" is not "complicated" except insofar as it's incoherent. it's not "undisclosed nuance" except insofar as it's incoherent.
the "kill switch" doesn't exist.
this is important to keep in mind. once you remember that NONE OF THIS EXISTS, you will realise that every one of the dilemmas you posit is an imaginary problem that follows from incoherent postulates.
e.g. "AI kill switch purists" is not a coherent postulation because the "kill switch" does not exist.
the "kill switch" is a hypothetical proposed in this post:
https://mastodon.social/@firefoxwebdevs/115740500373677782
the "kill switch" is a proposal to satisfy the demand for an opt-in by providing an opt-out. you might think that's a failure to respect the question, and you might even begin to suspect the proposal was in bad faith.
note that Jake, in presenting the kill switch and calling it a kill switch and getting it into all the papers as a kill switch, says he's uncomfortable with the name he's publicised it as. you might think that's oddly incompetent for literally a PR (devrel) person.
the concept as presented imposes multiple false dilemmas.
the LLM stuff should *incredibly obviously* be an extension. this is the purest possible opt-in, despite jake's past attempts to muddy the meaning of "opt-in".
making it an extension is also eminently feasible. There is literally no technical reason it needs to be a browser built-in.
this suggests the reasons are not in any way technical. some person with a name, who has yet to be named, dictated that it would be a built-in. so that's what Mozilla is going with.
why Mozilla went hard AI is entirely unclear. this would have been late 2024? we have no idea who was inspired with this bad idea nor why they were so incredibly keen to force it into the browser.
nor is it clear what Mozilla will do for external LLM services when the AI bubble runs out of venture capital and pops in a year or so, most of the chatbot APIs shut down and whatever remains is 10x the cost at least. but that's a problem for 2027's bonus, not 2026's.
note how the poll provides no option for "no LLM functions built-in to Firefox", in a pathetically transparent attempt to synthesize consent. jake wants to use this poll as evidence of what the user base wants, deliberately leaving out the option he knows directly a lot of them want.
and in conclusion:
1. solve the "kill switch" naming problem by branding it the "brutal and bloody robot murder switch with an option on the executives responsible".
2. make all this shit an extension like they should have a year ago.
3. and your little translator too.
