Create browser-optimized peer discovery mechanism

[albrow]

This will likely involve adding WebAssembly support to the Kademlia DHT implementation or using a separate Peer Exchange protocol.

[albrow]

I've done some testing in the browser and doing peer discovery through the DHT works fine for now. It is fairly resource intensive so we might want to switch to something else in the future. (Setting browser nodes to be a DHT client instead of a server helps a lot).

Going to de-prioritize this and remove it from the milestone.

[joeykrug]

https://gist.github.com/joeykrug/87498d3765814c6adb38d072e3f898c2 it looks like there's a bunch of options for in browser peer discovery that can be used redundantly (pulled this example from a libp2p repo), are these other options being used in case the DHT fails to bootstrap a user (see the peer discovery section in the config)?

[albrow]

@joeykrug thanks for sharing this. We are not currently using webrtc-star or websocket-star. There is no Go implementation of those packages and and they are likely going to be deprecated. We want to focus on using tools and packages that are going to have long-term support.