IPFS Lisbon meetup livestream is on!
https://www.youtube.com/watch?v=gvGAJbywq-0 …
-
-
Replying to @yoshuawuyts
"There's currently a huge bounty on breaking SHA-2, namely the worth of the whole bitcoin ecosystem"
1 reply 1 retweet 2 likes -
Replying to @yoshuawuyts
"There's a whole lot of work in IPFS going into not only working with DNS, but also with future naming systems such as Namecoin"
1 reply 3 retweets 3 likes -
Replying to @yoshuawuyts
PSA: I might be tweeting a whole bunch about
@IPFSbot today, sorry I'm not sorry
1 reply 1 retweet 5 likes -
Replying to @yoshuawuyts
Juan is talking a whole bunch about apps not working on spotty connections - peeps _should_ be able to just communicate over local networks
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
Lol, one way to work around npm caching not being great - run a local proxy registry mirror caching packages into content addressable blobs
1 reply 1 retweet 2 likes -
Replying to @yoshuawuyts
Blockchain documents are now up on the screen, very cool :D
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Go IPFS and JS IPFS are going to be update to run on IPLD soon - change is needed because it's now know how apps are being built
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
Touching on IPLD now, "Interplanetary linked data" - scheme to move data across planets
1 reply 0 retweets 2 likes -
Replying to @yoshuawuyts
"If you can't move data between planets, you need to redesign your system" - lol
2 replies 1 retweet 1 like
Drawing parallelisms between connectivity on planets and other remote areas. Spotty connections, latency - is making sense so far
-
-
Replying to @yoshuawuyts
Many of todays web 2.0 applications are too heavy to run in these types of situations. Big payloads, don't anticipate spotty networks
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Talking about history of naming schemes - plan9, git, bitcoin, ethereum - built on merkle trees
1 reply 0 retweets 0 likes - 31 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.