@chillicampari @firefoxwebdevs @joepie91 ️ But that alone won’t be enough to rebuild trust; I’d like to suggest something that would help with that, but unfortunately that’s far outside my wheelhouse
️

@chillicampari @firefoxwebdevs @joepie91 ️ The best thing you could do in Firefox is to completely remove the “AI” “features” that are built on the lie and contributing to the harm. The next best would be to move them to plugins that are not installed by default. The next best is the “kill switch”, but with “killed” as the default, and ideally, as you say, not a single switch but a set of them.
️

@chillicampari @firefoxwebdevs @joepie91 ️ After y’all lied to us, encouraged harm to us, set us up to add to that harm, and reverted us to that setup after we opted out, we don’t trust you anymore.

It’s alright to address lesser issues like the builtin translation, but that doesn’t address the main issue or rebuild any trust.
️

@chillicampari @firefoxwebdevs @joepie91 ️ The main issue is Mozilla as an organization embracing the lie that LLMs possess something resembling human intelligence, welcoming the full variety of harms caused by their implementation and use, integrating their use into unnecessary “features”, and enabling those “features” both by default and reverting them to enabled after updates.
️

@chillicampari @firefoxwebdevs @joepie91 I’m kindof amazed that Mozilla can’t distinguish which changes led to the backlash. I think that’s why this whole thing feels more like putting on a show than like a genuine attempt at reform.

The timing alone makes it clear that the builtin translation was not the issue. Sure, moving it to a plugin would be an improvement, and requiring user action to enable it would be smaller improvement, but that was the case before.
️