AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.

[firefoxwebdevs@mastodon.social]

@iam @alternativeto That's the thing about choice, 'nope' is an option.

[iam@ernestoacosta.org]

@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.

[firefoxwebdevs@mastodon.social]

@ArneBab @vex @dveditz now you're just trying to make me feel better

[jernej__s@infosec.exchange]

@firefoxwebdevs Why isn't it enabled by default?

[rysiek@mstdn.social]

@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.

[randamumaki@mstdn.social]

@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.

[calx@infosec.exchange]

@firefoxwebdevs pretty nice, wish more software allowed this

[kitsunevixi@sakurajima.social]

@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.

[workingclassgames@tech.lgbt]

@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.

[alvan@social.lol]

@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@cosocial.ca]

@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.

[cubeofcheese@mstdn.social]

@firefoxwebdevs @tay @madduci that feels more like "hide" than "block" to me

[wook@fosstodon.org]

@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”.)

[garretble@mastodon.social]

@firefoxwebdevs “Block AI Enhancements” should be checked by default, ya ding dongs.

[raymaccarthy@mastodon.ie]

@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@mastodon.ie]

@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.

[justin@toot.io]

@firefoxwebdevs you should've have needed to be the first, you should never have added things users don't want. Make it plugins, then users can choose to add disgusting "AI" "features". @raymaccarthy

[budududuroiu@hachyderm.io]

@mike @firefoxwebdevs Preference falsification, it's seen as socially condemnable to be ok with AI, especially in the circles that Mozilla frequents, so I'm not surprised public comments trend negative. Given they've sent an anonymous survey out, I'm pretty sure the balance is split between the no-AI and AI everything camps.

I don't get the vitriol towards Mozilla, at least not for this change, they literally show you how to turn off their AI features

[sb@metroholografix.ca]

@firefoxwebdevs
It must be really uncomfortable for you and your team to see this outpouring of opposition to the direction you are being lead.

I hope you know its not personal. But you must understand that it is deadly serious.

Please, hear us as we all shout in unison: STOP WASTING MONEY AND ENERGY ON GRIFTS AND JUST MAKE THE BEST DAMN BROWSER YOU CAN MAKE.

[drewtowler@mas.to]

@firefoxwebdevs If you physically and permanently remove all AI-related code from Firefox, I might start using it again. Not until.