Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.
-
@firefoxwebdevs your translations are bad and you should feel bad. both about them and about this poll.
@rose_alibi
i like the #firefox #translation because it helps make the web less US-centric by making international web more accssible.#firefox #translations actually respect privacy, as opposed to #googletranslate, so i can use them for the government websites that i don't always understand, because i'm not swedish speaker.
i don't get why this feature is lumped in with the privacy nightmare chat bots?
-
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 LLM is quantity, not quality. I don't see a distinction between "Open Data" and corporate raiding of the Internet, it's the same issue.
Aggregating data to replace logic until it can replace logic a percentage of the time is the issue. It's reintroducing a solved problem because shareholders want AI down everyone's throats.
-
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 mean realistically, we have about:config at home, and y'all are already not respecting that
why the future "KILL SWITCH" carrot? it just comes across like a Musk promise
-
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 frame of this question is risible.
I am begging you to just make a web browser.
Make it the best browser for the open web. Make it a browser that empowers individuals. Make it a browser that defends users against threats.
Do not make a search engine. Do not make a translation engine. Do not make a webpage summariser. Do not make a front-end for an LLM. Do not make a client-side LLM.
Just. Make. A. Web. Browser.
Please.
-
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?
Please just create a very good browser and drop all of the AI bollocks.
It's not helping. No-one wants it. Improve the rendering engine and fix bugs.
Please!
-
@firefoxwebdevs The frame of this question is risible.
I am begging you to just make a web browser.
Make it the best browser for the open web. Make it a browser that empowers individuals. Make it a browser that defends users against threats.
Do not make a search engine. Do not make a translation engine. Do not make a webpage summariser. Do not make a front-end for an LLM. Do not make a client-side LLM.
Just. Make. A. Web. Browser.
Please.
-
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 Said translation should be an opt-in extension you can install if you want it. Not a core component at all.
-
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 dunno, deleted as soon as you added Artificial Intelligence and never came back.
-
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 as a user, I like and use translation. Having one app render and translate content makes sense to me.
I like how you do it (incl on-device, on-demand and privacy-preserving, and open data (assuming it means not copyrighted?)).
Because of both, it is clearly different from other “AI” to me, even if it technically would use language models that are large, and this poll makes sense to me.
It's tricky, I voted, but wasn't super sure. I think granular controls would be great.
-
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 appreciate that you're asking us Firefox users for our opinion on a feature. Keep doing this please.
-
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 come on man.
-
@firefoxwebdevs I mean realistically, we have about:config at home, and y'all are already not respecting that
why the future "KILL SWITCH" carrot? it just comes across like a Musk promise
@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”
-
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 love the on-device translations and don't really want the other stuff.
Yes the kill switch should ideally be a settings page with many toggles for all ML-like features and an obvious master enable/disable-all toggle at the top of the page. -
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 think the best might be to generalize the "yes, but" answer.
Have a set of toggles, one for each feature. Whatever the default state is:
When I (the user) press the TURN OFF AI button or whatever the mechanics are, force them all to (as actively selected) OFF and make the default for any newly added such features also OFF (by implication of the default).
Let me manually toggle a given, specific feature back ON if I want to, *while* keeping the rest including default OFF.
½
-
@firefoxwebdevs I think the best might be to generalize the "yes, but" answer.
Have a set of toggles, one for each feature. Whatever the default state is:
When I (the user) press the TURN OFF AI button or whatever the mechanics are, force them all to (as actively selected) OFF and make the default for any newly added such features also OFF (by implication of the default).
Let me manually toggle a given, specific feature back ON if I want to, *while* keeping the rest including default OFF.
½
@firefoxwebdevs I realize that there's a lot of very vocal people about this, and you might note that I specifically say "whatever the default state is". *At least put the user in a position of being able to easily control these features* and turn them on or off per their preference. For some people, some of those features can be genuinely useful (as illustrated by some replies in this very thread, even). Not *having* to throw the baby out with the bathwater is advantageous.
2/2
-
@firefoxwebdevs What do you mean "open data"? https://firefox-source-docs.mozilla.org/toolkit/components/translations/resources/01_overview.html points to https://browser.mt/ points to https://paracrawl.eu/index.php which says "We do not own any of the text from which these data has been extracted."
-
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 Of course, ML translation suffers many of the same problems. Also, why are you integrating translation as a core browser feature? Seems more like an extension feature.
-
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 Thanks for involving the community in this! I've found the translation feature really useful even if the results aren't state-of-the-art!
I agree with other commenters that there's an issue with the term "AI", but I don't have any suggestions.
To match my current preferneces, I would like an AI kill switch to keep translations with local models, but disable LLM chatbots, summarizers, and agents.
-
-
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 My closest answer would be "no", but I think the question is kind of mis-phrased here, and that's probably going to lead to a confusing and potentially misleading outcome.
The problem that people have is not with "AI" as a generalized category, but with the current generation of thieving, climate-destroying, grifting systems that are marketed as AI to an overwhelming degree - notably LLMs and "generative AI", but really anything with those inconsiderate properties.
If your kill switch is presented as an "AI kill switch", then depending on the person they're either going to understand that as "exploitative tech", or as "machine learning", and so make different assumptions as to whether local translation is included in that.
So I think you'll have to be a lot more explicit about what you mean; either by describing clearly what the kill-switch includes, or what it excludes, right in the place where the option is offered. Otherwise it's damned if you do, damned if you don't; depending on whether you include translations, either one or another group is going to be upset with the unexpected behaviour.
So, ethically, if the translation feature is built on ethically collected data, and it has no outsized climate impact, then I would not consider it something that needs to be included in a "get rid of all of it" kill switch. But to convey this clearly to users, both that and why it isn't included should be explained right there with the button, with potentially a second-step option to disable it anyway if someone still feels uncomfortable with it.
That way you've transparently communicated to users and shown that you have nothing up your sleeve by immediately and proactively offering them an option to disable that, too, if they have already shown interest in removing "AI" features.
