here’s a worked example of why nobody believes firefox’s AI kill switch will be anything but a marketing wedge
-
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.
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
-
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.
-
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 the deployment of the new feature flags will continue until the user opts into defeat, sagging from exhaustion at having to defensively check their browser every 72 seconds
this fucking pattern got big with facebook (you know, that beacon of user consent) since like **2012**, it is absolutely fucking wild to me that any moz person does this shit with a straight face then calls it choice. absolute fucking gaslighting
-
@zzt the deployment of the new feature flags will continue until the user opts into defeat, sagging from exhaustion at having to defensively check their browser every 72 seconds
this fucking pattern got big with facebook (you know, that beacon of user consent) since like **2012**, it is absolutely fucking wild to me that any moz person does this shit with a straight face then calls it choice. absolute fucking gaslighting
@zzt and then of course this toot stands a chance to get the bonus round of some weird fucker koolaidmanning through the wall and arguing about whether gaslighting has absolutes
-
@zzt and then of course this toot stands a chance to get the bonus round of some weird fucker koolaidmanning through the wall and arguing about whether gaslighting has absolutes
@froztbyte
steelmanning
koolaidmanning -
@zzt "Why is investing in AI important for Firefox?" the question I want answered but know it won't be
@spinnyspinlock @zzt Long story short, Google wants it.
-
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.
@zzt
This has to be the clumsiest dropdown menu I've ever seen, especially the fact that neither the "AI window" nor "Classic window" options list keyboard shortcuts.
If this keeps up, it'll only be a matter of time before distros start shipping Librewolf (or other forks) as the default browser. -
@zzt
This has to be the clumsiest dropdown menu I've ever seen, especially the fact that neither the "AI window" nor "Classic window" options list keyboard shortcuts.
If this keeps up, it'll only be a matter of time before distros start shipping Librewolf (or other forks) as the default browser.@zzt Mozilla pumping their highly publicized, CPU/RAM-hogging feature while neglecting to give it a key combo would've been unthinkable only 5 years ago. -
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.
@zzt coming soon:
neoclassical window
pop window
baroque window
rock window
dubstep window
deconstructivist window
abstract windowno, none of these will have documentation either. that’s what the chat sidebar (also in 17 flavours) is for
-
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.
@zzt they should add "Export To Another Browser..."
-
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
@zzt this is confusing. I wonder if it is something like Coke, New Coke, New Classic Coke
-
@zzt "Why is investing in AI important for Firefox?" the question I want answered but know it won't be
@spinnyspinlock @zzt because it's important to some major investor(s), most likely. Follow the money.
-
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.
-
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.
@zzt wtf… what am i even to assume each of these means
new window -> not private, not AI
new AI window -> not private, yes AI
new classic window -> ???
new private window -> private, not AI…?no clue why all these are needed, they don’t even seem mutually exclusive. maybe firefox ai invented the classic window just for you? (/joking of course… i hope!)
-
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.
@zzt Your fury is entirely warranted, they're a treacherous brood and deserve to be called out. There is a way out of this though.
The easiest browser migration I ever did in over two decades was from firefox to librewolf, which I can wholeheartedly recommend. No idea why just copying .firefox to .librewolf insidr my user's home directory did not work, but transplanting the contents did the trick.
• Installed librewolf, launched and closed it once.
• Copied over the contents of the two profiles from .firefox to .librewolf in my home directory. Mixed them up initially, due to their names being cryptic a f and no obvious way of telling which is which, so at first bookmarks and settings didn't show.
• Deleted the contents inside the profiles and copied again from sources, but to the opposite destination each, to fix it.
• Launched librewolf, could barely tell the difference now that all was back where it belongs.Hope that helps!
-
@zzt this is confusing. I wonder if it is something like Coke, New Coke, New Classic Coke
-
@zzt wtf… what am i even to assume each of these means
new window -> not private, not AI
new AI window -> not private, yes AI
new classic window -> ???
new private window -> private, not AI…?no clue why all these are needed, they don’t even seem mutually exclusive. maybe firefox ai invented the classic window just for you? (/joking of course… i hope!)
@mrs_malice I think the New Classic Window item makes me so angry because it implies that there’s a planned future where New AI Window is the default and the non-AI window is effectively deprecated
-
@zzt wtf… what am i even to assume each of these means
new window -> not private, not AI
new AI window -> not private, yes AI
new classic window -> ???
new private window -> private, not AI…?no clue why all these are needed, they don’t even seem mutually exclusive. maybe firefox ai invented the classic window just for you? (/joking of course… i hope!)
@mrs_malice @zzt it's only a natural evolution of LLMs deciding what's best for us that they start procedurally generating the user interface, i can't wait!!!!
-
![[object Object]](https://media.mas.to/accounts/avatars/109/287/758/133/964/366/original/0f3099c0adfb36a0.png "[object Object]"){kind=avatar}
