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

[oberstenzian@mastodon.social]

@firefoxwebdevs Sounds great. Fuck your browser.

[wariat@mastodon.social]

@firefoxwebdevs
Better late than even later… thank you!

[wariat@mastodon.social]

@wojtek
Because optIn is better than optOut.

@fabio @firefoxwebdevs

[ranlvor@queerchen.de]

@firefoxwebdevs YES! Thank you.

[nieuemma@mastodon.de]

@ambiguous_yelp @firefoxwebdevs I was convinced the damage is irreparable. Wasn't everything just deleted?

[oay@mastodon.social]

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

[breizh@pleroma.breizh.pm]

@firefoxwebdevs@mastodon.social Well, it should have been there first and disabled by default, but at least it’s here now. Cool.

[ambiguous_yelp@veganism.social]

@nieuemma idk but I'm never going to let them forget it, maybe they'll make a statement that its impossible

[iam@ernestoacosta.org]

@firefoxwebdevs @alternativeto Nope, thanks.

[firefoxwebdevs@mastodon.social]

@ArneBab @vex @dveditz haha yeah it's 22:30 here. Sigh.

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