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

Bring Embedded Tracker closer to BEP Spec #9958

Open
jslay88 opened this Issue Dec 3, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@jslay88

jslay88 commented Dec 3, 2018

Continued from a discussion in PR...

I would like to get the tracker brought up to date, something at least closer to the BEP spec.

Here are some things which I have seen missing through some perusal of code. Please excuse me if I mention something the tracker already supports.

Tracker doesn't respond with compact peer list when compact=1:
http://www.bittorrent.org/beps/bep_0023.html

Tracker doesn't respond with peer id when no_peer_id is not present and compact=0.
http://www.bittorrent.org/beps/bep_0003.html

 corresponding to peers, each of which contains the keys peer id, ip, and port, which map to the peer's self-selected ID, IP address or dns name as a string, and port number, respectively. 

Tracker doesn't respond with complete and incomplete.
https://wiki.theory.org/index.php/BitTorrentSpecification#Tracker_Response

Tracker doesn't allow user to define min interval in advanced settings.
https://wiki.theory.org/index.php/BitTorrentSpecification#Tracker_Response

Tracker doesn't support IPv6 announcement. (Draft BEP)
http://www.bittorrent.org/beps/bep_0007.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment