Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.
-
@firefoxwebdevs But if the ML/AI training work is processing on the device and not is shared off device, and it is in support of a feature like translating a page (which should be prompted/selectable) then what’s the issue? You can say no and nothing happens. Or you can say yes and the worse that happens is you chew up some local power on your laptop or PC. Or are you saying that even though the translation happens on the device, the RESULT of that training data is sent back out?
@mdavis I believe it's a moral stance due to how the models were produced.
-
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 Like many others, I have a metric ton of thoughts on this topic. I might even try writing something to consolidate them.
In the meantime: I don't consider the translation models to be part of the major AI hype I loathe so much. Machine translation of language has been happening for a long time and has proven largely useful, and it lacks the stink of desperation which so many of the generative applications of recent times carry.
While I'm already thinking about it: even the name "AI kill switch" feels bad to think about. I know that "AI" is the buzzword that gets upper management giddy and which the untrained public is now used to hearing, but the fact of the matter is that if you can't "sell" a feature without appealing to buzzwords, your feature wasn't worth the time and effort put into it.
-
@joepie91 agreed.
@firefoxwebdevs we're not in those meetings so we don't know what all is actually included within the AI module suite, or even if that has been fully defined internally at this point, so of course there won't be a clean consensus externally from us on what "it" is and if it should be included or excluded, as it's up to our interpretation.
@chillicampari @joepie91 fwiw I asked about translation because we're figuring out what to do specifically about translation.
-
@firefoxwebdevs Like many others, I have a metric ton of thoughts on this topic. I might even try writing something to consolidate them.
In the meantime: I don't consider the translation models to be part of the major AI hype I loathe so much. Machine translation of language has been happening for a long time and has proven largely useful, and it lacks the stink of desperation which so many of the generative applications of recent times carry.
While I'm already thinking about it: even the name "AI kill switch" feels bad to think about. I know that "AI" is the buzzword that gets upper management giddy and which the untrained public is now used to hearing, but the fact of the matter is that if you can't "sell" a feature without appealing to buzzwords, your feature wasn't worth the time and effort put into it.
@bersl2 I agree it's a meaningless buzzword, but a lot of tech folks are saying they want "no AI" - they're using the buzzword. So the poll is about finding out what folks mean by "no AI".
-
@eckes for that usage pattern the results would probably be even worse with more fabrications. So what are we even doing here?
@tante hu? I guess a slm is much better suited as the old ispell dictionary, I don’t see an issue with offering that (as an option)
-
@mdavis I believe it's a moral stance due to how the models were produced.
@firefoxwebdevs Hookay… then this is less about a local feature or data sharing and more about an overall “Made with AI” concern where nothing related to AI *at*all*ever* taints the user’s browser, in or out. In that case, if the user turns on the AI kill switch, it should totally kill anything having to do with AI for those who take that position.
That’s an issue with these polls — too much undisclosed nuance to be able to answer properly.
-
@angelfeast @twifkak No, I don't think so. It says this (with a takedown compliance process posted afterward)...
License
These data are released under this licensing scheme: PD
We do not own any of the text from which these data has been extracted.
We license the actual packaging of these parallel data under the Creative Commons CC0 license ("no rights reserved").@tasket @angelfeast https://paracrawl.eu/moredata says "This is a release of text from Internet Archive.... The project also used CommonCrawl which is already public." Those crawls quite famously/infamously include copyrighted content. I don't see anything to suggest they filtered those datasets for public domain annotations. (Not that such an annotation would be enforceable, but it would at least be an indication of intent.)
-
@firefoxwebdevs Hookay… then this is less about a local feature or data sharing and more about an overall “Made with AI” concern where nothing related to AI *at*all*ever* taints the user’s browser, in or out. In that case, if the user turns on the AI kill switch, it should totally kill anything having to do with AI for those who take that position.
That’s an issue with these polls — too much undisclosed nuance to be able to answer properly.
@firefoxwebdevs But wait… what if the developers used AI to help develop the code in the browser itself? Does that mean AI kill switch purists should then rather not even use the product at all?
-
@firefoxwebdevs I can only speak for myself of course, but I'm someone who is strongly opposed to sneaky approaches, like hiding things in submenus or requiring people to go back later to disable new things, for example. And I'm also strongly opposed to basically everything in the current generation of "AI" (LLMs, GenAI, etc.) - but personally I wouldn't consider this sneaky, as it's immediately visible that there's a second choice to make, at the exact moment you disable "AI".
Of course if that stops being the case and the second option gets hidden behind an "Advanced..." button or foldout for example, it would be sneaky. But in the way it's shown in my mockup, I would consider it fine as it's both proactively presented and immediately actionable.
(I do still think that exploitative "AI" things should be opt-in rather than opt-out, but it doesn't seem like that's within the scope of options that will be considered by Mozilla, so I'm reasoning within the assumption of an opt-out mechanism here)
@joepie91 they will be opt-in, but different people have different opinions about what that means. For us, it means models won't be downloaded or data sent to models without the user's request.
However, some folks have said the only meaningful opt-in would be a separate binary for the browser-with-AI, or even having to compiling it manually.
-
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 stop putting AI in your products, full stop. The machine translations made with the help of native speakers is 1000x better than the slop you're feeding us
-
@zzt I posted this poll after a meeting where we discussed the design of the kill switch, and there was uncertainty around translations. I want to make sure the community's voice is represented in these discussions.
Don‘t „design a kill switch“. Just put all the slop features into seperate extensions.
Then see how many people will bother to install them, so you get a realistic idea for the actual demand. -
@firefoxwebdevs But wait… what if the developers used AI to help develop the code in the browser itself? Does that mean AI kill switch purists should then rather not even use the product at all?
@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.
-
@tasket @angelfeast https://paracrawl.eu/moredata says "This is a release of text from Internet Archive.... The project also used CommonCrawl which is already public." Those crawls quite famously/infamously include copyrighted content. I don't see anything to suggest they filtered those datasets for public domain annotations. (Not that such an annotation would be enforceable, but it would at least be an indication of intent.)
@tasket @angelfeast It's not clear to me that I'm looking at the right place. Is this the data being used by Mozilla? I'm hoping that could be resolved by more than the 10 minutes of research I spent on it. I'd like even more for it to require much less research to understand the supply chain of a product offered as a public service. I've also got lots of reasons not to give them the benefit of the doubt here.
-
@firefoxwebdevs I don't care. Local translation in FF is on the level of free early 2000s web translators. So maybe just remove it and add it again, when it's production ready
@flxtr
I use it daily and in general it's good enough to understand an article content without having to use an online translator. I love this feature!
@firefoxwebdevs -
@m0rpk @firefoxwebdevs quite honestly, you're off the mark, **a lot**.
A browser with a built-in translator is a door opener for the open web for so many people that don't read English well enough to benefit from the dominant corpus of technological, cultural and scientific websites.
Firefox could indeed remove that functionality and instead of letting people translate websites on their phone make them use the google translate app that directly. Congrats on how you've advocated for the open web.@funkylab Mozilla only have to make that functionality possible to add via a plugin for people who want it. That way user choice, accessible web translation, and separation between core and optional browser functions and are all satisfied.
There is nothing to say Mozilla have to deliver that plugin - and nothing to stop them from doing so either. Or anyone else.
I'd argue that's how the open web should work. Not mandating optional behaviour within the browser itself.
-
@firefoxwebdevs@mastodon.social I believe it'd be better if Firefox stopped referring to unwanted slop like chatbots with meaningless marketing terms such as 'AI' instead
@mkljczk
Wdym? It's a translator, not a chatbot
@firefoxwebdevs -
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 grow a pair and assert your products’s vision.
The loudest people are are unreasonable and do not understand what they actually want.
-
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 what exactly do you refer to as „open data”?
-
@funkylab Mozilla only have to make that functionality possible to add via a plugin for people who want it. That way user choice, accessible web translation, and separation between core and optional browser functions and are all satisfied.
There is nothing to say Mozilla have to deliver that plugin - and nothing to stop them from doing so either. Or anyone else.
I'd argue that's how the open web should work. Not mandating optional behaviour within the browser itself.
@m0rpk @firefoxwebdevs mozilla did deliver this as a plugin in the beginning. What's your point? "Don't make the web open, unless it's something that I approve?"
-
@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 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.