No one’s against a feature being opt-out unless they actively dislike that feature. You’re not going to make a post about the context menu items you don’t use unless you have some political opposition against them.

Nobody complains about the ¤ key on their phone’s English QWERTY keyboard, or the “generate QR code from tab” feature in Firefox that I’m sure you’ve never used. Neither of these features is opt-in, and yet you’re content with them. It’s because you don’t have any political opinions about the features themselves. You don’t actually care about opt-out when the feature doesn’t bother you.

Most features in most software are either opt-out or unremovable, though. It’s clearly not about that to you, it’s about the association with AI

This is just my opinion, but I think it’s reasonable to require your user to go to the settings if they want to remove a context menu item.

In fact, I think they’re going above and beyond here. Most people never use “Inspect Accessibility Properties”, yet they added it here with no option to remove it, and yet no one’s complaining.

I think the cause of this outrage is people reading too much into Firefox’s AI features. Firefox doesn’t bundle an LLM or make requests without your permission. It doesn’t put AI overviews on your pages. It didn’t remove existing functionality to make room for the new buttons. And it doesn’t shove any of the features into your face. It’s just a context menu item that opens a website in the sidebar if you choose to click on it.