@jaffathecake @duke_of_germany @firefoxwebdevs evidence was clearly that "folks who don't like AI" don't like AI *BUILT INTO FIREFOX*

you are wasting everyone's time and misrepresenting all the arguments as an irrational denial of AI that others might find useful.

It was always about the absurdity of integrating something, ANYTHING, that is not critical to web browsing, directly into the browser instead of making it a plug in, on equal ground to 3rd party developers.

Instead, this nonsense

@firefoxwebdevs @giacomo
If it presents the option and doesn't say what it's doing that's not informed consent.

The "first launch" popups that y'all normally do with a descriptive splash screen and a big button that can be skipped to enable the features in the first place is a *perfect* place to present it where people who do want it will see it

@davidgerard @duke_of_germany @jonny @jaffathecake @firefoxwebdevs holding up Mozilla as some sort last bastion against the tide is pretty absurd. They’re the poster child of failing to adapt!

Does this mean that Mozilla knows what they’re doing here? Hell no! They’re all a bunch of idiots. But they are idiots that understand that the Google largesse is ending, and a world with three corporate controlled key infrastructures is Bad.

@fasterandworse @duke_of_germany @firefoxwebdevs let me be absolutely clear, yet again: I do not consider the arguments being presented here to be irrational.

If you feel I've said that, can you point to where?

@duke_of_germany welcome to our safe corner of the internet, @flytox!

We can only speak for ourselves, and we've never added AI to our browser because our users are happy with taking the decision to use or not use AI in their own terms, instead of having it forced down their throats because it "has" to be built-in. Some thought we were being too "old-school" by not jumping on this bandwagon, since everyone else was doing it, but honestly, we're just listening to our community, the way we've always done.

You can read our whole stance from august '25 here: https://vivaldi.com/blog/keep-exploring.

@jaffathecake @froztbyte @barubary what I'm hearing here is "the correct reaction is to harass every single person involved in this debacle until they're too afraid to pull more of this shit"

@jaffathecake @duke_of_germany @firefoxwebdevs

you said that it's not really useful to know that people who don't like AI don't like AI

and then you said:

> To be clear, I'm not someone who has personally found AI generally useful in browsers (aside from a couple of one-off automations), but my feelings aren't strong enough to deny those features to others.

Jake Archibald (@jaffathecake@mastodon.social)

@froztbyte I suppose that's literally true. But, I also think a mountain is made out of the molehill that is AI in Firefox. The vast majority of the dev time is on other things. To be clear, I'm not someone who has personally found AI generally useful in browsers (aside from a couple of one-off automations), but my feelings aren't strong enough to deny those features to others.

Mastodon (mastodon.social)

@fasterandworse @duke_of_germany which part of that is calling people irrational?

@firefoxwebdevs
That's the first tying tried. The app works perfectly fine with or without but only when opening the tab list it differs from long delay.

I have tested with over 100 tabs in version 12x and it is still snappier than 147 with less than 50 tabs.

@ada would you feel comfortable filing a bug report about this on https://bugzilla.mozilla.org/home?

@jaffathecake @duke_of_germany Jake, let me be absolutely clear, yet again. The pushback has not been against AI, it has been against AI being integrated into Firefox. Every time you say these things which continue to ignore this distinction you are gaslighting our positions into being some kind of irrational request that breaks the laws of physics and not something that is completely rational and worthy of an honest response.

@fasterandworse @duke_of_germany let me be absolutely clear, yet again: I do not consider the arguments being presented here to be irrational or crazy.

One guy directly compared me to a rapist today. I felt that was irrational, but I don't think that's what we're referring to

@liquor_american @jaffathecake @duke_of_germany @firefoxwebdevs @davidgerard

What Jake has done here — perhaps this was his goal — is change the topic of the discussion from "Does AI belong in Firefox?" to an increasingly recondite and trivial row over who said what and why are they acting this way. I guess one might call this artful deflection. But it actually looks like somebody ducking the hard question. "Naa naa naa, I can't hear you!" crowed Jake's subconscious. Verbatim.

@giacomo @alextecplayz ok. Some features of video calling (watching, chatting) are available without granting microphone access, but maybe location access is a better example.

@firefoxwebdevs Question: did Mozilla heard and considered 966 answers (on their own blog, so not so fedi biased) and why not?
https://connect.mozilla.org/t5/discussions/building-ai-the-firefox-way-shaping-what-s-next-together/m-p/113012

@giacomo @firefoxwebdevs I detailed how Mozilla uses dark patterns in Link Previews to get people to enable AI: https://www.quippd.com/writing/2026/01/06/architecting-consent-for-ai-deceptive-patterns-in-firefox-link-previews.html

You may enjoy reading it.

@nieuemma @ambiguous_yelp @firefoxwebdevs Well, unlike what they are doing elsewhere, there is an edit history. They could go back.

@firefoxwebdevs Make it an optional extension.

@da_667
Wow, this quickly became a shit show.