Luca Matteis

What do you think of `select.js`? It should be asynch but it's actually synch. I will merge this once I get a chance of testing it all. Thanks!

Sorry for the late reply @stormslowly Essentially you can use promises in the function generators and dynamically create another b-thread that requests an event: ```js bp.addBThread('foo', ++priority, function *() {...

Sorry have no time to implement it. It's a pretty easy addition though.

Why transfer? If you need a feature submit a pull-request to my version or just fork it. I don't see the rationale behind transferring ownership. That's not how open-source projects...

perhaps this is related https://github.com/diasdavid/webrtc-explorer

Found this paper from last year's P2P computing conference: http://www.tsn.hhu.de/fileadmin/redaktion/Oeffentliche_Medien/Fakultaeten/Mathematisch-Naturwissenschaftliche_Fakultaet/Informatik/Soziale_Netzwerke/pubs/Andreas.Disterhoeft_2015_IEEE.P2P.2015.ShortPaper_Protected.Chords.in.the.web.Secure.p2p.framework.for.dosn.pdf

One main problem that I've noticed studying this is that with regular DHT you save IP addresses in a routing table, so when you go offline, and then go back...

@maxogden I see. Perhaps one way to implement it would be to have a separate table be populated with signaling servers which is used for bootstraps across disconnects. Peers (WebRTC...

@xuset from a high-level, how does this work? WebRTC connections need to be bootstrapped from zero every time you close the tab. Therefore your routing table cannot be saved across...

@pguth right, but that would put too much control on the signaling servers. To disrupt the network you'd just need to shut down a bunch of signaling servers.