Announcement for ProtoSchool's first libp2p tutorial #517
Conversation
| <img class="w-75-ns w-100" src="/124-libp2p-comes-to-protoschool/libp2p-ipfs-animation.gif" alt="libp2p animation representing libp2p being extracted out of ipfs" /> | ||
| </div> | ||
|
|
||
| Historically, companies that produced peer-to-peer applications like like Skype or BitTorrent created their own protocols to support them. Those protocols made a lot of assumptions about the environments they'd run in and the needs they'd meet, making them incredibly hard to upgrade or adapt to new environments. libp2p, however, has been extracted from its original implementation as the networking stack of IPFS, and can now serve a broad variety of use cases. While everyone building on IPFS or Filecoin is using libp2p as a dependency, many folks are using libp2p independently or embedded in other projects such as X, Y, and Z (insert examples that don't use IPFS or Filecoin). |
There was a problem hiding this comment.
| Historically, companies that produced peer-to-peer applications like like Skype or BitTorrent created their own protocols to support them. Those protocols made a lot of assumptions about the environments they'd run in and the needs they'd meet, making them incredibly hard to upgrade or adapt to new environments. libp2p, however, has been extracted from its original implementation as the networking stack of IPFS, and can now serve a broad variety of use cases. While everyone building on IPFS or Filecoin is using libp2p as a dependency, many folks are using libp2p independently or embedded in other projects such as X, Y, and Z (insert examples that don't use IPFS or Filecoin). | |
| Historically, companies that produced peer-to-peer applications like like Skype or BitTorrent created their own protocols to support them. Those protocols made a lot of assumptions about the environments they'd run in and the needs they'd meet, making them incredibly hard to upgrade or adapt to new environments. libp2p, however, has been extracted from its original implementation as the networking stack of IPFS, and can now serve a broad variety of use cases. While everyone building on IPFS is using libp2p as a dependency, many folks are using libp2p independently or embedded in other projects such as X, Y, and Z (insert examples that don't use IPFS). |
Since Filecoin uses IPFS, maybe it's not necessary to mention it + IPFS is more of a dev tool than Filecoin I believe, so just using IPFS sounds better.
Just 2 cents.
There was a problem hiding this comment.
@zebateira I'm inclined to leave this because (a) not everyone knows Filecoin uses IPFS and (b) libp2p sounds like it's more popular if we include both. @yusefnapora What do you think? Could either of you help with these examples I didn't insert? 😂
Co-authored-by: Zé Bateira <jose.bateira@protonmail.com>
Thanks @jennwrites! Do you know that those ones used libp2p independent of IPFS, which is what I'm going for, or shall I check in with the libp2p crew to confirm? |
|
The deploy is now in progress for the tutorial itself, so I hope to be able to publish this post later this afternoon once we've confirmed it's live. I've updated to today's date and fixed my header image, GIFs, and examples, so I think we're good to go as soon as that's resolved. |
|
re: timing sounds great! The libp2p examples I'm fairly certain are outside of IPFS, but please feel free to confirm! |
terichadbourne
changed the title
WIP
Do not merge until we've done these things (hopefully Wed/Thu of this week):