The Mozilla plan is to win people over to Firefox with AI features while ignoring the feedback from people who use it mostly because it's not running on the chromium engine. This makes the Gecko engine a liability for the company's mission. It's not unthinkable that they'll switch to chromium soon.

in case you're wondering about the futility of it all, here's two job openings for the Firefox team

https://www.mozilla.org/en-US/careers/listings/?team=Firefox

Incredible

https://mastodon.gamedev.place/@duke_of_germany/115853330852766984

@firefoxwebdevs @mdavis small clarification

@firefoxwebdevs introduced the concept of an "AI kill switch"

the "AI kill switch purists" you're talking about don't exist.

No serious person would think this is a good idea because it doesn't make sense. Evident by this "design" stumble at the start line

https://mastodon.social/@firefoxwebdevs/115740500373677782

@davidgerard @eckes

q1 - design one
q2 - see the post you responded to

@firefoxwebdevs

donate to servo if you can

https://opencollective.com/servo

they have a roadmap that is dedicated to making an actual browser engine, not a collection of browser features on top of one

https://github.com/servo/servo/wiki/Roadmap

@liquor_american @zzt @pixel @firefoxwebdevs As the only remaining cross-platform browser that is not chromium, Mozilla deserves nothing but pressure to do better. Defending Mozilla about anything other than making Gecko better is giving them permission to eventually be just another chromium skin

@zzt @firefoxwebdevs now would be good, before that new CMO is breathing heavily over the shoulder

@zzt @firefoxwebdevs You'd never have to say "consent", "opt in", "opt out", or "kill switch" again if you put design energy into overcoming whatever (WHATEVER) barriers are preventing all of these things being add-ons.

@zzt @firefoxwebdevs please don't call it the "design" of the kill switch when you have to ask *us* what it should kill—as some kind of transparency/openness posturing.

@zzt @firefoxwebdevs Why would Mozilla translations be built into the browser but other developers have to make them as add-ons? Or will Mozilla accept PRs for third-party translators to be built into the Firefox browser?

@firefoxwebdevs it would be compelling if the future of Firefox was to be the fastest, most secure, most efficient browser engine with the best add-on ecosystem.

It would also be compelling to hear someone from Mozilla talk about their design effort to improve add-on adoption rather than forcing add-on-level-functionality into the core product

@firefoxwebdevs It would also be compelling if a team at Mozilla were dedicated to building the best browser translation add-on on the market, for all browsers. To promote the power of add-ons and, at the same time, the Mozilla brand.

@firefoxwebdevs it would be compelling to hear someone at Mozilla recognise that you don't have this "kill switch" yet but you're already facing the problem of what to kill.

It would also be compelling to hear someone at Mozilla recognise that there is a browser and there are browser extensions and that "translation" has nothing to do with the operating system of a web browser.