Jacob Heun

So, we have a few types of interactive lessons that we've put together. Thinking more through this I think we could workaround some of these things. I'll write this out...

@terichadbourne we'd definitely like to get something integrated. We're working on finishing up the async refactor for libp2p. Once that's done, the Getting Started guide we're created would, I think,...

I think we should wait on this, and potentially look at for IPFS 0.7 once we have more information. The general idea is to avoid scenarios where we are dialing...

> I think we should probably tackle libp2p/go-libp2p-kad-dht#546 and libp2p/go-libp2p-kad-dht#566 before going to far into this though since those should help bring us down to 2-3x hop time (we expect...

It doesn't look like I do.

I believe the issue is here https://github.com/ipfs/benchmarks/blob/a8549f6c686ea0f517e164d7d565de0b0b3658b5/tests/lib/create-node.js#L55-L57 Currently it's trying to add secio to the stream muxers, which is incorrect, it should be `connEncryption`. Also, I believe secio might be...

> Can we add this to Working Kademlia for 0.6? That is the goal, I've duplicated the 0.6 milestone here and added it for tracking. > What's the status on...

I was able to replicate this locally on Boost doing retrieval testing with lassie, and it was due to an issue with the unsealing RPC connection resetting between lotus and...

> So @jacobheun what I read here is that the SP had an unseal error, canceled the retrieval, but the Lassie side recorded it as success (until it saw the...

No, a compatibility layer was added a few months ago to get interop functioning with go. Ideally we'd get both implemented together and scrap all of that shenanigans.