AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
-
@kittyjynx @firefoxwebdevs
> a browser not infected with Google, Apple, and now Firefox codePale Moon? https://en.wikipedia.org/wiki/Pale_Moon
@Ostrobothnia @firefoxwebdevs Thanks for the rec! I just installed it and will be test driving for a bit!
-
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 yay! \o/
-
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/
What Mozilla did:
️What the users actually wanted:
️Duke of Germany 💫 (@duke_of_germany@mastodon.gamedev.place)
Let's ask the real question: Firefox users, do you want any AI directly built into Firefox, or separated out into extensions? @firefoxwebdevs@mastodon.social @davidgerard@circumstances.run @tante@tldr.nettime.org #Firefox #InformedConsent [ ] I want AI built into Firefox [ ] I want AI separated into extensions [ ] Mozilla should not focus on AI features at all
Gamedev Mastodon (mastodon.gamedev.place)
-
@fabio @firefoxwebdevs survey only shows a tiny fraction of the total userbase. why it should influencethe default?
@wojtek @fabio @firefoxwebdevs then why do a survey?
-
@nuintari @firefoxwebdevs Don’t write "we“ where you should have written "I“. I find many AI features useful.
-
@mike @firefoxwebdevs "AI is changing the web" is also certainly one way of describing the unending tide of SEO-optimized slop coating every surface that's made using the web as a source of information and knowledge virtually impossible.
@alahmnat @mike @firefoxwebdevs SEO optimized shit came long before AI and has nothing to do with it. This myth that the web was a healthy place before LLMs came is annoying.
-
@mkj the next major ESR release is 153.0esr. That will include all features between Fx140 and Fx153 and is scheduled to ship on 2026-06-21.
In terms of policy: https://bugzilla.mozilla.org/show_bug.cgi?id=2005805
@firefoxwebdevs Thank you!
-
@alahmnat @mike @firefoxwebdevs SEO optimized shit came long before AI and has nothing to do with it. This myth that the web was a healthy place before LLMs came is annoying.
@Mastokarl No, the web wasn't in great shape before 2022, but LLMs have made the problem a billion times worse.
-
@alahmnat @mike @firefoxwebdevs SEO optimized shit came long before AI and has nothing to do with it. This myth that the web was a healthy place before LLMs came is annoying.
@Mastokarl @alahmnat @firefoxwebdevs I don't think anyone has illusions that the web was free of bullshit before LLMs.
But LLMs have made it vastly vastly easier to generate bullshit, and as an absolutely inevitable result, LLM-generated bullshit is now drowning out everything else.
This seems pretty uncontroversial to me.
-
@mausmalone also, the way this button is being presented feels like we are enabling a sparkly new thing? Kind of the opposite of what it is doing
@GuillaumeRossolini @firefoxwebdevs Yeah ... it's a very strange user experience to turn on turning off AI.
I still really think the Standard/Strict/Custom Privacy UI design is a good template.
-
What Mozilla did:
️What the users actually wanted:
️Duke of Germany 💫 (@duke_of_germany@mastodon.gamedev.place)
Let's ask the real question: Firefox users, do you want any AI directly built into Firefox, or separated out into extensions? @firefoxwebdevs@mastodon.social @davidgerard@circumstances.run @tante@tldr.nettime.org #Firefox #InformedConsent [ ] I want AI built into Firefox [ ] I want AI separated into extensions [ ] Mozilla should not focus on AI features at all
Gamedev Mastodon (mastodon.gamedev.place)
-
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 I'll be switching remaining friends and family members over to Librewolf and/or Vivaldi before this update drops
AI in the browser is a disaster waiting to happen and it's sad to see Mozilla think so little of its users opinions
-
Regarding "[...] I'm not personally in a position to action results of such a poll":
Are you in the position to bring up the results of such a poll in a meeting with your team & boss?
And if so, did you?
-
Regarding "[...] I'm not personally in a position to action results of such a poll":
Are you in the position to bring up the results of such a poll in a meeting with your team & boss?
And if so, did you?
@duke_of_germany @firefoxwebdevs they're aware of the sentiment. I'm sure you're aware that Mastodon has a high representation of folks who don't like AI, so presenting evidence that Mastodon users don't like AI is kinda… well… not really useful.
-
@duke_of_germany @firefoxwebdevs they're aware of the sentiment. I'm sure you're aware that Mastodon has a high representation of folks who don't like AI, so presenting evidence that Mastodon users don't like AI is kinda… well… not really useful.
@duke_of_germany @firefoxwebdevs whereas the poll I actually ran, which shows how target users of the feature view translation, was practically useful.
-
@firefoxwebdevs I'll be switching remaining friends and family members over to Librewolf and/or Vivaldi before this update drops
AI in the browser is a disaster waiting to happen and it's sad to see Mozilla think so little of its users opinions
@viralobscurity both Librewolf and Vivaldi have built-in translation, which people overwhelmingly consider to be AI (https://mastodon.social/@firefoxwebdevs/115849251057488746). Vivaldi even sends the text to a server for translation.
Your choice is your own, but we are up-front about the AI features we have.
-
-
@ArneBab people indicated pretty strongly that they wanted a way to block AI, but re-enable particular features https://mastodon.social/@firefoxwebdevs/115849251057488746.
It used to be referred to as a 'kill switch', which is much stronger wording, and a lot of folks wanted that wording (see the replies https://mastodon.social/@firefoxwebdevs/115740500373677782). But I think "block" is a reasonable middle ground. I understand that you don't.
-
-
