AI Controls (formally 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
-
AI Controls (formally '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 Oh boy! The feature we shouldn't need, to kill off the features we never asked for!
-
AI Controls (formally '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/
I know you'll likely get a whole bunch of negative feedback on Fedi for not going even further, but at least this appears to *clearly and unambiguously* put the user in control in a way that does not require digging through about:config settings and worrying about what an upgrade will do. So I am cautiously optimistic about this.
Can you say anything about when those of us who are on the ESR update track can expect to see this? Will there be a policy setting to control this?
-
AI Controls (formally '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 not ship a version with ZERO AI? -
@ArneBab "block" was picked deliberately, as it's removing all entry points to the feature, not just disabling the feature (e.g. disabled buttons are still there, but these are BLOCKED).
It was important to show the features individually so you can control them individually. E.g. translation is something people explicitly wanted to be able to re-enable https://mastodon.social/@firefoxwebdevs/115849251057488746
@firefoxwebdevs @ArneBab
No, you've lost the plot! -
AI Controls (formally '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
And WHY were these "True" by default?
Why once even re-enabled?Mozilla isn't trustworthy.
The so-called ML is an invasion of privacy and a waste of computing resource.
Go back to a Classic Firefox that's ONLY a browser and repects OS GUI look & feel instead of copying Google.
-
AI Controls (formally '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 "AI is changing the web, and people want very different things from it. We’ve heard from many who want nothing to do with AI. We’ve also heard from others who want AI tools that are genuinely useful."
Have you? Because I've literally only heard the former. See e.g. virtually every one of the 966 comments on https://connect.mozilla.org/t5/discussions/building-ai-the-firefox-way-shaping-what-s-next-together/td-p/109922
-
@firefoxwebdevs
And WHY were these "True" by default?
Why once even re-enabled?Mozilla isn't trustworthy.
The so-called ML is an invasion of privacy and a waste of computing resource.
Go back to a Classic Firefox that's ONLY a browser and repects OS GUI look & feel instead of copying Google.
@raymaccarthy about:config isn't intended to be for user settings. That's why we've created a dedicated AI controls page, and we're the first to do so.
-
AI Controls (formally '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/
credit where credit is due
I'm still going to use Librewolf as trust on telemetry and ad-partnerships is not yet restored
-
I know you'll likely get a whole bunch of negative feedback on Fedi for not going even further, but at least this appears to *clearly and unambiguously* put the user in control in a way that does not require digging through about:config settings and worrying about what an upgrade will do. So I am cautiously optimistic about this.
Can you say anything about when those of us who are on the ESR update track can expect to see this? Will there be a policy setting to control this?
@mkj I don't know the answer to this off the top of my head, but I'll find out and get back to you.
-
AI Controls (formally '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 is FANTASTIC! Thank you guys for listening to feedback!
-
@raymaccarthy about:config isn't intended to be for user settings. That's why we've created a dedicated AI controls page, and we're the first to do so.
@firefoxwebdevs
You are missing the point!The features should not exist! So then no need for a master switch in the main settings.
Firefox has got so broken it needs loads of settings changed in About.config and even then is LESS USEABLE than 10 or 15 years ago.
I've been using Websites since 1994. Mosaic, Netscape, Firefox.
Of course I've used most of the others.
-
@ArneBab "block" was picked deliberately, as it's removing all entry points to the feature, not just disabling the feature (e.g. disabled buttons are still there, but these are BLOCKED).
It was important to show the features individually so you can control them individually. E.g. translation is something people explicitly wanted to be able to re-enable https://mastodon.social/@firefoxwebdevs/115849251057488746
@firefoxwebdevs so i "re-enable" stuff I want after "blocking"?
re-enable calls for "disable" as the other part.
What that "block" does is "set default to disable" and "disable all" that we all know from the law-compliant cookie-banners.
Or rather: "make AI opt-in".
Suggestion that does not feel manipulative:
Button [disable all] ⇒ disables all AI options.
Added Option: [enable future AI features by default] ← gets disabled alongside the individual options when clicking [disable all].
-
@firefoxwebdevs so i "re-enable" stuff I want after "blocking"?
re-enable calls for "disable" as the other part.
What that "block" does is "set default to disable" and "disable all" that we all know from the law-compliant cookie-banners.
Or rather: "make AI opt-in".
Suggestion that does not feel manipulative:
Button [disable all] ⇒ disables all AI options.
Added Option: [enable future AI features by default] ← gets disabled alongside the individual options when clicking [disable all].
@ArneBab it doesn't just disable all existing feature, it also auto-disables future AI features, or 'blocks' them from even appearing in the UI.
-
AI Controls (formally '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 Too little. Too late.
-
R ActivityRelay shared this topic
-
AI Controls (formally '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 is so sad to watch.
Y'all need to pause and reflect on *why* the vast majority of your loyal user base wants nothing to do with your AI slop "features."
It's bad business. If you have to develop a kill switch for a whole class of feature because it's so toxic, maybe the need for a kill switch isn't the actual issue. Yeah?
Come on, we all know you're not this oblivious. Stop lying to yourselves and us.
-
N Marianne shared this topic
