reporting left=0 to tracker for new torrents from magnet link

[GoogleCodeExporter]

when adding a new magnet link you should be reported as a leecher, so i expect 
it to report to tracker left=1 or if the magnet was provided with an xl=size(or 
dl=size?) parameter, then to report left=thesize.

this causes issues trying to use magnet link with tracker since the tracker 
adds you as a seeder instead of leecher...

libtorrent 0.16.17 with Deluge 1.3 on archlinux

Original issue reported on code.google.com by dda...@gmail.com on 25 Dec 2014 at 4:45

[GoogleCodeExporter]

is it possible that the tracker you're looking at was added via the tracker 
exchange protocol? Such trackers are considered slightly less trusted than 
normal trackers, and some stats is omitted (i.e. set to 0).

as far as I can tell, trackers added as part of the magnet link should send 
proper stats, and before we have the metadata left is set to 16kB.

Original comment by arvid.no...@gmail.com on 26 Dec 2014 at 1:25

[GoogleCodeExporter]

no, the tracker was in the magnet link itself, and i have also edited code not 
to load tracker exchange extensions (code change flags=0 and only add 
ut_metadata, pex, metadata_transfer and smart_ban)

that brings up the other topic... what a horrible idea to have tracker exchange 
on by default.(i know thats kind of a deluge issue, but meh it shouldnt even 
turned on unless needed!)

with DHT, why tracker exchange? it seems unnecessary, trackers should be phased 
out unless you WANT to connect to a tracker like specifically to track stats. 
and that is why i had to disable it... i tried using a passkey system and ended 
up swapping passkeys with someone else using deluge :(

Original comment by dda...@gmail.com on 26 Dec 2014 at 5:59

[GoogleCodeExporter]

And if you want I can send you tcpdumps of Deluge 1.3.11 running with Tracker 
Exchnaged NOT ADDED, running libtorrent 0.16.17 and until the metadata is 
downloaded it always sends left=0

maybe this was changed some time between 0.16.17 and 1.0? it would be nice of 
it was fixed in the 0.16 branch tho, since deluge does not use 1.0 yet, and 
most distro packages, even "bleeding edge", are still 0.16 also

Original comment by dda...@gmail.com on 26 Dec 2014 at 6:48

[GoogleCodeExporter]

no updates on this? will it be fixed in 0.16.x? or must i use 1.0?

Original comment by dda...@gmail.com on 7 Jan 2015 at 11:23

[GoogleCodeExporter]

I cannot reproduce this with the head of 0.16 branch (and I can't think of any 
fixes in there that would affect this).

Could you provide some more details? For instance, could you post a magnet link 
with a tracker that reproduces this issue? (it doesn't have to point to a valid 
torrent, just a valid tracker).

Is it a UDP or HTTP tracker you're seeing this with?

Original comment by arvid.no...@gmail.com on 8 Jan 2015 at 6:09

[GoogleCodeExporter]

OK it is working correctly after all... just did a test, both UDP and HTTP 
reporting properly. i must have been mistaken and was looking at an announce 
where i was actually starting seed from .torrent, sorry.

testing with 0.16.17 it looks like it is sending left=16384 on the initial 
announce in both HTTP and UDP(0000 0000 0000 4000 ... what a pain that was 
decoding the hex packets). i also see someone else's Deluge 1.3.6 working 
correctly.

closed! thanks and sorry again, it just didnt even pass my mind that i was also 
starting some torrents from .torrent to seed :(

too bad utorrent 2.x, which the majority of my friends use, does report left=0 
on initial magnet announce :( they finally fixed it in 3.x but no one wants to 
use 3.x because of the ads it comes with...

any chance you could provide a fixed utorrent 2.x exe? i know you can do it :P

Original comment by dda...@gmail.com on 10 Jan 2015 at 3:54

[GoogleCodeExporter]

Original comment by arvid.no...@gmail.com on 13 Jan 2015 at 9:31

• Changed state: Invalid

[GoogleCodeExporter]

you know you can turn off the ads under advanced settings, right?

Original comment by arvid.no...@gmail.com on 13 Jan 2015 at 9:32