4 ms·
For any given type of item of information about me that a site may be able to see and want to use, it is going to fall into one of these groups: • Items that I
by tzs 8y ago
For any given type of item of information about me that a site may be able to see and want to use, it is going to fall into one of these groups:
• Items that I'm OK with sharing with every site.
• Items that I'm OK with sharing with some sites, but not with others.
• Items I'm not OK with sharing.
It might be nice if there was a standard list of items and a way to tell my browser which group each item falls under, and a standard way for the site to tell the browser which items it wants. The browser could then tell the site which group each such item falls under, and the site could dynamically generate a permission request and privacy disclosure that just covers those things I'm not willing to share with every site.
Maybe add some other dimensions to this covering things like how the site uses the item (internal use or shared with third parties; just to provide the services I use or also for marketing, for example), the category of site, and the location of the site.
- idlewords 8y agoWhere this consent model gets tricky is things like group chat. Who owns this exchange between us? You? Me? Hacker News?
- anon1m0us 8y agoWhy not everyone who participates in the exchange? Or perhaps only the words they contribute?
- schoen 8y agoWell, there's a fact that idlewords responded to tzs, which could be viewed as a fact about idlewords, a fact about tzs, a fact about both of them, or a fact about this overall conversation, among other things. For copyright purposes idlewords already has copyright in his post, but I don't think that's the kind of "owning" that we're talking about here. There's also the fact that, for example, you read what idlewords and tzs had to say to each other, and the fact that some people in the discussion upvoted their comments. That's already a lot of different sorts of facts about this conversation, and doesn't even reflect everything that HN (or readers) knows.
- burtonator 8y agoIt's not really possible due to the issues with some small leakage and classification of the events. For example, you might be ok with sending errors your app generates to the vendor so they can improve their product but there could be leakage. Filenames could leak and if you named something with PII then that leaks as well.