My perception was that it's still much too easy to trace the origin of content on IPFS and therefore not suitable for illegal things.
My perception was that it's still much too easy to trace the origin of content on IPFS and therefore not suitable for illegal things.
For anonymous content, you'd probably have to handle the encryption/decryption yourself and use IPFS as the distribution.
Changing a single byte changes the entire hash, so blacklists aren't a great solution if censorship is what you're after.
I will have to do a bit more research to see how the default clients handle caching popular, unrequested content.
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.
> 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)?
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.
However, I am hard pressed to find any sizable HN discussion that doesn't mention it? It's basically worrying about what shows up as downsides when Googling, since most potential customers are starting from zero.