A: knock knock
B: who's there
A: transport
B: transport who?
A: Transport yourself to attend libp2p day Oct 30th in Lisbon, Portugal 🇵🇹!
discuss.libp2p.io/t/first-ever-l…
@tomaka17@m4r73n Optimistic Protocol Negotiation covers it here: #initiator" target="_blank" rel="nofollow noopener">github.com/libp2p/specs/b…
@m4r73n@mxinden what's the status of this in other implementations?
@tomaka17 Why do you call it V1Lazy in Rust? If anything, this is Eager, not Lazy.
I've never said that publicly because I've worked on it for several years, but the libp2p protocol is a complete shit show and has always been. Don't use it for any new project.
@tomaka17@raulvk There's a couple different approaches here. I created this issue for a smaller incremental change that would reduce 1 RT (github.com/libp2p/specs/i…). QUIC helps here too, you can have a stream with just 1 roundtrip.
@tomaka17 Context: I'm a current maintainer of go-libp2p and implementer of (soon to be released) zig-libp2p. Proud to be part of the libp2p community❤️
@tomaka17 Again, libp2p isn't perfect. There's a lot of work still left to do. And I don't claim to have all the answers. But I do claim that we appreciate input and take feedback seriously. Will every suggestion be incorporated? No. Will good arguments stand on their own? Yes.
@open_sourcery@KeybaseIO@reactnative I was also really impressed with their instrumentation and how well it was integrated with Systrace. I think that the default @reactnative template should have this so that everyone can have much more meaningful systrace profiles.
Spent sometime with @open_sourcery, looking at the performance of @KeybaseIO's @reactnative mobile app.
Doing this 1:1 call was useful, and I would like to do more 1/2 hour perf deep dive sessions. If you are interested, send me a message.