Something that hasn't been made clear: Firefox will have an option to completely disable all AI features.
We've been calling it the AI kill switch internally. I'm sure it'll ship with a less murderous name, but that's how seriously and absolutely we're taking this.
…
Firefox for Web Developers
in reply to Firefox for Web Developers • • •All AI features will also be opt-in. I think there are some grey areas in what 'opt-in' means to different people (e.g. is a new toolbar button opt-in?), but the kill switch will absolutely remove all that stuff, and never show it in future. That's unambiguous.
…
reshared this
Ewen Bell 📸, shellbyte (temporarily less active), AA, Hex and mkj reshared this.
Firefox for Web Developers
in reply to Firefox for Web Developers • • •I'm not asking for faith in our direction - the thing I love about the Firefox community is how open, honest, and technical it is.
But I do ask that you don't have the opposite of faith. Like, try not to be determined that we're going to do the wrong thing here.
…
reshared this
AA reshared this.
Firefox for Web Developers
in reply to Firefox for Web Developers • • •I hope we can (re)gain your trust here.
I don't personally work on this stuff, but I'll try hard to answer any questions you have.
And other than that, I'll get back in my lane, and stick to web platform stuff.
- Jake (@jaffathecake)
shellbyte (temporarily less active) likes this.
Firefox for Web Developers
in reply to Firefox for Web Developers • • •Ewen Bell 📸
in reply to Firefox for Web Developers • • •rachael laura yay ~
in reply to Firefox for Web Developers • • •Seachaint
in reply to rachael laura yay ~ • • •@rachaelspooky Also, that whole bit where the new CEO kited blocking adblocks? Lost me forever. Critical moral failure. You try to fuck with my overton window I throw you out it.
If we want a real humane browser it needs to be 1) Nonprofit, actually this time, no Google buyouts and 2) Flat out reject inhumane tech (DRM, AI, whatever the next shitty thing is), 3) stop hand-wringing about "market share". It's not a market. It's a medium for humans.
mike805
in reply to Seachaint • • •Christophe Henry
in reply to Firefox for Web Developers • • •reshared this
Mother Bones and R.L. Dane 🍵 reshared this.
Christophe Henry
in reply to Christophe Henry • • •reshared this
AA reshared this.
Christophe Henry
in reply to Christophe Henry • • •It's like Mozilla is a car company and it's advertising a new car with leather in it. Ok, cool but what is it? A berline, a pickup, a SUV? Will I recharge with electricity or fuel? And Mozilla's answer is: "it has leather in it!"
It's… not great.
Nicolas Silva
in reply to Christophe Henry • • •Violet Madder
in reply to Firefox for Web Developers • • •@jaffathecake
Why would anyone trust Mozilla with a damned thing ever again when it's clearly been hijacked by people with an agenda to enshittify it into oblivion?
Dave Winer ☕️ reshared this.
24😷-185
in reply to Firefox for Web Developers • • •@jaffathecake
Unfortunately Mozilla asked twice for our feedback regarding the implementation of AI features. Twice, it was a resounding NO. Twice, Mozilla shooed away this simple 2-byte-length answer.
Why should we begin to trust Mozilla again?
Josh “Yoshi” Vickerson
in reply to Firefox for Web Developers • • •@jaffathecake it’s hard to believe the “kill switch” will actually do what it says. We’ve been told time and time again “AI” will be “opt-in” just to have the features repeatedly turned back on after users have disabled them.
Why is this *any* different?
Firefox for Web Developers
in reply to Josh “Yoshi” Vickerson • • •David Gerard
in reply to Firefox for Web Developers • • •@josh @jaffathecake I have had browser.ml.* settings I disabled by hand in about:config re-enable repeatedly with new versions. I posted about it on bsky and a pile of other people chimed in saying the same had happened to them too.
Do not try to pretend you don't know this was happening.
MarinaAbramovic'sInvisible Man
in reply to David Gerard • • •@davidgerard @josh @jaffathecake
⏫ Firefox was all sorts of happy to answer questions until this one came up and they've been silent for 24 hours
🤔
reshared this
Sabrina Web 📎 reshared this.
Kiloku - Secretário do Caos
in reply to MarinaAbramovic'sInvisible Man • • •"We want to regain your trust": *immediately lies to us*
Andrew Deacon
in reply to Kiloku - Secretário do Caos • • •Bruno Nicoletti
in reply to Andrew Deacon • • •Anthony
in reply to Firefox for Web Developers • • •All of the ones listed in this post, for a start: buc.ci/abucci/p/1763845084.289…
Since writing that I've found more. It's like mold growing in the basement.
A few versions ago Firefox had maybe 5 (?) such ML-related features. Since then, the number of configuration options has exploded. Many (most?) of these features are ON (set to true) by default. Worse still, the "namespaces" are not just
browser.ml. There'sbrowser.aiwindow,browser.tabs.groups.smart,extensions.ml, andsidebar.notification.badge.aichat.How do you intend to earn trust against this backdrop? I fully expect that every time I update Firefox I'm going to have to scour through
... show moreabout:configto find the 2, 5, 10, ??? new AI-related options and double check that they are off. You haven't given anyone a reason to believe that the "master kill switch" you keep referring to is going to cover every single one of these settAll of the ones listed in this post, for a start: buc.ci/abucci/p/1763845084.289…
Since writing that I've found more. It's like mold growing in the basement.
A few versions ago Firefox had maybe 5 (?) such ML-related features. Since then, the number of configuration options has exploded. Many (most?) of these features are ON (set to true) by default. Worse still, the "namespaces" are not just
browser.ml. There'sbrowser.aiwindow,browser.tabs.groups.smart,extensions.ml, andsidebar.notification.badge.aichat.How do you intend to earn trust against this backdrop? I fully expect that every time I update Firefox I'm going to have to scour through
about:configto find the 2, 5, 10, ??? new AI-related options and double check that they are off. You haven't given anyone a reason to believe that the "master kill switch" you keep referring to is going to cover every single one of these settings sprawled across so many different places. At this point in time the only thing I trust is that Mozilla will keep pushing AI into Firefox and that I will have no choice but to put in a lot of work to keep it turned off--or give up using Firefox altogether.Incidentally, and speaking of trust and consent, will the proposed "kill switch" be turned off by default? You talk of "opt-in" as if it is confusing, but it is not: this switch should be OFF unless a user wants it on.
@josh@vickerson.me @jaffathecake@mastodon.social
Anthony
2025-11-22 20:58:04
Firefox for Web Developers
in reply to Anthony • • •Anthony
in reply to Firefox for Web Developers • • •The user experience sucks because I don't want AI anywhere near my computer, and I don't want to have to put in work on my web browser to ensure this. By adding these features you've introduced more friction in the form of a configuration tax each and every time I update the browser.
@josh@vickerson.me @jaffathecake
Firefox for Web Developers
in reply to Anthony • • •Anthony
in reply to Firefox for Web Developers • • •Is it always off by default? Are all of the configuration options it covers off by default and stay off even if I turn the kill switch back to on?
Are all the options listed here controlled by the kill switch? buc.ci/abucci/p/1763845084.289…
@josh@vickerson.me @jaffathecake@mastodon.social
Is it always off by default? Are all of the configuration options it covers off by default and stay off even if I turn the kill switch back to on?
Are all the options listed here controlled by the kill switch? buc.ci/abucci/p/1763845084.289…
@josh@vickerson.me @jaffathecake@mastodon.social
Anthony
2025-11-22 20:58:04
Firefox for Web Developers
in reply to Anthony • • •2005800 - Add Disable AI section to gen ai settings
bugzilla.mozilla.orgmkj reshared this.
Anthony
in reply to Firefox for Web Developers • • •You haven't answered my questions. You've not given me any assurance that people who can answer my questions will get back to me. You've also given me a homework assignment.
You are doing the opposite of building trust with such a response. I just got done telling you the browser is creating work for me, and that I objected to this. Following that by giving me work to do is an irritating move--you see that don't you?
@josh@vickerson.me @jaffathecake
a40YOStudent
in reply to Firefox for Web Developers • • •- privacy first (ads and tracker blocking, disable is per-site)
- accessibility (like adding a custom css is still difficult
- common sense (auto hide cookie consent)
Firefox for Web Developers
in reply to a40YOStudent • • •Joachim
in reply to Firefox for Web Developers • • •if money is spent on paying people to work on AI, by definition it’s money that’s not directed towards the Web platform. Mozilla doesn’t have infinite resources. Choosing to redirect them towards AI is a choice, and it’s the wrong one.
@a40yostudent
Mother Bones
in reply to Firefox for Web Developers • • •It's *inherently* the wrong thing, though.
I also don't want to buy eyeglasses that include eyeball-poking blades "but with a kill switch to retract them in case you don't like those." I just want eyeglasses with no eyeball-poking blades to begin with.
mcc
in reply to Firefox for Web Developers • • •xinit ☕
in reply to mcc • • •@mcc
The chat request is coming from inside the house!
@firefoxwebdevs @oblomov
Dave Winer ☕️
in reply to Firefox for Web Developers • • •Look at the web as your product, and do things that make it easy for independent devs to create products for the web without locking users in. You can be sure Chrome won’t follow because they’re invested in capturing users, you should be invested in freeing them and enabling independent devs to create great products for them, without having to resell storage. Upgrade the web and let devs build in the newly freed web.
More here..
scripting.com/2025/12/17.html#…
Scripting News: Wednesday, December 17, 2025
Scripting NewsDave Winer ☕️ reshared this.
Norgg
in reply to Firefox for Web Developers • • •Hank G ☑️ likes this.
Firefox for Web Developers
in reply to Norgg • • •Jonathan Kamens 86 47
in reply to Firefox for Web Developers • • •It is 100% clear to anyone not trying to run cover for #Mozilla that multiple #GenAI features have already been introduced into #Firefox as opt-out rather than opt-in. This isn't questionable or debatable or complicated, it's simple fact.
You've given us no reason to believe this is going to change.
Trying to obfuscate this away in this thread makes it clear you're being disingenuous, whether or not you realize you are.
Jonathan Kamens 86 47
in reply to Jonathan Kamens 86 47 • • •It's not that we want it to be opt-in, we want it to not be there at all, because #GenAI is bad for tech and bad for the people whose content is stolen and bad for culture and bad for the whole fucking world, and we want #Mozilla to take a stand for what is RIGHT, not jump on the catastrophically bad AI hype train and join every other company in the bubble.
Doing AI at all, opt-in or not, is doing the wrong thing.
#Firefox
Jonathan Kamens 86 47 reshared this.
Martin Auswöger
in reply to Jonathan Kamens 86 47 • • •Martin Auswöger
in reply to Firefox for Web Developers • • •Hank G ☑️ likes this.
Firefox for Web Developers
in reply to Martin Auswöger • • •sodiboo
in reply to Firefox for Web Developers • • •I think it could be useful to have multiple levels of such a kill switch:
something like the following two checkboxes:
[X] Enable ML features
|- [X] Enable ML features that require an internet connection
unchecking the first one would lock the second one to off. but if you just uncheck the second one, then on-device translation would still be allowed, but not e.g. the ai chatbot sidebar.
too many checkboxes can be confusing and it's hardly a "killswitch" anymore. but these two in particular feel like they cover the most important bases from a fundamental privacy and reliability standpoint (but they do not properly cover the ethical concerns about training data licensing)
AA
in reply to Firefox for Web Developers • • •Silmathoron ⁂
in reply to Firefox for Web Developers • • •There is no world in which opt-in means "of course you can turn it off"...
Firefox for Web Developers
in reply to Silmathoron ⁂ • • •Fell
in reply to Firefox for Web Developers • • •@silmathoron If the button is similar in style to the other buttons, is not animated, doesn't trigger a popup unless clicked, and can be removed, then I'm okay with you guys adding it. I think the Firefox sidebar has such a button by default. That's fair.
The problem is that most browsers try to highlight their AI features by making them as noticeable as possible, using animations, colourful buttons, popups and such, which is just annoying.
Pedro Mateus
in reply to Firefox for Web Developers • • •Quixoticgeek
in reply to Firefox for Web Developers • • •have you told the people actually pushing the releases ? Currently the opt-in is hidden behind the about:configs page, and you actually have to opt out. That's not how an opt-in works.
May I suggest everyone in your organisation needs to attend a primer course on consent.
Firefox for Web Developers
in reply to Quixoticgeek • • •Quixoticgeek
in reply to Firefox for Web Developers • • •samir, sad, no more meows
in reply to Firefox for Web Developers • • •@mkj This is opt-out, not opt-in.
I am personally fine with this; it’s good enough for me. But words mean things.
mkj
in reply to samir, sad, no more meows • • •Jason Evangelho 🐧🎒
in reply to Firefox for Web Developers • • •Kev Quirk
in reply to Firefox for Web Developers • • •I think your CEO publicly stating that Firefox "will evolve into a modern AI browser" is what's got people on edge.
Further, this is just another step in a raft of poor decisions by Mozilla, which has me (after 20+ years of happy use) looking for an alternative.
Morten Juhl-Johansen
in reply to Kev Quirk • • •Jonathan Lamothe
in reply to Kev Quirk • • •Kev Quirk
in reply to Jonathan Lamothe • • •@me no. That's a direct quote from the post.
blog.mozilla.org/en/mozilla/le…
Mozilla’s Next Chapter: Building the World’s Most Trusted Software Company
Rebecca Smith (The Mozilla Blog)catch
Unknown parent • • •@christophehenry @nical they very publicly had to walk back accepting crypto donations in 2022. It's not quite putting crypto miner in Firefox or linking it to a crypto exchange but still.
techcrunch.com/2022/01/06/mozi…
Firefox maker Mozilla pauses crypto donations amid backlash
Manish Singh (TechCrunch)reshared this
AA reshared this.
Christophe Henry
Unknown parent • • •liquidlamp
Unknown parent • • •@nical @ecadre Why isnt there already a kills switch or opt in for these "tiny models?"
Having a dozen about:config settings be the only effective configuration option to disable Mozilla's current forays into AI doesnt exactly inspire trust about its future plans when the new CEOs first post is all about Firefox's AI future.
We've seen the direction the browser is already moving in with AI and user consent, so it should be no surprise that people are even more skeptical now.
mcc
in reply to Firefox for Web Developers • • •Bare-minimum acceptable would be for Firefox to put all AI/ML features behind a compile flag, and offer a download with zero AI capability in the binary. I requested this in a bugzilla ticket when the first "AI" feature was added, I think over a year ago, and if y'all had started on that then you wouldn't need to do work to add a "kill switch" now.
"A setting" is better than "no setting", but still somewhere below "barely acceptable" (or for that matter, "switch to Waterfox").
⊥ᵒᵚ Cᵸᵎᶺᵋᶫ∸ᵒᵘ ☑️
Unknown parent • • •Kuba Orlik
in reply to Firefox for Web Developers • • •Samat Sattarov
in reply to Firefox for Web Developers • • •Firefox for Web Developers
in reply to Samat Sattarov • • •[object Object]
in reply to Firefox for Web Developers • • •@SamatSattarov so your definition of opt-in includes enabling a bunch of browser.ml about:config settings after updates, including all the ones I’ve already disabled, just in case I change my mind and want my browser to be full of absolute horseshit?
that’s fucking worthless and I’d tell you to feel ashamed that this dark pattern crap is what you think constitutes consent, but let’s be real: you’re a PR mouthpiece for an AI corporation and are incapable of shame.
Jor ☝️😐
in reply to Firefox for Web Developers • • •Let’s put it bluntly:
- “AI” is crap, produces wrong or misleading answers all the time, and this cannot be fixed, by design. That’s in addition to all the ethical concerns (stealing people’s work, awful environmental impact, etc.) that should have excluded it a long time ago.
- your users massively said that they did not want it, yet you chose to forcibly impose it. The fact that you have to talk about an “AI kill switch” says that you are well aware of the amount of people who clearly do not want this in their browser.
- the argument that it can be turned off and that people should be “free to use it” and other shit like that is completely flawed, because even for the (few) people who may want AI in FF, well they could just use extensions for it anyway. That is precisely what extensions are for.
- However what you chose to do is to waste a significant amount of developer time and energy into the development of a “feature” tha
... show moreLet’s put it bluntly:
In short: the choice to force AI into FF while nobody wants it is unjustified on all accounts and an awful waste of development resource, and a spit in the face of your remaining users.
reshared this
Liam Proven reshared this.
StarkRG
in reply to Jor ☝️😐 • • •David Chisnall (*Now with 50% more sarcasm!*)
in reply to Jor ☝️😐 • • •@jor
Unfortunately, 'AI' is a meaningless marketing term. While most of the things under that umbrella are nonsense I have been impressed with the on-device translation models that the Firefox folks have produced:
There aren't many things in the AI hype nonsense that I say positive things about, but this is the biggest exception.
Jor ☝️😐
in reply to David Chisnall (*Now with 50% more sarcasm!*) • • •Mozilla is talking about making FF into an “AI browser”.
Firefox for Web Developers
in reply to Jor ☝️😐 • • •@jor @david_chisnall I think this is where some of the communication has gone badly.
We're also looking at using on-device models to provide alt text in cases where it's missing, which should improve a11y for those who need it most.
I don't think that's the kind of thing people think of when they hear AI, but it is.
Jor ☝️😐
in reply to Firefox for Web Developers • • •@david_chisnall
You are listing two features that most people will agree are justified (though they might represent a privacy risk depending on the implementation, but that’s another matter).
But this is hardly everything, is it ?
For example, there already is an integrated AI chatbot using the big chatbot providers.
Or an AI “summarizing” feature on iOS devices, which uses Apple Intelligence. Meaning that, in addition to the obvious privacy risk (we have to trust a company like Apple that they don’t collect the user’s data 🙄), will also generate a lot of crap, since Mozilla has to put some ridiculous disclaimer in their FAQ for the featur
... show more@david_chisnall
You are listing two features that most people will agree are justified (though they might represent a privacy risk depending on the implementation, but that’s another matter).
But this is hardly everything, is it ?
For example, there already is an integrated AI chatbot using the big chatbot providers.
Or an AI “summarizing” feature on iOS devices, which uses Apple Intelligence. Meaning that, in addition to the obvious privacy risk (we have to trust a company like Apple that they don’t collect the user’s data 🙄), will also generate a lot of crap, since Mozilla has to put some ridiculous disclaimer in their FAQ for the feature stating that you should absolutely not trust summaries generated by generative AI, a ”predictive technology not guaranteed to always be accurate” and that it is your responsibility to “verify summaries against the original page”. 🤡
(There is a similar hypocritical disclaimer on the “AI chatbot” page, hidden behind two levels of drop-down menus…)
In short : we all know that this will generate a shitload of false or misleading slop, some of which might even be dangerous, but FF encourages users to use and trust this, and encourages them to interact with “AI” providers that will collect their personal data while burning the planet for a few more digits of profits for the billionaires. 😬
And this is only the beginning, since the project is apparently to create a full “AI browser”, which means integrating more and more of that crap everywhere, and encouraging people to use it and trust it instead of what would be the only reasonable thing to do : warn people about how shitty and dangerous this technology is on many accounts, and trying to discourage its use as much as possible. 😬
Access AI chatbots in Firefox | Firefox Help
support.mozilla.orgFirefox for Web Developers
in reply to Jor ☝️😐 • • •Jor ☝️😐
in reply to Firefox for Web Developers • • •@david_chisnall
Then what was the point of talking about these features and implying that people might not understand that “AI” can also be those useful features?
Isn’t the point of this is to imply that the backlash against “AI” in FF might be misinformed? Which is also implied by “our communication has gone badly” and all that…
But we all know that these features are not the target of the backlash, those features (local translation, alt text) are not the ones massively rejected by your users.
What your users reject is the “AI chatbot”, “AI summary”, and similar crap that I listed above.
Now, could you please stop sidestepping the issue, and explain the rationale behind including all this “AI chatbot”, “AI summary”, etc. crap in Firefox itself, since as I mentioned earlier:
- it is useless, misleadi
... show more@david_chisnall
Then what was the point of talking about these features and implying that people might not understand that “AI” can also be those useful features?
Isn’t the point of this is to imply that the backlash against “AI” in FF might be misinformed? Which is also implied by “our communication has gone badly” and all that…
But we all know that these features are not the target of the backlash, those features (local translation, alt text) are not the ones massively rejected by your users.
What your users reject is the “AI chatbot”, “AI summary”, and similar crap that I listed above.
Now, could you please stop sidestepping the issue, and explain the rationale behind including all this “AI chatbot”, “AI summary”, etc. crap in Firefox itself, since as I mentioned earlier:
David Chisnall (*Now with 50% more sarcasm!*)
in reply to Jor ☝️😐 • • •@jor
My number one request to Mozilla would be: stop using the term AI.
It is a nonsense marketing term being pushed by Snake Oil Sam and his merry band to try to pretend that machine learning models are magic.
Talk about:
Do that, and you will regain my trust. Tell everyone that you are an 'AI-first company' making an 'AI-first browser' and I will assume you're a bunch of grifters trying to cash in on the current fraud bubble.
Jor ☝️😐
in reply to David Chisnall (*Now with 50% more sarcasm!*) • • •@david_chisnall I am not sure it really is the main issue here, as this implies again that it would be a bad communication problem, while it is not.
Although it would indeed be better to stop using misleading marketing terms like “AI” and replace them by better and more descriptive terms, the main issue to me here is: the inclusion directly in the browser of a technology that is by design unreliable, unethical and dangerous on many accounts.
Whether we call them “AI chatbots and summaries” or “dangerously misleading and unreliable LLM chatbots and summaries”, in both cases none of this should ever have been included in the first place.
Stéphane Bortzmeyer
in reply to Firefox for Web Developers • • •matthias koplenig
in reply to catch • • •@catch56 @christophehenry @nical Not quite a crypto miner? Do you even hear yourself?
The payment provider also allowed crypto-transfers, how is that even a scandal?
Somehow the Internet Archive takes in crypto donations to this day, and nobody cares.
Ian Bicking
in reply to Christophe Henry • • •@christophehenry They did work on both of those in Emerging Technologies (which was disbanded and most folks laid off in 2020).
I think IoT was seldom more than two people, usually one, and maybe some supporting folks around the web standards.
Hubs (a VR meeting space) was a bit larger, and had some external funding. Apparently it's spun off: hubsfoundation.org/ (it's always hard to know how successful these things are though)
In cases like these Mozilla usually hoped something would eventually spin off. These were never going to be a new direction for Mozilla or Firefox.
Hubs Foundation - We'll take it from here.
Hubs FoundationNicolas Silva
in reply to Christophe Henry • • •Nicolas Silva
Unknown parent • • •Damien de Lemeny
Unknown parent • • •@nical @areacode @christophehenry
"That's pretty common stuff"
No it isn't !!!! Please please please stop acting like one of the keystone pieces of software for millions of users is a playground for random pet projects following "hot" fads ! That is not good stewardship ! The only other actors that do this are the ones you're supposed to be a sane and reliable an alternative to, not more of the same crap !
Nicolas Silva
in reply to Damien de Lemeny • • •Nicolas Silva
Unknown parent • • •areacode
in reply to Christophe Henry • • •@christophehenry @nical
RE metaverse
techcrunch.com/2022/12/01/mozi…
Edit: support.mozilla.org/en-US/kb/e…
Mozilla acquires Active Replica to build on its metaverse vision | TechCrunch
Kyle Wiggers (TechCrunch)