If a kill switch is planned, then it should be the first thing implemented. Turns out it isn’t.
There really isn’t a reason not to switch to LibreWolf at this point.
It’s a shame that Mozzila is set on wasting developer time on tools people do not want, and in turn wqsting LibreWolf dev time on removing it.
Aodopting an opt-out model instead of opt-in is also bullshit. You should do opt-in, measure adoption and THEN maybe consider making it default, if it’s high. It probably won’t be. People who don’t care about what their tech does are already using chrome or edge.
I’d be also surprised if it didn’t do stuff like re-enabling itself after updates or some shit.
It should be the other way round - AI opt in.
Let’s hope this is true. Doesn’t sound very consistent to me. A “modern AI browser” but with AI disabled. And what’s the killswitch for if it comes with everything disabled and opt-in anyway?
And what’s the killswitch for if it comes with everything disabled and opt-in anyway?
A vain attempt to placate people who are still going to find some reason to complain about AI regardless of what they do.
Ah. There’s the backtracking I was expecting. They keep doing this. Making a feature opt-out instead of opt-in and then backpedalling as soon as the users revolt, offering a “happy medium” to placate us so they can continue to do the same shit over and over again.
Google does this with chrome too.
Thank the Nine



