AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs YES! Thank you.
-
Immediately restore the work of japanese language translators that you paved over with AI slop
AI Controversy Forces End of Mozilla’s Japanese SUMO Community
The SUMO Japanese team quits en masse, accusing Mozilla’s AI system of erasing years of community translation work.
Linuxiac (linuxiac.com)
@ambiguous_yelp @firefoxwebdevs I was convinced the damage is irreparable. Wasn't everything just deleted?
-
@firefoxwebdevs the tiny minority of people who choose to use firefox at all dont want AI. it should be off by default if its being shoehorned in anyway, but since mozilla doesnt care the least they could do is not neuter the name.
"kill switch" bites, "AI controls" licks
EDIT: misread formally as formerly, still dont like this
also, several people in the replies here point out that firefox questions the users choice after they already toggled the kill switch. im normally fine with software giving me a warning if it could potentially mitigate unintended consequences, particularly when it comes to security and/or privacy. in this case, a warning message would be more appropriate if you turned AI features ON, not OFF. i think thats why the demo video especially irks me
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs@mastodon.social Well, it should have been there first and disabled by default, but at least it’s here now. Cool.
-
@ambiguous_yelp @firefoxwebdevs I was convinced the damage is irreparable. Wasn't everything just deleted?
@nieuemma idk but I'm never going to let them forget it, maybe they'll make a statement that its impossible
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs @alternativeto Nope, thanks.
-
-
@firefoxwebdevs @alternativeto Nope, thanks.
@iam @alternativeto That's the thing about choice, 'nope' is an option.
-
@iam @alternativeto That's the thing about choice, 'nope' is an option.
@firefoxwebdevs @alternativeto No, the choice is to use something else that doesn't have AI (which nobody asked for), and which should be disabled by default, not enabled. Read the room.
-
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs Why isn't it enabled by default?
-
@sarah I'm not sure what we can do to convince you other than hold the promise over time.
@firefoxwebdevs @sarah maybe start by talking to your CEO:
> Firefox will remain our anchor. It will evolve into a modern AI browser and support a portfolio of new and trusted software additions.
https://blog.mozilla.org/en/mozilla/leadership/mozillas-next-chapter-anthony-enzor-demeo-new-ceo/This vision is a huge reason why people are not convinced. That, and how getting Firefox to implement these controls at long last felt like pulling teeth.
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs You have lost all sense and sensibility. You have lost the plot. You are bleeding users and your idea to get them back is to introduce features NOBODY wants. You used to be a good alternative to corporate browsers, but you have become the evil you were fighting against. Good riddance.
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs pretty nice, wish more software allowed this
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs@mastodon.social I think it would be better if the toggle was somewhere in the main UI or hamburger menu, instead of buried in the settings tab.
I think it would also make sense to have an on-boarding prompt to enable/disable AI when people open the browser the first time or update to the version this is added.
As other people are pointing out, the default if noone has explicitly turned it on should be off. -
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs This will just make firefox worse. aiSlop is already crashing and on the way out. Do the right thing here, get rid of it.
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs nice
I think if it runs locally, AI features are quite useful. E.g. I use translations daily. Tab grouping and image alt texts would also be great. Unfortunately they are probably not eligible to run locally.
-
@fabio @firefoxwebdevs survey only shows a tiny fraction of the total userbase. why it should influencethe default?
@wojtek Interesting that you have a Vivaldi.net account, a browser that famously doesn’t include any AI features. Your question is a bit strange in this context, or maybe it’s just a bad attempt at being a contrarian.
-
@firefoxwebdevs @tay @madduci that feels more like "hide" than "block" to me
-
@duke_of_germany @firefoxwebdevs whereas the poll I actually ran, which shows how target users of the feature view translation, was practically useful.
@jaffathecake @duke_of_germany @firefoxwebdevs .. thank you Jake for at least trying to do SOMETHING constructive here despite Moz leadership’s stance on AI. I can live with a BLOCK AI button if BLOCKED is default (although I’d personally prefer your limited resources were spent elsewhere).
Given you (accurately) mentioned Mastodon is skewed against AI, I’m curious what non-Mastodon data does Moz have on actual interest for AI in Mozilla? (Beyond “everyone is doing it”.)
