Feross Aboukhadijeh

New chunk stores available: https://github.com/SocketDev/fs-access-chunk-store https://github.com/SocketDev/idb-chunk-store

@eordano Yep, I'd like to support BitTorrent v2. I haven't had time to look at it in-depth yet. @eordano If you have time, I'd love to see a PR for...

No, but I'm working on one. I'll have something to share soon. Let's use this issue to track the progress.

Yeah, they're open to a BEP. I'm in contact with folks at BitTorrent, Inc. Happy to have you get started on a BEP, @yciabaud. I can help out once you...

@yciabaud I don't think there's a need for a WebRTC peer connection BEP. Once a connection gets established, the wire protocol is 100% identical. Unless I'm missing something, I think...

WebSocket tracker and WebRTC signaling are the same thing. I created WebSocket trackers in order to enable WebRTC signaling. I think there should be a single BEP.

We actually start the discovery process right away, even before the `'ready'` event fires, which is why we need https://github.com/feross/webtorrent/blob/c5eda255ab89efe8c1d62589a5df4ee7c146397b/lib/torrent.js#L1487-L1488. Maybe we should wait for the metadata?

@roccomuso You can safely ignore this warning. It's not an issue. You can change [`EventEmitter.defaultMaxListeners`](https://nodejs.org/api/events.html#events_eventemitter_defaultmaxlisteners) to `Infinity` if you want to make the warning go away.

I think that we are doing verification of the existing file data on disk as the last step before the 'ready' event fires.

@xuset I think this is a good idea. But I think we should solve this by not creating any wires until after verification. Just returning from `_update` seems a bit...