Feature Request Report Completion % to seeders

[Shadowtester]

I have had several people and a one admin on one of the trackers I use request Deluge to report % completion to the torrent seeders so I thought I would pass on that request.

[funchords]

The basic protocol does not provide for such messages. Do they have a particular extended message that they'd like to see? If so, what?

Most clients figure this out by combining the client's BT_BITFIELD handshake message with the BT_HAVE messages received there after, and dividing that by the number of pieces reported in the torrent metafile.

e.g. Torrent has 1000 pieces. Client had 650 pieces when he connected and reported 150 more while he was connected. Client currently has 800 pieces and is 80% complete.

[Bonzo]

If a user of Deluge is downloading from a single seeder using Azureus, the seeder will be shown 0% completion. Whatever the conventional way of calculating this is, it's clear that seeders using Azureus are not getting the feedback they're used to, and will be annoyed by not knowing how much the downloader still needs.

This used to be a problem with uTorrent 1.4 (I think). The reasoning there was that seeders need not be told what the downloader has, only what the downloader is requesting, so bandwidth can be saved. The complaints forced a rethink.

[lunke]

Azureus probably calculates the progress through the bitfield/have messages. The bitfield message may be omitted if the leecher doesn't have any pieces at all. So what you want to look into is if libtorrent sends have-messages to seeds.