News for hackers. Stuff that matters.
Re:Ask HN: Recommendations for Peer to Peer Frameworks? by jjallen on Sunday April 08, 2018 @10:54AM (#16786347)
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.

Re:Ask HN: Recommendations for Peer to Peer Frameworks? by lgierth on Sunday April 08, 2018 @02:58PM (#16787654)
Sorry to hear you had move to something else -- my guess is these crashes were from WebRTC, which isn't very performant in browsers yet. Especially with more than a handful of WebRTC connections, we've seen it crash regularly.

We've switched the default browser-to-browser transport in js-libp2p to a websockets relay recently, so you should give it another try.

Re:Ask HN: Recommendations for Peer to Peer Frameworks? by ComputerGuru on Sunday April 08, 2018 @05:21PM (#16788483)
Did you try to investigate the stack trace or file a bug upstream? No snark intended!
Re:Ask HN: Recommendations for Peer to Peer Frameworks? by jjallen on Sunday April 08, 2018 @10:17PM (#16789826)
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? by lgierth on Monday April 09, 2018 @05:38PM (#16797231)
We have no intention of letting libp2p stagnate - blog post with announcements coming soon!