IPFS is awesome even in terms of DMCA. And fundamentally, it isn’t really different today: if the copyright trolls contact you, it’s because you’ve shared a file with a specific hash. The hash (among other things, of course) is important, otherwise they wouldn’t survive in court. This is actually a big plus for IPFS: you just blacklist a hash, the default nodes will comply, and unless you tell your node to opt out of the blacklists, you won’t be able to “ipfs get” the file, and this will be network-wide. If someone changes the hash, e.g. by printing a carriage return to the end of the file, then all the copyright owners need to do is blacklist the new hash, and it will be network-wide immediately. It’ll probably still be a whack-a-mole, but i’s way better, easier & faster than location-based blocking, removing search results from Google and what not. IPFS is (in probably every respect) the perfect solution.
JayBrown
32
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Editing/deletion of content and power dynamics | 18 | 2143 | May 23, 2017 | |
| IPFS and GDPR/CPRA compliance | 17 | 1661 | April 21, 2022 | |
| Avoid hosting of illegal material | 26 | 14532 | October 20, 2023 | |
| Problems with access control mechanisms | 7 | 776 | June 11, 2023 | |
| How can I be certain that my IPFS node is not hosting content X short of `rm -rf ~/.ipfs`? | 6 | 2193 | February 7, 2020 |