Posted: Thu May 11, 2006 6:46 pm
Azeureus is a memory hog it seems also, thats one of the reasons why I dumped it.
Yeah, that´s the main problem of Azureus, i usually just let it on when i´m not using the comp, it´s not that big deal to me.psi29a wrote:That is due the fact it is written in java, which does indeed eat a lot of resources. The good news is that it runs on just about any OS, which is double plus for me since it pays to have OS agnostic software.
Again, I would recommend not to use BitComet, I may end up banning its use. Sorry.Tempest wrote:I use BitComet, Daedelus refered it to me and so far it's working pretty damn well.
also there is a great comparison of BT clients here:Wikipedia wrote:During versions 0.59 to 0.60, BitComet was receiving bad publicity because of an incomplete implementation of the DHT feature. DHT is a protocol that can connect peers without the need of a tracker. BitComet's implementation did not respect the 'private' flag of a torrent, allowing other DHT users outside of a private site to access and download that site's files if 1) the tracker is down, 2) 'Add DHT Network as backup tracker' option is selected and 3) the torrent file has been shared out. This in turn allowed users that hadn't signed up to avoid download and upload ratio restrictions, which are common on private trackers. Many private trackers (including BitSpirit) have now banned all versions because of the flawed implementation of the DHT feature that is unfair to the peers on the private tracker. Although this problem of not respecting the private flag was solved in the 0.61 release, there are still many DHT leaks. Thus BitComet remains banned on many private trackers.
Two of the major DHT bugs were fixed with the release of BitComet 0.64. These were editing the .xml file of the active .torrent to allow not only DHT but PEX to run as well. The other bug is pasting "DHT Network" into the tracker list in the properties section of a .torrent.
BitComet's upload slot limit is known not to work. BitComet has also been accused of favoring other BitComet users on uploads, hammering trackers, dropping piece requests, and other similar "cheating" techniques.
Yes...uh...cheating is...so bad...Wikipedia wrote:During versions 0.59 to 0.60, BitComet was receiving bad publicity because of an incomplete implementation of the DHT feature. DHT is a protocol that can connect peers without the need of a tracker. BitComet's implementation did not respect the 'private' flag of a torrent, allowing other DHT users outside of a private site to access and download that site's files if 1) the tracker is down, 2) 'Add DHT Network as backup tracker' option is selected and 3) the torrent file has been shared out. This in turn allowed users that hadn't signed up to avoid download and upload ratio restrictions, which are common on private trackers. Many private trackers (including BitSpirit) have now banned all versions because of the flawed implementation of the DHT feature that is unfair to the peers on the private tracker. Although this problem of not respecting the private flag was solved in the 0.61 release, there are still many DHT leaks. Thus BitComet remains banned on many private trackers.
Two of the major DHT bugs were fixed with the release of BitComet 0.64. These were editing the .xml file of the active .torrent to allow not only DHT but PEX to run as well. The other bug is pasting "DHT Network" into the tracker list in the properties section of a .torrent.
BitComet's upload slot limit is known not to work. BitComet has also been accused of favoring other BitComet users on uploads, hammering trackers, dropping piece requests, and other similar "cheating" techniques.
I always knew there was something strange about you...now I know why. *gaspshockhorror*arke wrote:Now I feel strange for using the vanilla BT client.
Its just that you can add plugins and it has many features.Fatal_CobraX wrote:Omg..
I'm the only one who uses ABC?!
... Whats the real difference with azureus being so much better?