Skip to main content


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.

…

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.

…

Aaron reshared this.

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.

…

in reply to Firefox for Web Developers

I don't know what you are expecting. The things your leadership are saying are indistinguishable from the crap that Sam Altman and the rest of the LLM "AI" crowd are saying. It's special pleading to say "yeah but our guy is on the level so you should trust us". Were all just tired of it.

2xfo reshared this.

in reply to GrayGooGlitch

I should also note, the opposite of faith is skepticism, and it's the place we should be when people make unverifiable claims. If you mean faith as synonymous with confidence, that comes from trust and demonstrated good will. The good will dried up the moment unwanted ML and LLM garbage was jammed in and set as opt-out rather than opt-in.

All of this should be opt-in from jump. Barring that, there should be clear and concise instructions for opting out, not messing around in hidden setting panels.

in reply to Firefox for Web Developers

I think the reason most of us have the opposite of faith is both that Mozilla leadership has shown the complete lack of understanding as to what Firefox (or other, since abandoned projects) stand for *and* the strong messaging they tend to send about the latest hypebro crap ("AI first" now, a few others from previous CEOs) which all goes firmly contrary to what the users feel Firefox should be standing for.
in reply to Henrik Pauli

@phl well, I hope I can counteract some of that here by posting straight-forward content about web platform stuff.
in reply to Firefox for Web Developers

With respect you can't counter what those of us who have lost faith see again and again from Mozilla. It's a long history, not just recent and has become progressively worse over years. AI is an expected, but for many particularly abhorrent footshot in a steady stream.

I gave up on Firefox for other reasons (performance) a few years ago now, and use it only to recover old passwords. I would never use it seriously again because it's not worthy of my trust.
@phl

in reply to happyborg

@happyborg I always find the performance reason interesting, simply because I somehow never managed to face the same issue as you guys. I've never in the last 20 or so years found Firefox (annoyingly) slow, bar the few times some site would maliciously misbehave (think YouTube being angry about people with adblockers), so other than side-by-side comparison showing that it loads a slight bit slower, I guess I just managed to avoid sites that are painfully slow with Firefox?
in reply to Henrik Pauli

@phl
It's about device (eg budget phone) use patterns (eg many open tabs) rather than sites, but FF on Android was indeed unusable on IMDB.com.

It was also terrible for me on a high powered 64GB Linux laptop because of many open tabs.

Brave has been fine for a few years now on same devices and with same use patterns - regardless of websites. I guess Chrome might be too but who still uses that 🀣

Yeh, I know many do. πŸ€¦β€β™‚οΈ
@firefoxwebdevs

in reply to happyborg

@happyborg
Ahh interesting, yeah, I count Firefox Android a very different entity from Firefox the desktop browser, so much so it didn't even occur as an option in this discussion :D And you're right, *that* one has had some wild issues (from performance to web function to UX), to the extent that it's only been my secondary browser until very recently.

Can't, thankfully, say I've ever had anything nearly as grating with the true OG Firefox on desktop.

@firefoxwebdevs

in reply to Henrik Pauli

@happyborg I have like 4 windows, each with over 20 tabs in my current work firefox (tree style tab continues to be a life saver) and have not had any performance issues with that much nonsense open yet o_O

Similarly, at home (though usually only one window), I might end up preloading a dozen youtube or whatever tabs to check out later.

@firefoxwebdevs

in reply to Henrik Pauli

I have five virtual desktops and each might have 20 browser windows open with 1 to 10+ tabs in each. Not to mention multiple instances of other memory heavy apps such as VSCode & terminals running mega Rust builds etc

It's a powerful laptop but Brave handles this while Firefox does not.

I don't understand why your experience has any relevance to mine, but people do insist on responding with, it works fine for me. I'm happy for you but it isn't helpful.

Same re Android
@firefoxwebdevs

This entry was edited (1 month ago)
in reply to happyborg

@happyborg Crikey that's a lot of windows :D

And nothing more than just being curious what it takes to have a bad experience in Firefox because I thought I had too much stuff open.

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)

in reply to Firefox for Web Developers

It's not only about trust. It's also the question how Firefox wants to be part of destroying our climate and water ressources in a time of #climateEmergency and growing #desertification thanks to #datacenters needed by the #AIHype!

Software that contributes to this destruction, even though it would work without it, is not an option for me. If it forces me to use such functions, I consider it even criminal. Firefox/the CEO wants AI.

#climateAction

@jaffathecake

reshared this

in reply to Petra van Cronenburg

@NatureMC @jaffathecake +1. "Our standard pizza contains arsenic, but there's an arsenic-free option if you choose!" is not a moral stance.

reshared this

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?

in reply to Firefox for Web Developers

@jaffathecake the β€œAI” chat flag resets every now and then. browser.ml.enable as well. I don’t have them all memorized, but I’ve had to disable them more than once (yes, same browser profile).

I run Dev Edition. Maybe it’s a bug πŸ€·β€β™‚οΈ but against the backdrop of doubling down on things Mozilla’s users explicitly reject, it sure is a strange coincidence.

in reply to Josh β€œYoshi” Vickerson

@jaffathecake β€œkill switch” is opt-out, btw.

Opt-in would be users having to separately choose to install and enable it.

in reply to Josh β€œYoshi” Vickerson

@josh everyone has a different definition of opt-in, which I why I was up-front about that. Whereas the kill-switch is unambiguous.
in reply to Firefox for Web Developers

I don’t think it’s ambiguous to say something users have to turn off is not β€œopt-in”.
in reply to Josh β€œYoshi” Vickerson

@josh Indeed. Opt-in is when these features ship turned off by default.

Having to interact with a switch, kill switch or no, to remove them from our sight is opt-out.

in reply to Firefox for Web Developers

@josh
Hi, simple non-natively-English speaker here. A kill-switch is unambiguously opt-out to me: I do not want AI, so I use the kill switch... to opt-out.
in reply to Eh?!?

@Eh__tweet @josh Here's a made-up example…

Let's say a new button appears next to the location bar that does _AI things_, but not until the button is clicked.

Some would say that's opt-in, but some would say they didn't opt-in to that button being there.

This ambiguity doesn't exist with the kill switch. It would remove that button, or prevent it from ever appearing.

Does that make sense? This is how the two things work together.

in reply to Firefox for Web Developers

@Eh__tweet @josh
Am I missing something? If the default is with AI and you need to hit a button to "kill" it then you're opting out of having AI. I don't understand how the opposite can be true. Are you opting in to a kill switch? Is that the suggestion?
It sounds like the US mobile carriers calling a normal phone "unlocked". No, that's a phone, you're locking it.
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.

in reply to the elder sea

@eldersea @davidgerard @josh @jaffathecake

Every time I look, it seems there are additional options involving 'ml' to disable, some more esoteric than others.

This does not inspire confidence that future lines in about:config will be explicit about what they do viz. LLMs and bloatware.

in reply to the elder sea

@eldersea @josh @jaffathecake if Mozilla is gonna send people who say "hiii~ uwu smol bean dev here!!" and they just fuckin lie at us like this ... well actually, they're probably sending their best remaining
This entry was edited (1 month ago)
in reply to David Gerard

@davidgerard @eldersea @josh @jaffathecake

I don't know what everybody's upset about. All AI features are opt-in only. You have to deliberately opt-in by failing to repeatedly disable several cryptic default settings hidden behind an obscure configuration URL.

reshared this

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

πŸ€”

in reply to Firefox for Web Developers

@jaffathecake

If you want to make an AI browser, make a separate browser with AI. Then you can compare how many users are on that browser vs. how many are on the browser without AI.

I like Gecko. I don't like generative AI. I am still using Thunderbird because there's no AI or plans to integrate AI.

I have stopped using Firefox and purged it from most of my machines because it is diving into AI.

I have stopped using search engines because they have integrated AI.

I am concerned about the societal and ecological impacts of AI.

I would love to see Mozilla stop shooting itself in the foot. Instead, I see you all reaching for another box of bullets and reloading the gun.

#NoAI

in reply to Firefox for Web Developers

a killswitch isnt enough and never will be. for the longest time, this was the browser with integrity and a clear mission. even the slightest bit of AI in the browser, even opt in, is a betrayal of that mission. AI is the kind of thing that should be treated as malware and firefox is infected.
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.

reshared this

in reply to Firefox for Web Developers

Sensitive content

in reply to Yora

Sensitive content

@Yora
in reply to Firefox for Web Developers

Yeah I think most people mainly deplore the hype and the resources spent on technological trends whose benefits are not always obvious. Before that, Mozilla advertised about FirefoxOS, before killing it to focus on IoT, before moving on to blockchain, then crypto, then NFT's and now IA. In more that 10 years, none of this projects produced anything useful for the users.
in reply to Christophe Henry

Right now, Mozilla would probably be the first company to be diagnosed with ADHD. It really can't seem to focus and do something productive. The question was never "should Firefox have IA?". The question is "to do what?". Mozilla is communicating that IA is coming. Not announcing a new feature. TBH, it's worrying. IA should be an implementation detail, not the central point.
This entry was edited (1 month ago)
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?

in reply to Firefox for Web Developers

@jaffathecake I'm sorry you were put in this position.

Many people are extremely angry about resource-guzzling, plagiarising, bullshitting chatbots being forced into every aspect of our lives. We are personally insulted on a daily basis by being told they can do our jobs. We watch as innocent friends and family are conned into believing whatever slop they generate. We seethe with rage as our governments are co-opted to pour money into this awful technology instead of stopping it. We fear for our children growing up in this world. We are literally told it will become our god.

Into this context, you're pushed out as a helpless lightning rod. Clearly you have no power to change Mozilla's strategy, and clearly your bosses aren't going to front up and fix things.

You didn't do this. In an ideal world people wouldn't vent their anger at you personally. But the world we're forced to live in is very very far from ideal.

in reply to Firefox for Web Developers

the problem is: if you work on AI, then there will be less work on urgent things like:
- 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)
in reply to a40YOStudent

@a40yostudent
> common sense (auto hide cookie consent)

How is "Let's hide the fact websites screw you by hiding pre-enabled trackers when GDPR requires opt-in" is common sense? It defeats "privacy first"…

Common sense is refusing useless cookies autocratically and blocking trackers and extensions can do both…

Websites displaying big-ass banners for technical/useful cookies such as auth/session cookies is just dark pattern. Law requires tracker consent, NOT useless banners…

in reply to 🐧DaveNull🐧 ☣️pResident Evil☣

@a40yostudent

Also, those panners are rarely "cookie consent" despite having "consent" in he UI title. They are often
- opt-out forms
- loaded after both cookies and script (or otherwise) trackers are loaded
- trackers are still loaded/loaded again again in new/other pages even after opt-out…

Also, browsers automagically modifying webpages content without the user knowledge/permission/opt-in is no different than Browser-in-the-middle attack and should be illegal.

@firefoxwebdevs

in reply to 🐧DaveNull🐧 ☣️pResident Evil☣

@a40yostudent Common sense is not doing Artificial Stupidity because it
- waste resources
- makes computing super-expensive for everyone, not just "AI users"
- destroys the planet
- legitimates toxic business and shitty companies that ignores copy-left licenses terms, exploit click workers and openly fund techno-fascism…

So idiots can generate bullshit summaries of webpages and help LLM companies bypass content crawlers blocking, to steal content without authors consent…

@firefoxwebdevs

This entry was edited (1 month ago)
in reply to a40YOStudent

@a40yostudent fwiw I haven't seen anyone redirected from working on web platform stuff to AI stuff.
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

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#…

Dave Winer β˜•οΈ reshared this.

in reply to Firefox for Web Developers

The thing is: Adding LLM-stuff to FF and burying the possibility to disable it in about 6 different "about:config" settings is not exactly how trust is built.

It's the corporate bullshit (like those bloody TOS) that is killing Firefox, and hence Mozilla.

reshared this

in reply to Firefox for Web Developers

The overwhelming evidence for the past 15 years is that Mozilla doesn't care about its users, its browser, or our privacy. I'm sure you can understand, especially in light of the new CEO's comments, people are going to be sceptical. People want Firefox to just be a browser. Telling them ad blockers might be banned and that Firefox might become an AI platform is not helping the perception people have of Mozilla.
This entry was edited (1 month ago)

reshared this

in reply to Firefox for Web Developers

I'm very glad to hear that there will be a kill switch; however I don't think there is any ambiguity about what opt-in means, it's all in the name: it means "off by default" so you can say "sure, I want this, turn it on".
There is no world in which opt-in means "of course you can turn it off"...
This entry was edited (1 month ago)
in reply to Silmathoron ⁂

@silmathoron eh, maybe it's simpler than I think. If a new menu item appeared that does nothing until it's clicked, is that still opt-in? What if it's a button next to the location bar?
in reply to Firefox for Web Developers

a new greyed button that pops a menu saying "we've got AI, currently it's off, do you want to turn it on? yes/no" would definitely be opt-in, yeah πŸ™‚
in reply to Silmathoron ⁂

@silmathoron that seems reasonable, although I've also seen folks describe that as "shoving AI down their throats", so I didn't want to promise 'opt-in' when it might not be the model of opt-in people are thinking of.
in reply to Firefox for Web Developers

@silmathoron
Opt in means it doesn't do anything unless i ask for it. It means the settings are disabled by default and maybe sometimes after an update they get reset to off because things changed and the permissions are different now. It's the complete opposite of what they've been doing and I'm not hopeful that they will change things enough to fix their reputation.
in reply to 2xfo

@silmathoron
I want a hard fork created with reactionary fury that specifically rejects AI for its ecological and social consequences. I don't want Google telling my browser how to work - whether it's because they own its engine or its boardroom
in reply to Firefox for Web Developers

I find this hard to trust when so far the AI features have been snuck in as on by default and there's like 20 different config settings you need to turn off to be rid of them, but if true that would be good (although I'd prefer the features not being there in the first place)
in reply to Norgg

@Norgg I think there's also some disagreement in terms of what is and isn't AI. Like, Firefox uses on-device models for page translation, which is great for privacy. Is that AI?
in reply to Firefox for Web Developers

@Norgg This is nonsense equivocation.
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.
in reply to Jonathan Kamens 86 47

@Norgg Furthermore, opt-in isn't even enough.
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
in reply to Jonathan Kamens 86 47

@jik As I am a Firefox user and I don’t think I’ve opt-outed of anything (or I have and I forgot ☺️) which GenAI features do I have in my Firefox?
in reply to Martin AuswΓΆger

I just installed a fresh snap of 146.0.
- Right click on any page and you get the new "Ask an AI chatbot" menu option. And before anyone says it, a feature not being fully configured is not the same as it being opt-in.
- Perplexity was added to the list of default search engines.

These AI first features just appeared with no warning and are distinctly not opt-in. Mozilla seems to think "you can just not click the AI button" is the same as opting in to it appearing in the first place. I have no interest in my UI being a minefield.

in reply to Firefox for Web Developers

@Norgg "Machine learning technologies like the Bergamot translation project offer real, tangible utility. Bergamot is transparent in what it does (translate text locally, period), auditable (you can inspect the model and its behavior), and has clear, limited scope, even if the internal neural network logic isn’t strictly deterministic. Large language models are something else entirely*. They are black boxes. You cannot audit them. You cannot truly understand what they do with your data. You cannot verify their behaviour.

*in the context of a browser, I trust constrained, single purpose models with somewhat verifiable outputs (seeing text go in, translated text go out, compare its consistency) more than I trust general purpose models with broad access to my browsing context"

1/

in reply to Firefox for Web Developers

@Norgg I personally would be fine with a kill switch for β€œGenAI” and β€œSending data somewhere else than the visited website”. An on-device machine learning translation model (non-LLM) would not be affected by that.
in reply to Martin AuswΓΆger

@ausi @Norgg I've been reaching out to folks about this and a lot feel on-device is still something they don't want. It's tricky.
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)

in reply to Firefox for Web Developers

@Norgg An AI kill switch should disallow the following categories in my opinion:
- LLM aka GenAI aka hallucinations
- trained on stolen data
- training or usage causes disproportionate impact on environment
- sending data to some AI company

If the on-device translation falls into any of them I’d also say that I don’t want that.

But I guess it will be very hard to find broad consensus here :(

in reply to Martin AuswΓΆger

@ausi @Norgg thinking about translation, avoiding 'hallucinations' is tricky if any kind of inaccuracy counts as a hallucinations. If not, it's hard to categorise which errors are hallucinations and which are… other kinds of misinterpretation.
in reply to Firefox for Web Developers

Previous generations of translation engines had different kinds of failure modes β€” if the system couldn't find a reasonable solution, the outputs would be clearly garbled, giving you pretty solid cues that the transmission was broken. As translation engines have shifted into LLMs, the output has gotten more polished and less useful, because the errors are much harder to spot. As someone who has used machine translation from a fairly small language dozens to hundreds of times a day for almost a decade, this is a genuinely serious problem. I would strongly prefer to see machine translation continue previous lines of development rather than just tossing everything in the blender. It feels like the sentiment now is "well, if we just throw enough compute at it we can fully replace all human translation", as opposed to ceating a tool designed for actual human needs. At the core, that's what all of this is about β€” this is a technology in search of things it can do, not features designed for the needs of real users. If you go back to designing tools for actual users intended to do specific things in the world in the way most useful for those people, rather than forcing all uses through the Everything Machine, you'll get a much better reaction.
@ausi @Norgg
in reply to Firefox for Web Developers

If you planned to make it 'opt-in' you wouldn't be calling it a kill switch. Don't pretend 'opt-in' is the same as 'possible to disable'.
in reply to Fritz Adalis

@FritzAdalis I didn't mean to pretend anything. I tried to be honest and clear that what counts as 'opt-in' means different things to different people.

For example, if an AI button (that did nothing until it was clicked) appeared next to the location bar, would you consider it opt-in. This is just a made-up example btw.

in reply to Firefox for Web Developers

@FritzAdalis no. if you put a button on my browser without asking me, that is not opt in. I honestly don't understand how you could think it is.

"we installed our dishwasher in your kitchen, but you don't need to use it, so we're calling that opt-in."

in reply to Firefox for Web Developers

I don't think the definition of opt-in is anywhere near that ambiguous. Do you think the Edge Copilot button 'did nothing until pressed'? Sure, you add the button. Then it's too slow to open so you cache things first. Then on first open it's not relevant, so you train from the start. All along advertisers want the data. (You'll recall that you removed "we won't sell your data, ever" from your web site.)

Right now to disable features like ai and ads and coupons I have to go into about:config. If you're confident users want those features, why not make them disabled by default and make users open about:config to enable?

(And let's face it, Mozilla has a frequent habit of turning disabled features back on during even minor updates.)

You could make all of this an add-in that has to be installed, like you should have done from the beginning. Including unwanted, unrelated features is the force-feeding that users hate and nobody important at Mozilla seems to understand that.

in reply to Firefox for Web Developers

Is it opt-in or is it a kill switch (i.e., opt-out)? The fact that you contradict yourself trying to assuage ambiguity only to add more doesn't inspire confidence.
in reply to Jake Wharton

@jw Eh I guess I failed to make it clear. I'll try again:

A new button appearing in the toolbar for an AI feature that does nothing until it's clicked - some would say this counts as opt-in, some would say otherwise.

Whereas the kill switch would remove this button, or prevent it ever appearing.

I don't think that's a contradiction?

in reply to Firefox for Web Developers

@jw

It's very simple. If I get a question when I start firefox asking me if I want to use AI, it's opt in. If I have to do anything at all to disable it, it's opt-out.

If you show me a button that is doing something using AI, it's neither, it's trying to trick me.

in reply to EQ

@eq @jw "it's neither" - exactly, I wanted to be clear up front that there's ambiguity there, but not with the kill switch.
in reply to Firefox for Web Developers

Kill switch does not fix it. When you use the word AI nowadays, what your really mean is sending data to a big company that will store and use it for training their model and then make my job redundant with it before the bubble bursts and someone walks away with a lot of money to start the next grift.

If something is opt-out, it will be active for everyone that does not know this. What is it that is so nessesary in a browser that it has to be an integral part, not plugin?

in reply to EQ

@eq I've spoken to folks who consider local-models to be part of the bad thing too - those don't send data anywhere.

There's a lot of differing opinions on this it seems.

@EQ
in reply to Firefox for Web Developers

@eq adding my voice to the torrent: I'm fine with local models in niches like neural net machine translation, OCR, text to speech & vice versa. the instant it involves feeding the megacorp "AI" machine that all of us are already forced to subsidize with higher prices for hardware, electricity, water, by having our work & our thoughts stolen by massive scraping (which we have to pay hosting bills for) ... it crosses a very bright line in the sand, and means I'm done with Mozilla.
@EQ
in reply to Firefox for Web Developers

Is the kill switch on by default? If so, yes, that's opt in. If not, no, that's not opt in, the same as all the other crap you've done. And like, yes, having an actual single switch you don't keep turning back on, if this actually ends up being the case, is better than the current malice, but it's still not opt-in. Saying there are different definitions here is wildly disingenuous. If does not require an explicit user action to turn it on, it's not fucking opt-in. So if you build a kill switch and it's turned off in the default install, then you can say it's opt in.
in reply to Firefox for Web Developers

You're not talking to normal web users, you're talking to the bunch that makes the web what it is - or what it should be for that matter.

We can very well see behind phrases like "kill switches" and "customer centric" decisions.

I don't know why you've chosen to be either stupid or outright malignant, but I will not support it.

#Firefox is built to be the foundation of the open web. #AI in the current form is *THE* antithesis to it.

Stop #gaslighting us.

Stop enabling #slop.

in reply to Fabian Transchel

@ftranschel
To be fair, i fully expect Firefox management is gaslighting their programmers just as well as the rest of us
in reply to 2xfo

@RnDanger @ftranschel The Encyclopaedia Galactica defines Mozilla Management as "a bunch of mindless jerks that will be first up against the wall when the revolution comes".
in reply to Firefox for Web Developers

"Hello, Welcome to Firefox! Do you want AI?"

giant-ass button: "[ NOOOO ]" *CLICK*

I never see AI ever, ever again.

If it really is that simple, I will welcome it. πŸ˜„

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").

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.

Unknown parent

mastodon - Link to source
Firefox for Web Developers
@SamatSattarov which AI things in Firefox do you feel haven't been opt-in so far?
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.

reshared this

in reply to [object Object]

@SamatSattarov and while we’re here

I know it’s very popular among PR fuckfaces to claim that your justifiably angry users are confused as a way to control the discussion.

none of us are confused. all of us know a dark pattern when we see it. plenty of us have had to implement them for our dickhead employers. none of us want our consent violated by a browser we’ve previously done advocacy for. no, you don’t get to dictate what a consent violation looks like for your users.

in reply to [object Object]

@SamatSattarov β€œwhy are you being so mean, we’re developers too” be fucking serious. Firefox is fucking cooked and so’s the web and you’re giving me PR language from an Oops! Not Actually Official! account and expecting me to not notice I’m talking to a salesperson under the employ of a millionaire who only recently told me and the rest of the Firefox userbase to personally go fuck ourselves

reshared this

in reply to Firefox for Web Developers

If the "kill switch" is not defaulted to on, we're all one "corruption lost your profile" event away from having our data exposed to that shit. Not acceptable. I do not even want the code for interfacing with these monsters present on my SSD. It should only be there of you intentionally download it from a.m.o.
in reply to Firefox for Web Developers

yeah you guys are ignoring obvious refutations of this warm and fuzzy nothingburger of a claim
in reply to Firefox for Web Developers

What would AI do in a browser anyway? Does it make rendering HTML faster? Thats all a browser should do.
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” that almost nobody wants, while this developer time and energy could be better used for all the features that the people that still use FF actually want.
  • and as an added β€œbonus”, including AI in the browser itself instead of leaving it to extension developers apparently requires more and more effort from fork maintainers to remove that crap, that should never have been included in the first place.

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.

This entry was edited (1 month ago)
in reply to Firefox for Web Developers

How about a single switch for the advertising features? Some of the ad stuff is hella risky and can be a pain to turn off one preference at a time blog.zgp.org/turn-off-advertis…
Unknown parent

mastodon - Link to source
Sam Livingston-Gray
@jackwilliambell I recently heard 3 expressed as "trust is gained in drops and lost in buckets"
in reply to Firefox for Web Developers

I blew up somewhat over you calling your users confused and playing fuckfuck games with the meaning of opt-in, so as an apology I’ve made a small donation to the future of the web

servo.org/sponsorship/

This entry was edited (1 month ago)
in reply to Firefox for Web Developers

We dont want any of that shit. Stuff it.

Organisational fork of Mozilla. πŸ‘ˆ

Mozilla took a billion dollars from google. Mozilla is poisoned.

How about a coalition of distributions take over a fork of last years Firefox?

#fedora #ubuntu #susi #linux

in reply to Kevin Russell

@kevinrns you’re free to fork it. But the main problem is. You’ll need a ton of money to keep it running.
in reply to Lucas 🌐

@P_Lucas
Like much bigger projects forked elsewhere. In fact entire distributions have been formed out of volunteers.

Organisational coalition to fork Mozilla is the path. Auditing.

Fun fact there are more distributions than CPUs.

in reply to Firefox for Web Developers

Why is this opt-out, rather than opt-in?

I see that you've written that once we "use the kill-switch" it will remove the features, but that's an opt-out.

If you take consent seriously, have an "opt-in" button.

in reply to PJ "chinga la migra" Coffey

@Homebrewandhacking the individual features will be opt-in, but that means there may be toolbar buttons to activate the feature, or prompts like "do you want to translate this page". Whereas the kill switch would remove all of those.
in reply to Firefox for Web Developers

So features will be available but opt in to switch them on, kill switch removes the features altogether?
in reply to PJ "chinga la migra" Coffey

@Homebrewandhacking

Individual features can be enabled/disabled. Disabling will remove any downloaded models (which are only downloaded on interaction with the feature).

The 'kill switch' disables all features, including any new ones added in future.

But, with the kill switch active, you can still enable individual features - that was the bit that was missing.

⇧