| ▲ | runtimepanic a day 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 a day ago | parent [-] | |||||||||||||||||||||||||
I 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. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||