4 ms·
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 whic
by lemoncookiechip 11mo ago
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 11mo agoAnything enabled by default without prompting in an update is usually against the user.
- zbentley 11mo agoWhat 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 11mo agoPlease learn what "usually" means. If a thing USUALLY happens, pointing out times it didn't is not a counter argument.
- zbentley 11mo ago> 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.
- skywhopper 11mo agoHow? about:config doesn’t count as “the GUI”, imo.
- Animats 11mo agoWhere? I just looked in Settings.
- input_sh 11mo agoRight click on the icon → remove. The same goes for right clicking on the page → ask AI → remove.