The tracker is ignoring the `num_want` param in the announce request.

[josecelano]

It seems the tracker is also ignoring the num_want param in the announce request.

num_want is the number of peers the client wants in the announce response (peer list).

See https://www.bittorrent.org/beps/bep_0015.html

Right now:

• We always return less than 74.
• We ignore the num_want.

Originally posted by @josecelano in #262 (comment)

[josecelano]

I don't see in any BEP a reference to the numwant param in the HTTP request. Only:

https://www.bittorrent.org/beps/bep_0008.html

However, I've found other resources that apply this limit to the HTTP tracker.

• https://www.cse.chalmers.se/~tsigas/Courses/DCDSeminar/Files/BitTorrent.pdf

• https://wiki.theory.org/BitTorrent_Tracker_Protocol

• http://www.forensicinsight.org/wp-content/uploads/2013/02/F-INSIGHT-BitTorrent-Protocol.pdf

• BitTorrent.pdf

• F-INSIGHT-BitTorrent-Protocol.pdf

I will add it also to the HTTP tracker but with the name numwant instead of num_want (https://www.bittorrent.org/beps/bep_0015.html)