Handling findability of illegal content

I’m sure this question has been asked before, but I’m still in the orientation phase and can’t seem to find an answer anywhere.

How does IPFS handle specifically the findability of illegal material?

To be clear, I understand that nodes can choose what content to host, I understand that C&Ds and GDPR claims can be sent, just like with the traditional web. The main difference that I find concerning is the difference the CID makes:

Let’s take the scenario of a victim of revenge porn. In the traditional web, a widely circulated url is hosted in one place. When it gets taken down, there’s no guarantee the material isn’t stored or hosted somewhere else, BUT at least the widely circulated url doesn’t point to it anymore.
In the case of IPFS, if a CID is widely circulated and a hundred takedowns are performed after endless legal action, the content will still be accessible by exactly the same CID if I understand correctly.

Is there a way to “dark” a CID, and how would that be handled? Would making a CID go “dark” go against IPFS being anti-censorship by design? If it is possible, who would decide what sort of content to do this with? Is that a centralized decision?

1 Like

What you’re talking about is managed through the system “bad-bits” found at “https://badbits.dwebops.pub/” but its my understanding that there are a few different options used thoughout the space as well.

For Bad-Bits, you can report any violations via email to the abuse@ipfs.io group. The IPFS Infra team will handle all reports. IPFS Providers in the community can use this denylist(JSON file) to check to make sure they are not pinning/hosting flagged content. A really helpful system for any public gateway work!

There was a lot said about this in this video from IPFS Camp- IPFS Service Panel - Thibault Meunier, Matt Ober & Mario Camou - YouTube