If you beat up the firefox team long enough you actually get the required controls.
@isotopp I found it a bit weird that it defaulted to "on"/"do not block" when I had set all the .ml. options in about:config to "off" ages ago already..
@isotopp Counterpoint: Mozilla has nothing but contempt for their users, and are treating us like complete idiots
@liquor_american @isotopp
I'm just waiting to read "well, 'everything' is a debatable concept..."
@RnDanger @isotopp They've already pulled that shit when they posted a poll heavily implying that translation was a big reason to keep everything enabled by default
@liquor_american @isotopp oof, i was riffing on their confusion about "consent' but i guess i shouldn't be surprised πŸ™ƒ
@liquor_american @isotopp As opposed to the other tech providers?
@rrb @isotopp "Yet you participate in society! Curious! I am very intelligent."
@liquor_american @isotopp I am open to alternatives.

@isotopp

I've blocked everything for now but I might turn on translations and image alt text.

@isotopp no, it should have been opt-in, not opt-out.
@maaneeack doesn't the "new and current (...) are blocked by default" mean opt-in or is that part only "if opt-out"?
@gorobar They made the 'killswitch' so that you can individually re-enable certain features. That's what that notice means.
Opt-in would mean that no AI was enabled by default, and you could choose to enable it.
@maaneeack OK, I understand - thanks for the info.
I guess it's better than nothing like this, but definitely should have been opt-in.
@isotopp But we don't have to stop, right?

@isotopp

How hard do we have to beat them up to get them to stop working on this AI stuff and focus on making the browser good?

@isotopp and the required controls might or might not do what they say, or might not do it in the next commit. Who can say? Mozilla is not credible on the topic.
@isotopp
No, the AI features shouldn't be there to need turning off!
They haven't listened ever I can remember on GUI (it's destroyed) or changes on plugins, or fixing bugs.
I've dozens of non-AI settings I now have to change in about:config.
They've made abysmal changes to Thunderbird. Using Firefox since 1.0.4
@isotopp I would be thankful if they could simply tell me what's actually going on instead of providing me with multiple "Learn more" links.
@isotopp No, it should have been opt-in.

@isotopp
1. The wording is absolute garbage. There is no enhancement with AI, it's annoyance and spyware.

2. I'm already off FireSlop and will keep it that way for the foreseeable future. πŸ€·β€β™‚οΈ

3. It should have been opt-in from the beginning and not an opt-out after community going rampage. πŸ€¦β€β™‚οΈ

@isotopp but now they gate translations behind #AI? Fuck that noise.
@binford2k it works well in practice. The global switch set to off does not prevent you from enabling individual settings.
@isotopp I missed that, thanks
@isotopp not a fun of AI, but the fox is cute ​​
@isotopp Well... no. They shouldn't have bothered with AI from the begin with...

@isotopp

I'd have preferred AI-free (and I'm not planning on going back from AI-free forks anytime soon) but it's a start.

@isotopp
Block?

Still no option to disable. Words have meaning.

Like an ad blocker vs not having ads. Or a popup blocker vs if javascript never had a window.open function in the first place. "Block" is the one we use when trying to stop the browser from doing something, but the bad guys keep finding workarounds.

@isotopp waterfox! Dont trust Mozilla..
@isotopp too late. I've switched to Vivaldi; I'm not going back.
@isotopp Calling the new killswitch "Block AI enhancements" is such a shitty dark pattern.
@isotopp and instantly blocked this shit. πŸ‘
@isotopp Luckly, Firefox 140 ESR is still a thing.