Peer routing: find a specific peer on the network. Content routing: find a piece of content somewhere on the system. "who" vs "what"
-
-
Replying to @yoshuawuyts
Lol, "hole punching is complicated" - yuppppp. Apparently not everyone has followed the RFCs that should allow for it, hah
1 reply 1 retweet 1 like -
Replying to @yoshuawuyts
Extra category: "concensus" - touching on different protocols and tradeoffs, starting with raft
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Ooh, building concensus systems on top of bitcoin or ethereum; maybs link it back to raft - libp2p will expose a common interface for them
1 reply 1 retweet 0 likes -
Replying to @yoshuawuyts
Yesss, so contraints can specify which parts of the forest you have. E.g. an IPFS that is only accessible over Tor
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
Touching on multiformats now - self describing values. Leads to protocol agility, interop, avoid lock in
1 reply 2 retweets 1 like -
Replying to @yoshuawuyts
"My protocol will never change" - "Yes. Yes they will change. Your system will break"
1 reply 2 retweets 0 likes -
Replying to @yoshuawuyts
"It would be cool if we could have agility in a system. Upgrade from sha2 to sha3 when problems are found"
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Touching on one of the multiformats now: multihash. Others are same in spirit (boo, I wanted to hear about multistream :p)
2 replies 0 retweets 1 like -
Replying to @yoshuawuyts
check out https://github.com/jbenet/multistream … <3 -- will move to the http://github.com/multiformats org soon
1 reply 0 retweets 1 like
4:23 AM - 25 Jul 2016
0 replies
0 retweets
0 likes
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.