-- Originally posted on the official forums by me--
Please avoid BitComet above V. 0.90. if the tracker you're using is incompatible.
This problem has been present for a long while, but I thought the developers soon would make it possible to choose what user-agent BitComet should report with.
It seems like the V. 1.0 will be the best release yet, as it has been a while since a new BETA version has been released, hence we must suppose that the developers are working hard on this new release and adding new features.
Until the V. 1.0 release, where I truly hope that the "Hybrid Announce" will be made user-changeable, I must advice you to avoid using BitComet on private trackers, which has blocked browser user-agents.
How do you know, if the tracker you're using is "incompatible"?
It's very easy to find out.
1. Load BitComet and start a torrent from the private tracker.
2. Now, instantly, go to the "Trackers" tab.
3. Look at the tracker-message. If it looks like one of these two messages (or something similar) the tracker is "incompatible" with BitComet above V. 0.90:
Why?
1. When BitComet is done leeching a file, it'll automatically send an "annouce-wire" to the tracker, telling the tracker that it is done leeching a particular file (Completed). If the tracker receives this message, the tracker will add the torrent to the "snatched-list", if the tracker supports this.
It'll also add the last megabytes to your down- and upload stats, remove the torrent from your "leeching list" and put it on the "seeding list" instead.
2. When you manually stop a torrent, BitComet will send another "announce-wire" to the tracker. This time it tells the tracker that you have stopped the torrent, and it should remove the torrent from your "leeching list" on the tracker page.
Now, the tracker does not receive these two messages, if the tracker is "incompatible" with BitComet. BitComet does not do a "hybrid announce" when stopping torrents.
This is indeed a bug, but if it gets possible to manually choose what user-agent BitComet should announce with, then the bug would be fixed.
Let's hope this gets done in V. 1.0. Until then, please use either BitComet V. 0.90 or BitComet V. 0.70.
Good Regards,
XSTREM - Unofficial BitComet Ambassador.
