the kill switch framing is interesting because it treats AI features as a coherent unit you'd want to disable together. in practice most AI features in browsers are pretty granular -- autocomplete, summarize page, translate. the users who want to disable AI usually mean 'stop sending my browsing data to a model endpoint,' not 'disable the local spell checker.' a per-feature data-flow disclosure might be more useful than a binary kill switch.
From TFA:
> For those who wish to maintain some AI functionalities, a selective blocking option is available, enabling users to retain useful features like on-device translations while avoiding cloud-based services.
I think a lot of people are simply sick of seeing "HEY NEW AI FEATURE LOOK AT ME" popups everywhere. Shove something into people's faces often enough and it becomes like a red rag to a bull. That's probably not the only thing, but it's one big motivation why some people want it.
Sure, but then the people complaining would need to recognize that that's not happening. All the AI features are local models. The only thing not local is that side window you can open that can connect to a chatbot. It's also easy to disable.
Honestly, I think people just like complaining. I think they like complaining about Firefox even more. There's plenty to complain about, but aren't there bigger fish to fry right now? Seems like complaining about some minnows while we're being circled by a bunch of great whites
People vehemently asked for a kill switch that does exactly that - kill off all AI-related features. I quite like the local LLM translations etc., but jedem Tierchen sein Plaisierchen, as they say over here.
I don't think AI features in a browser are bad, and I think people who tut-tut it are overboard.
However, I think data control is critical and any kind of implicit cloud service such as transmission to remote AI servers should be toggle-able clearly, just like search autocomplete can be done.
https://news.ycombinator.com/item?id=47077431, by dang, 4 days ago:
All:
(1) Generated comments aren't allowed on HN - this rule predates LLMs but obviously applies even more now: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=by%3Adang%20%22generated%20comments%22&sort=byDate&type=comment
(2) If you see accounts that look like they're mostly posting genAI comments, please let us know at [email protected]. That's how I found my way to these cases.
>"But I use it to help my English!!!! Who cares if it's AI if the comment is good??????????"https://news.ycombinator.com/item?id=46747998, by dang, 1 month ago:
Please don't post generated or AI-filtered posts to HN. We want to hear you in your own voice, and it's fine if your English isn't perfect.
If you don't flag this shit when you see it, HN is fucked. The commons is fucked. And you all keep upvoting and replying to comments from accounts that start posting 30 comments a day after 2 years of silence that are all one tightly packed paragraph of pablum with the same structure and tells that are harder to fix than replacing the em dash with a double hyphen.---
P.S. The actual comment is (surprise!) completely wrong. Visit Settings -> AI Controls and you will see a granular set of feature switches under the master kill switch. Each has a clear title and description and is independent.
Thing is, there's a large (or at least certainly vocal) contingent of users (and mostly techies, to boot) that view "AI" as the Devil, and transformer models as the original sin, and they want to refuse to partake, wholesale.
This feature seems to be a nod to people with this worldview.
EDIT: See e.g. https://news.ycombinator.com/item?id=47133786 liking AI features to defecating on your food. It's not a technical objection, it's a principled one.