Frostwire– It has a built-in search engine, doesn’t keep logs, and offers a fast downloading speed.# It has an abusive multi-tracker implementation (announces to all trackers in all tier always).Note: It’s highly recommended to use the fastest VPN while torrenting it will provide better anonymity and security with the fastest downloading. # It also abuses super-seeding by disconnecting and reconnecting to get a slot, and basically monopolize the super-seeder's bandwidth. # If you request too many pieces from it (something around 100? or so), it drops ALL your requests. (afaik, uTorrent is working on a similar feature, but will be making it public information, so that all other clients can implement it if their authours wish to this is the only real way for this to be effective) # The new encrypt header feature in BC 0.60 gave it a very unfair advantage and would basically prefer itself over uploading to other tpyes of clients. # It has no (working) upload slot limit, so it makes the upload bandwith so streached out that each peer only gets a few 100 bytes per second or less. # when it gets snubed by another peer (basically meaning the peer refuses to give the BC client any upload because it has not been given any download from the BC client, the BC client then disconnects up to 10+ times per second to that client in an attempt to get unsnubed. # it hamers the tracker, and pays no attention to the tracker when it tells the client how long to wait before re-announce. The reason why is because of its countless "cheating like" characteristics, for example: Most of you think BitComet is "faster" than other clients, but what u don't know is the reason why. OK, most of you are wondering if the BitComet ban will be lifted here, and the answer is no, and it will most likely never be unbanned here. I disabled internet connection, i used bitcomet tracker, and 2 clients.
Here is a log generated by azureus 2.3.0.6 while trying to downloadĤGb torrent from BC0.60 and stuck to about 8MB: In fact i think it does'nt depends from bitcomet itself, but the problem lies in the last version of the other clients !Īzureus 2.3.0.6, but not with azureus 2.0.7.0īC0.60 vs utorrent 1.3.3 both on the same pc, same results :/īitlord (last version) vs azureus (last version) both on the same pc, same results :/ Ive made several tries with friends, i've made them use bitcomet 0.60 and bitcomet 0.59, no difference. If i do a stop/start to the torrent seeds resumes for another 10/15 seconds. I've a 10mbit HalfDuplex connection, it seems that BC starts seeding at very high speed for about 10, 15 seconds (it transfers usually 8MB), after that. Now it seems that i cannot seed to some clients constantly. I used bitcomet since 0.57 without any problem. Well, not really a chellenge, and maybe not directly related to utorrent, but maybe some coder could explain me why.
0 kommentar(er)
