![]() ![]() 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.Ī 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. Automatically droping working connections is hostile activity - it creates lots of churn which costs extra bandwidth for trackers and peers alike.Ĥ.BitComet seems to favor uploading to other BitComet clients, even when getting faster download speeds from other clients. ![]() Sadly, Azereus is reported to do this too. ![]() (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.)ģ.BitComet disconnects and reconnects to download more than is fair via optimistic unchoke - (which is meant to give new arrivals something to share. 1.BitComet incorrectly uses DHT on private torrents/trackers, even ignoring BitComet's user's settings NOT to if the tracker briefly goes down!Ģ.BitComet deliberately misreports upload and download amounts to trackers and seeds in order to get the "lion's share" of upload bandwidth from seeders. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |