raulk

@Gozala I see. It wasn't clear this proposal is WebRTC focused. > 1. Nodes do not need to be configured (With list of ICE candidates) AFAIK, nodes don't need to...

@vmx How would a serde path work here? This is a dynamic data structure whose schema we don't know.

Yes I know, but validating the whole input would imply deserialising into ipld::Ipld, which uses owned data, so it's not zero-copy syntactical validation?

Here's a PR: https://github.com/ipld/libipld/pull/159 I'm working on removing the recursion. I have some ideas.

@Stebalien hinted that deserializing into IgnoredAny may do the trick here.

@Stebalien the way that this is built in go, the API for optimistic selection only allows us select a single protocol at a time: https://github.com/multiformats/go-multistream/blob/8d8704410c0e9960941180cb617803b16edbe301/lazyClient.go#L18 So if either `/multistream/1.0.0` or...

> go-libp2p never actually negotiates two protocols in a row. I meant the `/multistream/1.0.0` protocol, followed by protocol X. As seen by multistream-select, these are two distinct protocol proposals that...

Many thanks for writing this up so eloquently, @alexander255. Let me just rant a little bit and dump some rambling thoughts. Mapping your proposal to challenges we needed to solve:...

Pinging @tomaka and @moul, as they both have made headway bringing in bluetooth support for libp2p (rust and go, respectively). I'm curious if a `BD_ADDR` atom in the multiaddr is...

Go 1.16 uses MADV_DONTNEED by default, which should (in theory) returned memory quicker to the OS. That said, I'm happy putting this behind an env var feature flag, because it...