6 ms·
This feels less like an “anti-AI” stance and more like a trust and control issue. For browsers especially, users have very different threat models and performan
by runtimepanic 9mo ago
This feels less like an “anti-AI” stance and more like a trust and control issue.
For browsers especially, users have very different threat models and performance expectations, and “always on” AI features blur that line quickly.
An explicit opt-out makes sense, but I wonder if the more important question is whether these features can be implemented in a way that’s truly local and auditable.
If users can’t clearly understand where data goes and what runs on-device, toggles become a necessary safety valve rather than a preference.
- ronsor 9mo agoI haven't paid close attention, but as far as I can tell, Mozilla has mostly invested in local AI for tasks such as translation, summarization, and organization. As long as that's the case, I don't see any particular safety or privacy risks; if it works without an Internet connection, it's probably OK.
- forgotpwd16 9mo agoSummarization is using a chosen cloud-based AI provider.
- freehorse 9mo agoAre you sure? I see a huge spike in CPU when I long-click on a link to see the preview and summary. This is the newest summarization feature, not the older one with the chatbot on the side.
- forgotpwd16 9mo agoAh, didn't know they moved to local models. My comment was about the old chatbot-based feature.