Feross Aboukhadijeh
Feross Aboukhadijeh
Basically, upon initialization of a WebTorrent client, we should create a port mapping using the client's listening post (`torrentPort`) and the DHT's listening port (`dht.address().port`). You can probably just add...
@lmatteis webtorrent-desktop clients that are not behind NATs can be reached by all other clients (webtorrent-desktop and otherwise). But yeah, you're right.
> #1437 actually worked and I used it. It was closed because no one reviewed it. I reopened it. We're behind on code reviews but I'm trying to work my...
There's no way to add proxy support to the browser version of WebTorrent. That will always use your browser/OS proxy settings because JavaScript in a web page can't control that,...
This package looks quite good: https://www.npmjs.com/package/socks
Yeah, that's totally fair! I think this wouldn't be that hard to support, so it'll probably happen. The `socks` dependency seems pretty lightweight. Or even better, we can avoid the...
Also, for others coming along later, this is the bounty that @Ohge is referring to: https://www.bountysource.com/issues/34324857-socks-proxy-support
Currently the tracker is required for all WebRTC signaling (aka peer introductions). PEX for WebRTC would be great. If someone would like to look into how this could be designed...
What if we simplified to just include one hop? In other words, a peer sends a list of all peer IDs they're connected to during the extended handshake. Then the...
cc @jhiesey for feedback