@Mastokarl @alahmnat @firefoxwebdevs I don't think anyone has illusions that the web was free of bullshit before LLMs.

But LLMs have made it vastly vastly easier to generate bullshit, and as an absolutely inevitable result, LLM-generated bullshit is now drowning out everything else.

This seems pretty uncontroversial to me.

@GuillaumeRossolini @firefoxwebdevs Yeah ... it's a very strange user experience to turn on turning off AI.

I still really think the Standard/Strict/Custom Privacy UI design is a good template.

@duke_of_germany @firefoxwebdevs https://mastodon.social/@firefoxwebdevs/115859962325484652

@firefoxwebdevs I'll be switching remaining friends and family members over to Librewolf and/or Vivaldi before this update drops

AI in the browser is a disaster waiting to happen and it's sad to see Mozilla think so little of its users opinions

@firefoxwebdevs The damage is done. I am not coming back. You're wasting money and effort on useless shit instead of making Firefox better for my purposes. So I'd rather support a fork that removes all that AI code the hard way. I don't trust your "controls" to do anything at all.

Regarding "[...] I'm not personally in a position to action results of such a poll":

Are you in the position to bring up the results of such a poll in a meeting with your team & boss?

And if so, did you?

@jaffathecake @firefoxwebdevs

@duke_of_germany @firefoxwebdevs they're aware of the sentiment. I'm sure you're aware that Mastodon has a high representation of folks who don't like AI, so presenting evidence that Mastodon users don't like AI is kinda… well… not really useful.

@duke_of_germany @firefoxwebdevs whereas the poll I actually ran, which shows how target users of the feature view translation, was practically useful.

@firefoxwebdevs Calling them "enhancements" sure is a choice.

@viralobscurity both Librewolf and Vivaldi have built-in translation, which people overwhelmingly consider to be AI (https://mastodon.social/@firefoxwebdevs/115849251057488746). Vivaldi even sends the text to a server for translation.

Your choice is your own, but we are up-front about the AI features we have.

@vex I’ve been on the side of the maintainer who misjudged something and has gotten heated responses, and from that experience I think that I got too heated.

It’s really hard not to get defensive when there is a lot of heat already.

And FF devs are regularly taking the heat, even though most just try to do good work.

When you know someone receives a lot of aggression already, you shouldn’t add more.

I realized too late that we were effectively ganging up on them.
@firefoxwebdevs @dveditz

@condret @mike our translation, tab naming, and link preview features all use local models.

The AI sidebar doesn't, but I'm assuming that's obvious as you select a third-party service to use.

@ArneBab people indicated pretty strongly that they wanted a way to block AI, but re-enable particular features https://mastodon.social/@firefoxwebdevs/115849251057488746.

It used to be referred to as a 'kill switch', which is much stronger wording, and a lot of folks wanted that wording (see the replies https://mastodon.social/@firefoxwebdevs/115740500373677782). But I think "block" is a reasonable middle ground. I understand that you don't.

@firefoxwebdevs @sarah the fact that this is the best you can do with a technology designed from the ground up to ignore/bypass consent, is exactly what's pissing everyone off.

The very fact that this technology is being implemented directly into the browser telegraphs the intention to not keep that promise.

@ArneBab @vex @dveditz I found our discussion here reasonable, fwiw. I appreciated your viewpoints here, even if I didn't agree with all of them.

@vex @sarah is there a particular AI feature/flow that you feel bypasses consent?

Models are downloaded after the user indicates they want the feature.

@firefoxwebdevs Sounds great. Fuck your browser.

@firefoxwebdevs
Better late than even later… thank you!

@wojtek
Because optIn is better than optOut.

@fabio @firefoxwebdevs