Legal takedown request compliance

[flyingzumwalt]

From @josephholsten on Fri Apr 01 2016 02:03:38 GMT+0000 (UTC)

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

• Court injunction
• DMCA takedown notices, like GitHub - github/dmca: Repository with text of DMCA takedown notices as received. GitHub does not endorse or adopt any assertion contained in the following notices. Users identified in the notices are presumed innocent until proven guilty. Additional information about our DMCA policy can be found at
• Roskomnadzor requests, like GitHub - github/roskomnadzor: deprecated archive — moved to https://github.com/github/gov-takedowns/tree/master/Russia

How may an IPFS service provider comply with these requests?


Copied from original issue: Legal takedown request compliance · Issue #106 · ipfs-inactive/faq · GitHub

[flyingzumwalt]

From @josephholsten on Fri Apr 01 2016 02:04:50 GMT+0000 (UTC)

some related info exists on https://github.com/ipfs/faq/issues/9

[flyingzumwalt]

From @jbenet on Fri Apr 01 2016 05:56:44 GMT+0000 (UTC)

@josephholsten see https://github.com/ipfs/faq/issues/36#issuecomment-140567411

[flyingzumwalt]

From @josephholsten on Sat Apr 02 2016 02:30:16 GMT+0000 (UTC)

@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”

[flyingzumwalt]

From @malakai97 on Wed Oct 19 2016 18:56:52 GMT+0000 (UTC)

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.