How does the statistic update work towards the tracker?
There seems to be a lot of confusion about how the statistics updates work. The following is a capture of a full session to see what’s going on behind the scenes. The client communicates with the tracker via simple http GET commands. The very first in this case was: GET /announce.php?info_hash=c%97%91%C5jG%951%BE%C7M%F9%BFa%03%F2%2C%ED%EE%0F& peer_id=S588—–gqQ8TqDeqaY&port=6882&uploaded=0&downloaded=0&left=753690875 &event=started Let’s dissect this: info_hash is just the hash identifying the torrent in question; peer_id, as the name suggests, identifies the client (the s588 part identifies Shad0w’s 5.8.8, the rest is random); port just tells the tracker which port the client will listen to for incoming connections; uploaded=0; (this and the following are the relevant ones, and are self-explanatory) downloaded=0; left=753690875 (how much left); event=started (telling the tracker that the client has just started). Notice that the client IP doesn’t show up here (although it can be sen