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.
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.
Something that hasn’t been made clear: Firefox will have an option to completely disable all AI features.
We’ve been calling it the AI kill switch internally. I’m sure it’ll ship with a less murderous name, but that’s how seriously and absolutely we’re taking this.
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.
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