3 ms·
The way IPFS works though, isn't it by definition that any file you can get from one gateway, you should eventually be able to get from any gateway? In other w
by TeMPOraL 3y ago
The way IPFS works though, isn't it by definition that any file you can get from one gateway, you should eventually be able to get from any gateway?
In other words: it doesn't matter your gateway logs shows that no one ever requested a file with a specific content hash, because should one eventually request that content hash from your gateway, they'd get the file in question.
Honestly, until reading the headline, it never occurred to me what now I realize is stupidly obvious: the promise of p2p content-hash-based distribution is that it's robust and censorship-resistant, as the targeted data isn't bound to specific places, but rather is automatically mirrored and made available across the entire network. The flip side of the data being accessible from any point in the network, however, is that... the data is accessible from any point in the network - meaning that every point individually is distributing everything that's in the entire network, and is potentially liable for it all.
- sneak 3y agoA gateway is a bridge from http to ipfs. Not all nodes are gateways.
- TeMPOraL 3y agoBut all gateways are nodes. Of course, unless we're talking CSAM, no one will be targeting arbitrary nodes. But gateways are, by definition, the publishers of what's in IPFS. They are frontends to the same backend - and thus it makes sense for each of them to be liable for everything that's on the backend, i.e. the whole IPFS network.
- 22c 3y agoEhh... Does it make sense in the same way that TOR exit nodes are liable for everything on TOR, or that VPN providers are liable for everything that is downloaded via the VPN or that the ISP is liable for everything that its users download? I think that's why DMCA safe harbor exists, and it could be argued that an IPFS gateway is acting as an OSP (in fact, it's almost text-book[1]). Though, at this point, it seems that DMCA is skewed almost exclusively in favor of rights holders (or indeed anyone simply claiming to be a rights holder), that unless you're Comcast or Verizon or something, you're not going to get much sympathy from the legal system by claiming to be an OSP. [1] https://en.wikipedia.org/wiki/Online_service_provider https://en.wikipedia.org/wiki/Online_service_provider
- TeMPOraL 3y agoVPN providers and TOR exit nodes are a different beast, IMO. They're potentially liable for everything that goes through them, but it's a "push" model, not a "pull" one. Plenty of organizations don't want to interact with, or intermediate in hosting, TOR exit nodes, because they fear any kind of illegal thing could come through those nodes - but until something specific does come out, that's a risk management reason, not a legal reason. In contrast, IPFS gateways are running on a "pull" model. Anyone can come to the gateway, and pull through it anything that's stored anywhere in the IPFS network. This is meaningfully different, in the same way "users could post illegal/infringing content to YouTube" is different from "there exist illegal/infringing content on YouTube already posted, available to anyone who know the ID to put in the URL". In the former case, possibility of "bad" upload doesn't create a problem until such upload actually happens; in the latter case, possibility of a "bad" download is a problem even if, so far, no one actually downloaded the "bad" thing. > I think that's why DMCA safe harbor exists, and it could be argued that an IPFS gateway is acting as an OSP I don't have any argument against that. I assume this wasn't tested in courts yet, and the rights holders are exploiting this uncertainty, expecting that no IPFS gateway operator will try to contest the DMCA claims.
- 22c 3y agoI don't understand what you mean by push/pull in this context. Aren't I pulling content through a VPN or TOR exit node? Pulling content through my ISP? > expecting that no IPFS gateway operator will try to contest the DMCA claims. Unfortunately, even if you have a case, there are substantial legal costs involved.
- TeMPOraL 3y ago> I don't understand what you mean by push/pull in this context. Aren't I pulling content through a VPN or TOR exit node? Pulling content through my ISP? I thought this was clarifying it well: This is meaningfully different, in the same way "users could post illegal/infringing content to YouTube" is different from "there exist illegal/infringing content on YouTube already posted, available to anyone who know the ID to put in the URL". But maybe it's not, or maybe I'm making a category error here?