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?

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?

@davidgerard @theogrin @mdavis @firefoxwebdevs "No AI, and Anthony Enzor-DeMeo resigns in disgrace."

@theorangetheme @theogrin @mdavis @firefoxwebdevs also the new AI CMO. also whichever person started this ball rolling and got Anthony in.

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?

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?

@mdavis @firefoxwebdevs

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.

@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.

@firefoxwebdevs then I think it comes down to- is translation specifically considered "AI" by your own definition (not personally your definition, how it is treated internally by Mozilla)?

If it is treated and handled as "AI" then yes, following the idea of including what is defined by Mozilla as "AI" into the "AI kill switch" it should be disabled when the "kill switch" is toggled.

@joepie91

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?

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?

@chillicampari @firefoxwebdevs @joepie91 I’m kindof amazed that Mozilla can’t distinguish which changes led to the backlash. I think that’s why this whole thing feels more like putting on a show than like a genuine attempt at reform.

The timing alone makes it clear that the builtin translation was not the issue. Sure, moving it to a plugin would be an improvement, and requiring user action to enable it would be smaller improvement, but that was the case before.
️

@chillicampari @firefoxwebdevs @joepie91 ️ The main issue is Mozilla as an organization embracing the lie that LLMs possess something resembling human intelligence, welcoming the full variety of harms caused by their implementation and use, integrating their use into unnecessary “features”, and enabling those “features” both by default and reverting them to enabled after updates.
️

@chillicampari @firefoxwebdevs @joepie91 ️ After y’all lied to us, encouraged harm to us, set us up to add to that harm, and reverted us to that setup after we opted out, we don’t trust you anymore.

It’s alright to address lesser issues like the builtin translation, but that doesn’t address the main issue or rebuild any trust.
️

@chillicampari @firefoxwebdevs @joepie91 ️ The best thing you could do in Firefox is to completely remove the “AI” “features” that are built on the lie and contributing to the harm. The next best would be to move them to plugins that are not installed by default. The next best is the “kill switch”, but with “killed” as the default, and ideally, as you say, not a single switch but a set of them.
️

@firefoxwebdevs I also like the idea of having all such features as extensions rather than built in features, so they can be explicitly turned on by people who want to.

Would really make the product clearly stand out from others

@davidgerard @theogrin @mdavis @firefoxwebdevs I fixed it.

Do you want AI slop in Firefox?

@theorangetheme @davidgerard @theogrin @mdavis @firefoxwebdevs If Firefox isn't willing to cut out AI (fuck levers and knobs), then stop calling it Firefox.

Let the legacy of user trust and privacy end and stop lying to people. Mozilla is a company, the browser is a product, and you (Moz Org and Foundation) have no interest in consumer rights.

Mozilla's battlecry should be "Shut up, download the free browser, and let us watch everything you do." Because we're not your customers anymore. Stockholders and advertisers are.

Your next poll: How can (browser not Firefox) bring you ads and save you money when shopping?" That is what you want to ask, so do 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?