3 ms·
It's as much infamous for illegal content as hard disks are. That is, you can choose to host some, but you can also choose not to.
by StavrosK 9y ago
It's as much infamous for illegal content as hard disks are. That is, you can choose to host some, but you can also choose not to.
- prophesi 9y agoYeah, it will eventually support having blacklists. So if you get a cease-and-desist letter, you can simply blacklist the offending content. It doesn't completely solve the issue, but it should help mitigate getting into legal trouble with it. For anonymous content, you'd probably have to handle the encryption/decryption yourself and use IPFS as the distribution.
- StavrosK 9y agoIt supports blacklists now too. The bigger mitigation is that IPFS is a "push" and not a "pull" system, so you only store content you have explicitly requested.
- joshfraser 9y agoYour blacklist becomes someone else's favorites list. Changing a single byte changes the entire hash, so blacklists aren't a great solution if censorship is what you're after.
- prophesi 9y agoYep, and even the content you've explicitly accessed, it's garbage collected unless you pin it. So that helps further mitigate the issue, in case you mistakenly stumble upon undesirable content.
- book_mentioned 9y agoAll content received is automagically re-distributed by default, correct? It is similar to BitTorrent in this regard; very different from the more common client/server paradigm. I will have to do a bit more research to see how the default clients handle caching popular, unrequested content.
- AgentME 9y agoNo, if you run ipfs, you only host what you choose to host and things that you have recently requested. Your node doesn't passively accept content from others to host. (Otherwise, a joker would probably saturate the entire network's hosting capacity with /dev/urandom, or everyone would saturate the network's hosting capacity with their own encrypted backups, etc.) I think there must be something wrong with the way ipfs presents itself, because I see this misconception (that just running ipfs causes you to host anything) often.
- kodablah 9y agoIt's likely due to people thinking that "distributed" means "distributed by default". IPFS needs to gear it's docs to make people think in terms of Bittorrent (i.e. pinning, seeding, etc) and not in terms of RAID (i.e. sharding, high availability).
- book_mentioned 9y ago>> All content received is automagically re-distributed by default > you only host [...] things that you have recently requested Thank you for taking the time to correct my misunderstanding, but is this not restating what I wrote? Or are you rejecting the other portion of the comment discussing caching popular content (never requested/received)?