3 ms·
And the file could be published on IPFS so hosting it is not relevant. Hash would ensure that you're getting the right file - from any IPFS node. There is even
by nileshtrivedi 9y ago
And the file could be published on IPFS so hosting it is not relevant. Hash would ensure that you're getting the right file - from any IPFS node. There is even an HTTP bridge for IPFS content.
- StavrosK 9y agoThere are many HTTP bridges, I run one: https://www.eternum.io/ https://www.eternum.io/ Latest easylist: https://www.eternum.io/ipfs/QmdDtvs1QaQQG6NMpc2cpncA4zVZqgUKUs3LQdTtLditx7 https://www.eternum.io/ipfs/QmdDtvs1QaQQG6NMpc2cpncA4zVZqgUK... If you decide to use IPFS for distribution of your list, I'd be happy to donate some Eternum credits so you can pin it.
- ballenf 9y agoThat may be great as a parallel project, but the point of this one is to take head on legally any challenges. At least that's my reading of his explanation. He's blazing a trail that others who may be more risk averse or have more to lose can then follow. Actually blocking these domains is kind of a side benefit, especially since the most likely people to download the extension are those who could just as easily achieve the end result themselves in other ways. Unfortunately there is no legal concept of waiver in this situation: the other side can pick and choose weak targets at will and avoid someone who will fight back. Just one more critical flaw in the DMCA system. Contrast this with trademark law where one must universally enforce the mark or risk losing it entirely.
- xorcist 9y agoIf you can distribute the hash to all users, you can probably distribute the blocklist as well. The size isn't the problem.