Michiel De Backker

Ok, thanks for the feedback. I'll try to find some time for the initial small steps like the number of address types. PS: Maybe `dgraph-io/badger` could be an interesting embedded...

I've been busy working on the WebRTC library itself. Still interested in this thought. I just need to find the time. The tracker side of WebTorrent probably doesn't need WebRTC...

If you have any questions, the #pion channel of the gopher slack hosts a vibrant community that loves to discuss all things WebRTC.

Playing around with adding Dial and Listen. However, it's not directly clear how to handle the `streamIdentifier` and `defaultPayloadType`. We could: * Add them to the method signature or config....

Just to flesh out our options here: [pion/webrtc](https://github.com/pion/webrtc) is a pure Go WebRTC stack. The entire stack is implemented in user-space on top of UDP. It is developer friendly and...

For your information: We built a pure Go WebRTC implementation at [pions/webrtc](https://github.com/pions/webrtc).

FYI, there is a parallel effort at https://github.com/neelance/go_js_wasm_exec.

No, sorry, it's been a while. I assume it's some part of the JSEP spec that was skipped.

The [go-webrtc-aside-transport](https://github.com/Jorropo/go-webrtc-aside-transport) uses WebRTC for muxing.

Bit of background: My goal is to fill in the missing WebRTC support in go-libp2p. This library contains the first step in that direction: a port of [js-libp2p-webrtc-direct](https://github.com/libp2p/js-libp2p-webrtc-direct) which is...