Here, you dropped this: -

!Skłodowska!<

I think it’s quite clear there’s ambiguity (hence this discussion). How would you define opt in? Should a user not even see the button for an opt in feature?

I mean yeah, that’s a fair point, and the dev said that themselves, that the definition of opt in is ambiguous. The definition they seem to use is that AI won’t run unless you explicitly tell it to, and I think that’s ok. There’ll be a button that you can press to do some AI action and you can hide it using the kill switch.

I do hope the kill switch isn’t hidden behind 5 layers of menus

Come to think of it, I do enjoy the translation feature in Firefox

I don’t see why there is a big outrage. Sure I’m not a fan of the AI features and I certainly will disable them but it’s tot like they’re forced upon me. Some people like (want) AI in the browser and good for them, this makes the browser better and easier to use for them. For me, it doesn’t change my experience at all

(Commented this separately on purpose)

All AI features will also be opt-in. I think there are some grey areas in what ‘opt-in’ means to different people (e.g. is a new toolbar button opt-in?), but the kill switch will absolutely remove all that stuff, and never show it in future. That’s unambiguous.

Sounds like they will be opt in, not opt out

I once tried vibe coding a web app using GitHub Copilot. That motherfucker wrapped every single endpoint with

try:
    ...
except Exception:
    return "An error occurred"

What the fuck is wrong with you Copilot? This piece of shit trying to hide all the errors. If I don’t know there are errors then there aren’t errors. Apparently