New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What extensions are important/mandatory for a modern bittorrent client? #22
Comments
Looking at what other clients support, I think we should support:
|
By encryption you mean the data encryption , if yes then it will be great. I think anonymising the user is heavily required looking at how the snooping is being done everywhere. |
Yes, I'm referring to BitTorrent protocol encryption. Anonymizing the user is another issue completely, and much harder. |
And then I thought people at Stanford can do anything..Must be harder..;) |
Mutable torrent support would be really good. Here's a BEP39, although I'd prefer an implementation that let torrent clients push a new torrent file iff it's an updated version. |
I added individual issues tracking each of these extensions.
Note that I couldn't find any substantive background info on bittorrent UPnP, so I left that one off for now. @feross I think this issue should be closed as answered and further progress should be tracked in these sub issues. |
The bittorrent extension protocol (BEP10) allows clients to innovate and come up with their own extensions to the protocol. A few extensions, like torrent metadata (BEP9), DHT (BEP5), and the PORT message are widely supported. WebTorrent already has basic support for these.
However, there are probably other extensions that are de facto mandatory in modern clients. Once nearly all clients support a feature, I'd guess that clients without the feature are at risk of being ignored, or at a speed disadvantage. Which extensions fit this description?
If you're familiar with bittorrent, please feel free to chime in. I'd love more help from people who know about bittorrent!
The text was updated successfully, but these errors were encountered: