[lemoncookiechip]

They're all easily disabled in the GUI itself. The article is exaggerating, the closest argument is that it enables itself by default when it first updated which is fair, but they're easy to disable within the menu itself.

[skydhash]

Anything enabled by default without prompting in an update is usually against the user.

[zbentley]

What about TLS versions? Or tabs, way back in the day? Or security warnings/prevention for CORS?

All of those were, as far as I know, enabled by default and released in browser updates.

[burnte]

Please learn what "usually" means. If a thing USUALLY happens, pointing out times it didn't is not a counter argument.

[zbentley]

> Anything enabled by default without prompting in an update is usually against the user.

I believe that, of browser features released, the overwhelming majority are enabled by default (if they even can be disabled). Including TLS/https warnings, tabs, automatic page unloading, support for new HTML/JS capabilities, and so on.

Those don't generate an outcry--they're usually celebrated, in fact--so either browser updates are "usually" fine, or you have an extremely un-usual threshold for wanting things not to change.

[Animats]

Where? I just looked in Settings.

[input_sh]

Right click on the icon → remove.

The same goes for right clicking on the page → ask AI → remove.

[skywhopper]

How? about:config doesn’t count as “the GUI”, imo.