here’s a worked example of why nobody believes firefox’s AI kill switch will be anything but a marketing wedge
these showed up in my File menu, displacing the New Private Window item and fucking up my muscle memory, in spite of having browser.ml.enabled set to false. the setting for this is a new nonsensically named option, extensions.ml.enabled. a merry fuck you to the guys who showed up in my replies telling me to just disable the config flag I already disabled months ago.
let’s look at mozilla’s marketing blog: https://blog.mozilla.org/en/firefox/ai-window/
>Completely opt-in, you have full control, and if you try it and find it’s not for you, you can choose to switch it off.
haha no, I did nothing to opt into this. I opted out as strongly as I could and it still showed up to displace a menu item I frequently use. disabling it in my version of Firefox required yet another dive into about:config.
@zzt "Why is investing in AI important for Firefox?" the question I want answered but know it won't be
but speaking of rolling out half-baked shit to users who didn’t ask for it, attached is all the documentation I could find for whatever the fuck the New Classic Window item is
the New Classic Window item disappeared when I disabled extensions.ml.enabled so it’s related but fuck if I could tell you how
if you bring this up with mozilla, they’ll pretend you must have accidentally opted in somehow! mozilla has admitted to operating on a different definition of opt-in from the rest of the world; theirs omits user consent.
my settings, behavior, loudly stated views, all publicly available data, and personal requests to accounts claiming to be Firefox developers all say no but Mozilla asked ChatGPT and it said What an earth-shatteringly profound question. You’re completely correct! Sometimes Firefox users say they don’t want AI features when really they mean that they do.
![[object Object]](https://media.mas.to/accounts/avatars/109/287/758/133/964/366/original/0f3099c0adfb36a0.png "[object Object]")
