Live data from Hacker News

Ask HN: Recommendations for Peer to Peer Frameworks?

news.ycombinator.com

61–70 of 78 posts

Re: Ask HN: Recommendations for Peer to Peer Frameworks?

#61
post #21

Earlier quoted context omitted.

We moved away from libp2p at the project I work on because of major instability problems in browsers. Our dapp that used libp2p would crash after a few minutes and was generally not easy to use. EDIT: I'm referring to the JS version here.

Did you try to investigate the stack trace or file a bug upstream? No snark intended!

Yes, of course, and it was WebRTC. We ended up with a better solution (encoding the metadata we were storing in IPFS in a bytes32 stored in the Ethereum blockchain).

There were extra scripts and setup. Overall moving off simplified our stack, so it was probably a good move despite libp2p's crashing.

Could be totally fixed by now for all I know.

That said, it was believed that most Protocol Labs resources were/would be devoted to Filecoin, which is probably a safe bet.

Re: Ask HN: Recommendations for Peer to Peer Frameworks?

#63

Earlier quoted context omitted.

>We're thinking of moving to this framework internally at Ethereum. Why not GNUnet? Check the recently released 181 pages long dissertation on it: https://grothoff.org/christian/habil.pdf

GPL license is probably a non-starter.

Why?

Re: Ask HN: Recommendations for Peer to Peer Frameworks?

#64

The 181 pages long GNUnet dissertation very recently got released: https://grothoff.org/christian/habil.pdf I'd strongly recommend going for GNUnet, nobody takes me serious when I say this, but it WILL surplant IP eventually.

> but it WILL surplant IP eventually.

The painful move from IPv4 to IPv6 suggests that this is unlikely. More likely is an overlay over IP, TCP, or even HTTPS.

Re: Ask HN: Recommendations for Peer to Peer Frameworks?

#65

Earlier quoted context omitted.

GPL license is probably a non-starter.

Why?

> The core of Ethereum includes the consensus engine, the networking code and any supporting libraries. For C++, this includes libethereum, libp2p, libdevcore, libdevcrypto, libethcore, libevm and libevmface.

> The core of Ethereum will be released under the most liberal of licenses. This reflects our desire to have Ethereum used in as many diverse environments as possible, even those which, for various reasons can require modifications or augmentations to the software which cannot be released to the public.

https://github.com/ethereum/wiki/wiki/Licensing

Re: Ask HN: Recommendations for Peer to Peer Frameworks?

#66
post #23

Earlier quoted context omitted.

Hey, Benji from Peer5 here - our product is really cool and helps you scale your video delivery but I don't believe it works in this case. We solve the problem of distributing HLS/DASH delivery over large p2p swarms and scaling video. Doesn't sound like it could work for OP. Thanks a lot for keeping us in mind though :)

Hey Benji. I saw you guys setting up at NAB yesterday. Would there be a good day this week to come by and talk shop?

Hey Adam, I'm not attending NAB this year - Shachar and Hadar would love to talk (shachar@peer5.com or hadar@peer5.com) in terms of technical people attending :)

Re: Ask HN: Recommendations for Peer to Peer Frameworks?

#67
post #51

Earlier quoted context omitted.

Scuttlebutt and Dat ( https://datproject.org/ ) are definitely looking like good bets right now.

Also perhaps fun to note is that we're currently hacking on a Rust version of Dat. Hopefully we'll be able to bring the Dat protocol to more languages and platforms soon! https://github.com/datrs

Oh man that makes me happy. I just posted about that this morning. Hopefully I can find a way to contribute!

Re: Ask HN: Recommendations for Peer to Peer Frameworks?

#68

Earlier quoted context omitted.

I really wish there was an additional implementation in something like Rust (personal preference, but C would be good as it's fairly easy to bind to) for DAT, because what they're doing is rather cool and the experience is tidy.

That’s in the works: https://github.com/datrs

Awesome. I'm really excited for that, I'll have to try to contribute.

Re: Ask HN: Recommendations for Peer to Peer Frameworks?

#69
I recently discovered zyre. Its from the same guy that brought us the wonderful zeromq library

While it does a lot of the connection and communication part, it lacks a way to bypass nat routers.

Here is a book on zyre http://zguide.zeromq.org/php:chapter8

I also found this thing called pwnat which bypasses nat routers without the need for UDP hole punching !

https://github.com/samyk/pwnat

I feel like if someone made a high level wrapper combining these two, we can have a very good framework.

Re: Ask HN: Recommendations for Peer to Peer Frameworks?

#70
post #64

The 181 pages long GNUnet dissertation very recently got released: https://grothoff.org/christian/habil.pdf I'd strongly recommend going for GNUnet, nobody takes me serious when I say this, but it WILL surplant IP eventually.

> but it WILL surplant IP eventually. The painful move from IPv4 to IPv6 suggests that this is unlikely. More likely is an overlay over IP, TCP, or even HTTPS.

>The painful move from IPv4 to IPv6 suggests that this is unlikely. More likely is an overlay over IP, TCP, or even HTTPS.

GNUnet can function as an overlay and an _underlay_ simultaneously, quoting from the dissertation:

> GNUnet is an overlay network, as it is initially supposed to primarily operate over the existing Internet network. However, GNUnet does not assume that this is always the case. For example, GNUnet can also operate directly over WLAN or Bluetooth to create an ad-hoc wireless mesh network, and with the GNUnet “PT/VPN” subsystems we can run TCP/IP over GNUnet. So in this configuration, GNUnet would be an underlay network, a bit like MPLS or B.A.T.M.A.N. [NAL07]. In reality, we in fact expect to see both at the same time: some peers will run over the existing Internet, while others may connect to GNUnet on Layer 2.

Post reply on HN