BitTorrent Tracker Analysis : SweDVDR

[Zorvak]

The script may be something like that, but just like SweDVDR's script, it will deal with a lot of false positive, from ghostleecher, different announce time and power outage
Imagine this scenario :

Torrent X has 10 seeder and 0 leecher.
Seeder A starts seeding at 15:10. The next announce time would be 15:40
Leecher B starts leeching at 14:50. The next announce time would be 15:20
Torrent X has 10 seeder and 1 leecher now.

Leecher B connects to seeder A, and downloads 200 MB from Seeder A.
At 15:10, 20 minutes after he start downloading, there's power outage on Leecher B's computer.

announce_time = 30 minutes.
announce_time * 1.2 = 36 minutes

Every announce_time*1.2 (36 minutes), SweDVDR will start removing "dead peers".
At 15:36 Leecher B is removed from peerlist, and torrent X has 10 seeder and 0 leecher.
At 15:40 Seeder A sent his announcement, sent that he upload 200 MB.
If the script only check if the number of leecher is zero, Seeder A will be banned.

Or this ghostleecher scenario:
Leecher A copy all peerlist from Torrent Y, and paste it in Torrent Z.
Leecher A remove the tracker url from torrent Z and start ghostleeching, he's not shown in the peerlist.
The peerlist stay the same, 10 seeder and 0 leecher.
Any seeders that upload to leecher A will be banned because they send upload announcement when total download / leecher count is zero.

Still, it's better to be safe and just check "Stop faking when swarm speed is zero".

[anon]

Torrent X has 10 seeder and 0 leecher.
Seeder A starts seeding at 15:10. The next announce time would be 15:40
Leecher B starts leeching at 14:50. The next announce time would be 15:20
Torrent X has 10 seeder and 1 leecher now.

The* trackers' scripts also watch activity like this. Always wondered what they do on this situation.

And anti-ghostleeching scripts will have to deal with power failures, too.