Talking about history of naming schemes - plan9, git, bitcoin, ethereum - built on merkle trees
-
-
Replying to @yoshuawuyts
Talking about problems with git: doesn't support file chunking - not great for large files. Future versions of git should hopefully fix this
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Original motivation for the web: applications were built for only certain systems - couldn't easily be ported - needed common abstractions
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
Same should apply for other protocols - allow merkle trees talk to each other
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Turns IPFS into a merkle forest - allows connecting different merkle trees with each other. bitcoing <-> ethereum <-> git - glue layer
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
IPLD: distributed hash chain format for merkle trees (hope I quoted that right, hah)
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
ooh, IPLD might be standardized in the near future - either w3c or IETF - yaaaas, fingers crossed
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Touching on libp2p now - this is what I was waiting for :D
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
"It's straight forward to create a p2p library that works for 80% of the people, but the question is: how do you reach the remaining 20%?"
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
So libp2p has a concept of different cagegories: transports, discovery, peer routing, content routing
1 reply 0 retweets 0 likes
"We broke the end to end model by stuff like NATs, libp2p tries and fix some of those breakages"
-
-
Replying to @yoshuawuyts
libp2p allows different tradeoffs to be made, application can express what it requires and the best fitting transport will be used - neat!
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Peer routing: find a specific peer on the network. Content routing: find a piece of content somewhere on the system. "who" vs "what"
1 reply 0 retweets 0 likes - 19 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.