John Hiesey

I actually spent some time thinking about this problem a few weeks ago and I think a WebRTC DHT may be feasible. I'll add my thoughts here soon.

I've actually been working on a somewhat different DHT architecture here: https://github.com/jhiesey/webdht At this point the code is pretty messy and mostly undocumented. I hope to get it cleaned up...

@dcposch if it works well I want to look at making node bindings for it as well.

The original reason for adding `torrent.rescanFiles()` was to allow adding data into webtorrent after a torrent was already started, specifically for a use case the Internet Archive has. I agree...

I wrote the stale while revalidate logic for socket.dev and can confirm it works like @feross said above. To clarify, we always return data on that endpoint even if it's...

I know that Chrome doesn't route `localhost` through proxies when running locally, but I'll have to test it with Sauce Connect to be sure. Http polling combined with certificate bumping...

I'm actually in the process of writing a replacement for `http-browserify` with much more compatible stream support. It looks like @substack hasn't had the time to maintain this module, and...

See use cases here: https://github.com/libp2p/js-libp2p-webrtc-star/issues/177#issuecomment-500303109

@solanoepalacio @kibertoad I'm also interested in implementing this, potentially as soon as this week. What I have in mind is a chainable method on the query object, tentatively named `abortOnSignal`....

The object to be returned by `createReadStream` should be a node-style readable stream. What you need to do on your end is documented here: https://nodejs.org/api/stream.html#stream_class_stream_readable_1 Essentially it boils down to...