@Joker said:
@Kevin4fm Dug into this properly, using "#helix" as the test case — nothing is broken on your end or ours; the message is literally true.
A torrent is identified by a fingerprint of its contents, not by its name. The "#helix" you're seeding carries the fingerprint of an earlier upload of that release which was later removed from the site (duplicate cleanups, re-uploads and the like happen all the time). The page you linked is a newer upload of the same release from June 2 — same name, different fingerprint.
Please, I have a few questions:
This fingerprint you mentioned, how does it differ from the torrent infohash?
I understand that you cannot rely solely on the infohash, otherwise a torrent that is removed and then reuploaded would already inherit the data from the previous... But in what scenario, or should I ask how, two torrents with the same infohash could be treated differently by the tracker?
If kevin has a torrent already added that's giving unregistered but have peers connecting and transferring bytes... Redownloading the newly added torrent and getting the same infohash means it is for all purposes a bytesize copy of the previous file.
You said that there's nothing broken on his side nor the tracker's, but where else could it be?
I have a different version of the same client, I don't get any error, so the logical first step would be for Kevin to try a different client to see if the outcome is the same.