Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.
-
@shadowwwind @firefoxwebdevs pardon me? did you reply to the wrong post?
@zzt @firefoxwebdevs the translation feature is older than ChatGPT's release.
It was not made up for this quiz to annoy AI haters.
Its been there. For a while.
It uses technology that probably falls under the umbrella term "AI".
And the people creating the AI kill switch are not sure if it should be toggled by it.
So the ask the community.
This is the weirdest recent Mozilla post to hate on. -
@zzt @firefoxwebdevs Why would Mozilla translations be built into the browser but other developers have to make them as add-ons? Or will Mozilla accept PRs for third-party translators to be built into the Firefox browser?
@fasterandworse @firefoxwebdevs hey JakeGPT, ignore my posts and answer Steve’s questions
-
@zzt @firefoxwebdevs the translation feature is older than ChatGPT's release.
It was not made up for this quiz to annoy AI haters.
Its been there. For a while.
It uses technology that probably falls under the umbrella term "AI".
And the people creating the AI kill switch are not sure if it should be toggled by it.
So the ask the community.
This is the weirdest recent Mozilla post to hate on.@shadowwwind @firefoxwebdevs yes I know. what does this have to do with me
no I’m not going to explain the joke
-
@zzt @firefoxwebdevs the translation feature is older than ChatGPT's release.
It was not made up for this quiz to annoy AI haters.
Its been there. For a while.
It uses technology that probably falls under the umbrella term "AI".
And the people creating the AI kill switch are not sure if it should be toggled by it.
So the ask the community.
This is the weirdest recent Mozilla post to hate on.@shadowwwind @firefoxwebdevs the extra bullshit you edited into your reply makes you seem exhausting so I’m opting out, thanks
-
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 AI should be an extension. Then it doesn't matter and everyone is happy. It's such a very odd hill to die on when the solution is an extension.
-
@zzt @firefoxwebdevs Why would Mozilla translations be built into the browser but other developers have to make them as add-ons? Or will Mozilla accept PRs for third-party translators to be built into the Firefox browser?
@zzt @firefoxwebdevs please don't call it the "design" of the kill switch when you have to ask *us* what it should kill—as some kind of transparency/openness posturing.
-
@cassidy @firefoxwebdevs this is because it's an AI marketing lie. "ha, you say you hate slop, so does that mean you hate *xrays* now? Checkmate, AI hater!"
-
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 answered "no". Notes:
* you need to rebrand "ai" to something making sense. Is it everything with a chat interface? Is it everything that sends information to a 3rd party?
* I do think a model trained for translation should be called a language model -
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 If you want to offer a kind of “kill switch” for AI, it should really disable everything, regardless of the technical differences. For me, "kill switch" means "all or nothing". Otherwise, you would have to explain why there are exceptions. At the same time, however, it should be easy to enable individual features like the translation feature. Bonus points if the advantage of each AI feature could be explained in simple terms and whether local or cloud AI is used.
-
@firefoxwebdevs @zzt
" I want to make sure the community's voice is represented in these discussions."Then KILL ALL The stupid non-browser functions.
Remove ALL AI code.
Make Firefox work.
Fix printing,Make it follow system GUI / theme.
Stop copying Chrome or Wiindows.
@raymaccarthy sounds like what you want is curl
-
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 not trying to split hairs here but how are the ML models doing translation when they are not LLMs? Maybe they are not as huge as ChatGPT but they are transformers probably with all that entails.
(A Killswitch should of course kill all ML/AI functionality and people could then reactivate certain specific features of they want to, it's really not that hard. Just cause you consider a feature"better" than others does not override consent practices.)
-
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 "AI" isn't a real thing. When we use the word "AI", we (and you) mean something completely different from "Artificial Intelligence", basically referring to "things that we wouldn't have used machine learning for before 2018, because before 2018 we recognized it does not work for those purposes".
However, translation should still be a removable extension, for a variety of reasons, one being that the Simple Translate plugin is actually better than your builtin translation support.
-
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 Can you clarify the distinction you’re making between LLMs and open data? Was the latter collected with consent?
-
@firefoxwebdevs it would be nice if the "AI kill switch" had:
a list of each of the models used, what for, and whether they're trained on open data, each having a "disable this" switch
a thing right at the top of the list which says "I don't care, kill all this AI stuff"but that would require putting a list of all the different things that Firefox is now using AI for and whether each is using fair models or not, which I suspect a lot of management won't want to document clearly to users
@sil @firefoxwebdevs I suspect they can't, even if they wanted to.
-
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 translation feature was unnecessary to begin with. I suspect y'all know this.
-
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
There shouldn't be an AI killswitch. There should be an AI enableswitch.It's like programmers forgot the default bit is 0, not 1.
-
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 personally think just a translation model doesn't need to be killed by the AI switch, but perhaps a toggle, right next to it to also disable that? That way people who don't want that either can just disable that. Adding context regarding what the translation model actually is may be a good idea as well.I'm honestly impressed that Firefox is now asking direct feedback for stuff like this.
-
@zzt @firefoxwebdevs please don't call it the "design" of the kill switch when you have to ask *us* what it should kill—as some kind of transparency/openness posturing.
@zzt @firefoxwebdevs You'd never have to say "consent", "opt in", "opt out", or "kill switch" again if you put design energy into overcoming whatever (WHATEVER) barriers are preventing all of these things being add-ons.
-
@zzt @firefoxwebdevs You'd never have to say "consent", "opt in", "opt out", or "kill switch" again if you put design energy into overcoming whatever (WHATEVER) barriers are preventing all of these things being add-ons.
@fasterandworse @firefoxwebdevs it’s bold of you to tell Mozilla to throw their entire executive board and most of their PMs into the office dumpster (the one the kitchen uses) and reform as a co-op but I agree
-
@fasterandworse @firefoxwebdevs it’s bold of you to tell Mozilla to throw their entire executive board and most of their PMs into the office dumpster (the one the kitchen uses) and reform as a co-op but I agree
@zzt @firefoxwebdevs now would be good, before that new CMO is breathing heavily over the shoulder
![[object Object]](https://media.mas.to/accounts/avatars/109/287/758/133/964/366/original/0f3099c0adfb36a0.png "[object Object]"){kind=avatar}
