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.
β¦
Aaron 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.
β¦
GrayGooGlitch
in reply to Firefox for Web Developers • • •2xfo reshared this.
GrayGooGlitch
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.
Henrik Pauli
in reply to Firefox for Web Developers • • •Firefox for Web Developers
in reply to Henrik Pauli • • •happyborg
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
Lazarou Monkey Terror πππ reshared this.
Henrik Pauli
in reply to happyborg • • •happyborg
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
Henrik Pauli
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
Henrik Pauli
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
Similarly, at home (though usually only one window), I might end up preloading a dozen youtube or whatever tabs to check out later.
@firefoxwebdevs
happyborg
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
Henrik Pauli
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.
happyborg
in reply to Henrik Pauli • • •I'd have more desktops and Windows if the system could handle it!
@firefoxwebdevs
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)
Petra van Cronenburg
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
2xfo reshared this.
M.S. Bellows, Jr.
in reply to Petra van Cronenburg • • •reshared this
β¦ π Gus Posey and M.S. Bellows, Jr. reshared this.
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?
Lazarou Monkey Terror πππ reshared this.
Firefox for Web Developers
in reply to Josh βYoshiβ Vickerson • • •Josh βYoshiβ Vickerson
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.
Jennifer Kayla | Theogrin π¦ reshared this.
Josh βYoshiβ Vickerson
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.
Firefox for Web Developers
in reply to Josh βYoshiβ Vickerson • • •Jennifer Kayla | Theogrin π¦
in reply to Firefox for Web Developers • • •@josh
The kill-switch is unambiguously an opt-out option.
Firefox for Web Developers
in reply to Jennifer Kayla | Theogrin π¦ • • •Jennifer Kayla | Theogrin π¦
in reply to Firefox for Web Developers • • •Josh βYoshiβ Vickerson
in reply to Firefox for Web Developers • • •Ridge
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.
Fish Id Wardrobe
in reply to Ridge • • •Eh?!?
in reply to Firefox for Web Developers • • •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.
Firefox for Web Developers
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.
Fish Id Wardrobe
in reply to Firefox for Web Developers • • •@Eh__tweet @josh
> Some would say that's opt-in
no: unless they were peddling a shitty dark pattern, they would not.
Display Name
in reply to Firefox for Web Developers • • •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.
Display Name
in reply to Display Name • • •"Don't worry! You can opt in to remove the fly from your soup with just one spoon!"
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.
the elder sea
in reply to David Gerard • • •@davidgerard @josh @jaffathecake
I just checked on this PC and had to disable them *again.*
Jennifer Kayla | Theogrin π¦
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.
David Gerard
in reply to the elder sea • • •ToddZ β
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
Cassandrich, Shannon Prickett, Billy Smith and Fish Id Wardrobe reshared this.
Cali's Vassal Duke 4 Denmark
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
π€
Jeff
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
Firefox for Web Developers
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.
reshared this
Kevin Russell reshared this.
The Psychotic Network Ferret
in reply to Firefox for Web Developers • • •Sensitive content
"I hope we can (re)gain your trust here."
All of this should have been said over a year ago. For many, this is going to sound too little, too late. The people at the top of Mozilla have not been doing the project any favors.
"Just be glad this thread wasn't a long-ass video. It almost was."
Now _that_ would have been completely unforgivable.
Yora
in reply to The Psychotic Network Ferret • • •The Psychotic Network Ferret
in reply to Yora • • •Sensitive content
Kim Crawley (she/her) π·π
in reply to The Psychotic Network Ferret • • •Please check out stopgenai.com
Stop Gen AI β Mutual Aid and Political Activism
stopgenai.comChristophe Henry
in reply to Firefox for Web Developers • • •Christophe Henry
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?
Isaac Freeman
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.
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)
π§DaveNullπ§ β£οΈpResident Evilβ£
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β¦
π§DaveNullπ§ β£οΈpResident Evilβ£
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
π§DaveNullπ§ β£οΈpResident Evilβ£
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
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
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.
Mina
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
pgcd reshared this.
DistroWatch
in reply to Firefox for Web Developers • • •reshared this
Shannon Prickett reshared this.
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 β • • •Silmathoron β
in reply to Firefox for Web Developers • • •Firefox for Web Developers
in reply to Silmathoron β • • •2xfo
in reply to Firefox for Web Developers • • •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.
2xfo
in reply to 2xfo • • •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
β¦ π Gus Posey
in reply to Firefox for Web Developers • • •Norgg
in reply to Firefox for Web Developers • • •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
Martin AuswΓΆger
in reply to Jonathan Kamens 86 47 • • •Alex Wilson
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.
muffa
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/
Martin AuswΓΆger
in reply to Firefox for Web Developers • • •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)
Martin AuswΓΆger
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 :(
Firefox for Web Developers
in reply to Martin AuswΓΆger • • •Eleanor Saitta
in reply to Firefox for Web Developers • • •@ausi @Norgg
Fritz Adalis
in reply to Firefox for Web Developers • • •Firefox for Web Developers
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.
Amoshias
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."
Fritz Adalis
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.
Jake Wharton
in reply to Firefox for Web Developers • • •Firefox for Web Developers
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?
EQ
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.
Firefox for Web Developers
in reply to EQ • • •EQ
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?
Firefox for Web Developers
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.
deutrino
in reply to Firefox for Web Developers • • •Eleanor Saitta
in reply to Firefox for Web Developers • • •Fabian Transchel
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.
2xfo
in reply to Fabian Transchel • • •To be fair, i fully expect Firefox management is gaslighting their programmers just as well as the rest of us
Zappes
in reply to 2xfo • • •Jared White (ResistanceNet β)
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. π
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").
Kevin Russell
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.
Jonathan Lamothe
in reply to Kev Quirk • • •Firefox for Web Developers
Unknown parent • • •[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.
reshared this
Cassandrich reshared this.
[object Object]
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.
[object Object]
in reply to [object Object] • • •reshared this
jwz reshared this.
Cassandrich
in reply to Firefox for Web Developers • • •Cali's Vassal Duke 4 Denmark
in reply to Firefox for Web Developers • • •Gabe Kangas
in reply to Firefox for Web Developers • • •Jor βοΈπ
in reply to Firefox for Web Developers • • •Letβ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.
Don Marti
in reply to Firefox for Web Developers • • •turn off advertising features in Firefox
blog.zgp.orgSam Livingston-Gray
Unknown parent • • •[object Object]
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/
Sponsorship - Servo aims to empower developers with a lightweight, high-performance alternative for embedding web technologies in applications.
ServoKevin Russell
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
Lucas π
in reply to Kevin Russell • • •Kevin Russell
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.
PJ "chinga la migra" Coffey
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.
Firefox for Web Developers
in reply to PJ "chinga la migra" Coffey • • •PJ "chinga la migra" Coffey
in reply to Firefox for Web Developers • • •Firefox for Web Developers
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.