Skip to content
This repository has been archived by the owner on Apr 29, 2020. It is now read-only.

Legal takedown request compliance #106

Closed
josephholsten opened this issue Apr 1, 2016 · 5 comments
Closed

Legal takedown request compliance #106

josephholsten opened this issue Apr 1, 2016 · 5 comments
Labels

Comments

@josephholsten
Copy link

Many legal jurisdictions may mandate that certain content be taken down:

How may an IPFS service provider comply with these requests?

@josephholsten
Copy link
Author

some related info exists on #9

@jbenet
Copy link
Contributor

jbenet commented Apr 1, 2016

@josephholsten see #36 (comment)

@josephholsten
Copy link
Author

@jbenet nice! Eventually I'd like to flesh this out with public gateway operator guides for "How to verify you're using the appropriate denylists for your jurisdiction" and "So you've just received a DMCA takedown notice, here's how to respond"

@malakai97
Copy link

It's useful to realize that even with http takedown notices only apply to a single server. The users that have already received the content that was taken down still have that content, and there is nothing technical in place to prevent them from making it available again (nor does the takedown notice apply to them in many jurisdictions).

IPFS just makes this truth obvious.

@madavieb
Copy link

This issue has been moved to https://discuss.ipfs.io/t/legal-takedown-request-compliance/295.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants