@gatesvp @firefoxwebdevs @jmax this sounds like it could be a horribly onerous task for the Moz dev teams, of course. And I think that a Mozilla viewed as on the side of the angels could get away with saying, hey this translation/JS loop detection stuff is "AI" but that's not really what you want to turn off so it's not on the list, and be trusted. But Moz is increasingly not viewed by some of its user community as deserving that benefit of the doubt.

@gatesvp @firefoxwebdevs @jmax of course there's much "AI" stuff in firefox. I'm assuming that it would all be listed, and all disableable. The CEO promised "a clear way to turn AI features off... A real kill switch" -- if all that other stuff qualifies as "AI", then that means it'll be turn-off-able, no?
I agree that it's hard to engage with non-specific anger; I think the way to add clarity to that conversation is to be specific, about which AI parts are in Moz and where they came from.

@firefoxwebdevs it would be nice if the "AI kill switch" had:
a list of each of the models used, what for, and whether they're trained on open data, each having a "disable this" switch
a thing right at the top of the list which says "I don't care, kill all this AI stuff"

but that would require putting a list of all the different things that Firefox is now using AI for and whether each is using fair models or not, which I suspect a lot of management won't want to document clearly to users