Hacker News Reader

I'm genuinely curious which part ipfs solves here? Given that it's still accessed via browser/domain wouldn't they just block the dns or even ip? In which case this is no more resilient than say multiple domains and dns entries and proxying on from there to a central database (which could be run in a jurisdiction over which Spain has little control and which they would have to discover first anyways)

View on HN

Data on IPFS is accessed over P2P, not over IP. ipfs.io is just running a gateway. Anyone could do that. In fact; if you were to run IPFS on your computer, you'd probably have your own gateway on your localhost.

Somebody would just make their own public gateway, and the government would need to block another domain. Of cource, running IPFS for yourself would take away any need to use a gateway.

I'm not an expert, but I think it goes like this: ipfs, similarly to torrent, is p2p. Given an address (that's a hash for the file), your client will look for other peers that have the file, and get it from them. Unless they find all the peers holding the file or start blocking ipfs traffic, there's little they can do to prevent access.

Reply on news.ycombinator.com