Skip to content

Instantly share code, notes, and snippets.

@joepie91

joepie91/gist:65db672cafd8ad0deae89d3bbc8e7f85

Created July 12, 2016 16:06
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save joepie91/65db672cafd8ad0deae89d3bbc8e7f85 to your computer and use it in GitHub Desktop.
Save joepie91/65db672cafd8ad0deae89d3bbc8e7f85 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
gistfile1.txt
[17:33] <joepie91> so like, the big problem with IPFS-based things is that nobody feels responsible for maintaining availability
[17:33] <joepie91> which is fine for popular things like torrents with thousands of seeds
[17:33] <joepie91> but not for small/uncommon things
[17:33] <joepie91> there's no central server with a backup regime which is responsible for availability
[17:33] <joepie91> in one way, that is a feature
[17:34] <joepie91> but in another way, it means that none of the peers are likely to have a similar availability regime or guarantee
[17:34] <joepie91> because everybody thinks "oh, it's distributed, I can just rely on the other peers"
[17:34] <joepie91> it's a game theory problem really, and unless it's solved, this trend of building everything on top of IPFS is going to result in *massive* data loss in the next 2-3 years
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment