this post was submitted on 19 Dec 2025
651 points (97.9% liked)
Microblog Memes
9916 readers
2827 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Since when a kill switch means "opt-in"???
You are falling for their bullshit.
I mean it seems to me the opt-in part is when they say it will be opt-in by it potentially being a button on the toolbar. Though the dev acknowledges not everyone will see that as opt-in.
Source: https://mastodon.social/@firefoxwebdevs/115740500373677782
I can understand why people have issues with that, but let's at least keep criticisms to what they've actually said?
"That feature will be opt-in. In the sense that it's on by default and you can opt-out with a button. Not everyone will see this as opt-in."
Yeah, no shit. Because that's not opt-in, that's opt-out. Pulling shit like that already makes me distrust their communication.
Ok, I genuinely might be reading this wrong and the other guy won't communicate, so:
The way I read that is "we will have a button that's there that you can click to activate an AI feature" (though it's unclear if that's actually what it'll be like when finalised). And yeah, I'd rather that was an extension or something I'd go and toggle on if I wanted. That said, I also don't consider that to be "on by default".
And before anyone misunderstands more, I hate the addition of AI in everything and don't think Firefox should do this. That's not the point I'm arguing.
So, I might be wrong on this, too... But I don't think it's too ambiguous.
They have a button that turns stuff off. Not on. So for me, it's kind of clear that they're building an opt-out solution.
If a feature needs a button to disable it, it IS opt-out, not opt-in.
You too are falling for their bullshit, as well as to my blocklist.
plonk