From @mcast on Thu Sep 08 2016 21:12:33 GMT+0000 (UTC)
“Bad data” blocklists are introduced in #106, #36.
Official, default block lists are dangerous, they make the maintainer a target of law enforcement requests and bring lots of political hassle with them over what belongs on such a list and what doesn’t.
Block lists should require explicit and separate user opt-in to reduce censorship incentives. Having them maintained by a 3rd party also helps to unburden developers from such politics.
Sadly, this seems likely true in at least some regions.
So how are blocklists to be
- generated and maintained?
- The big “official” organisations can publish lists of any data they care to declare “bad”.
- If I assert copyright on my data, can I publish a blocklist for unauthorised derivatives I find?
- for fetching some files, you could go to prison or even just disappear
- if for copyright files (e.g.
.mp3) maybe it’s ok to have it if you paid; no re-sharing
- some files you just prefer not to see at work, or show to children
- provided as default, or discovered?
- by users/servers in an administrative region; like CRDA
- according to the carriers’ preference e.g. businesses, for their staff
- by user preference, e.g. things many people find they want to un-see
- for abuse of power-to-censor
- for chilling effects
to be sure to keep coders out of legal & political trouble?
Copied from original issue: https://github.com/ipfs/faq/issues/176