Switeck Posted December 17, 2005 Report Share Posted December 17, 2005 Firstly, BitComet cheats:1.BitComet incorrectly uses DHT on private torrents/trackers, even ignoring BitComet's user's settings NOT to if the tracker briefly goes down!2.BitComet deliberately misreports upload and download amounts to trackers and seeds in order to get the "lion's share" of upload bandwidth from seeders.(Others have said that using super-seed as a seeder often takes >200% of the torrent's size to create other seeds due to BitComet's cheating-by-default.)3.BitComet disconnects and reconnects to download more than is fair via optimistic unchoke -- (which is meant to give new arrivals something to share. Sadly, Azereus is reported to do this too. Automatically droping working connections is hostile activity -- it creates lots of churn which costs extra bandwidth for trackers and peers alike.4.BitComet seems to favor uploading to other BitComet clients, even when getting faster download speeds from other clients. The most extreme case was a private tracker/torrent on a huge college lan with "100mbps" connections -- the person who did this could download at >5mbps if using BitComet but only ~5-15 KB/sec if using µTorrent.A ban on a particular BitComet version won't affect a new BitComet version that doesn't fix the problems, or client id hacks which spoof different client+version messages. It'd be an arms race of sorts, just like AV software having to identify ever-changing viruses.A total BitComet ban would limit BitComet's author's incentive to remove the cheating, because even a noncheating BitComet version would still be partially banned till EVERYONE on µTorrent upgrades to a non-banning version.Instead of banning BitComet clients, ignore them!...by µTorrent doing a little "tit-for-tat": uploads from µTorrent to BitComet clients will always get upload bandwidth priority (High, Normal, Low) 1 setting lower than everyone else.Also retain information about ALL connected and disconnected peers in a torrent. Then, don't treat reconnecters like "new peers" which deserve optimistic unchoke. Instead, snub them! The disconnected peer list could even be used by firewalled peers to quickly retry disconnected unfirewalled peers. (It does no good to try to connect to a disconnected firewalled peer.)By targetting BAD BEHAVIOR, µTorrent could handle any client which does the same without additional code. Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.