@firefoxwebdevs In the context of granular control they're quite good though? ie I can accept/delete them per domain as I like. I voted for the middle option as the only granular option, but granularity can be more fine-grained than that, is what I mean. And privacy is all about control over the granularity. Time-limited access tokens with very specific permissions are maybe a better analogy.
scribe@mastodon.sdf.org
@scribe@mastodon.sdf.org
Indlæg
-
Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation. -
Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.@firefoxwebdevs I think it's less about use cases and more about general trust, as privacy often boils down to. If you're talking about an AI "kill switch", you're talking about trust in what's been defined as "AI", and trust in the browser developer as a whole.
Once definitions are murky, there's an area open for ongoing redefinition. One way to adopt a "private by default" approach is to follow what cookies do, for instance, and allow users to allow limits to the extents of permissions.
-
Firefox uses on-device downloaded-on-demand ML models for privacy-preserving translation.@firefoxwebdevs I'm not a fan of this all or nothing approach to functionality. What happened to the paradigm of things being scope and/or time-limited, eg just for this page, for x minutes?