[StavrosK]

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.

[book_mentioned]

All 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]

No, 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]

It'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).

[jstanley]

I wonder how much of it is the NSA and GCHQ's of the world trying to scare people away from using IPFS...

[kakarot]

Willing to bet that guy didn't read the docs, maybe this is a public relations issue.

[book_mentioned]

>> 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)?

[AgentME]

Oh, I just realized I missed the word "received" in your first sentence! I don't have much to add to how you actually worded the sentence.

I think the automatic re-sharing of recently requested content is only for a short time period (elsewhere someone mentions 30 minutes). Probably not anything anyone should rely much on; it just sounds like a bonus to maybe soften the blow a little bit if you get a lot of activity suddenly.

[prophesi]

Yeah, 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]

It 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]

Your 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.

[atrus]

Blacklists are double hashed, so they aren't useful for finding 'bad' content.

[tscs37]

And who can assure that these blacklists won't be manipulated for someone's gain? Ie, surpressing activity they don't like on the network?

[prophesi]

Yep, 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.