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@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”.)
-
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 “Block AI Enhancements” should be checked by default, ya ding dongs.
-
@raymaccarthy @firefoxwebdevs It would need to cater for not only Windows and macOS (possibly multiple versions of both) as well as quite a few different Linux desktops. At the same time, it would need to have light and dark modes for all.
With Fx having the same broad style across most platforms feels much better to support and easier for contributors to work on.
@plwt @firefoxwebdevs
Only if your SW is broken and simply getting a window, then drawing its own controls. Perhaps years ago Firefox was changed to use its own renderer and CSS instead of system API calls for all controls etc.
I can even do a custom theme on Mint+ Mate, Win98, XP, Win7 and well written programs look native.How can you even know the Look & Feel? The entire concept of Firefox GUI must now broken.
That would explain the garbage scrollbars.
-
@raymaccarthy @firefoxwebdevs It would need to cater for not only Windows and macOS (possibly multiple versions of both) as well as quite a few different Linux desktops. At the same time, it would need to have light and dark modes for all.
With Fx having the same broad style across most platforms feels much better to support and easier for contributors to work on.
@plwt @firefoxwebdevs
Short answer, if you think that you are completely wrong about how a program should do a gui. You are writing about something with a custom skin, not a well behaved program. Even a QT based program can follow an arbitrary OS look and feel. Java can. So instead of creating and styling a funky scrollbar you FW tells OS: Scrollbar here this orientation & length.Winamp was 1st I encountered ignoring OS.
