Caltrops - Rants





	[quote name="Fussbett"]My ISP is doing experiments with bandwidth shaping to try and curb the huge hit on traffic that Bit Torrent has wrought, especially with the launch of their new VOIP service. As a result I was experiencing many painful BT fluctuations and as I would change clients, ports, and settings to combat my new poor performance I would get different results, depending on the day of the week. Ray of Light was quick to label my scientific process as <a href="http://en.wikipedia.org/wiki/Cargo_cult" target="cargo">cargo cultism</a>, but I was desperate. Taking a cue from a disgruntled forum, I discovered a solution that seems to work perfectly, returning my speeds to the glory days of BT: Use BitComet's "Protocol Header Encryption" (set to ALWAYS), and set the listen port to the same port that my ISP's VOIP uses. Then... Oink. [quote]2005-12-10 - BitComet We are following the example led by other private bittorrent trackers and <b>we have banned all BitComet clients</b>. Perhaps having so many sites banning it will encourage their developers to do something about it. The reason why: BitComet, like Azureus, allows the sharing of peers via a DHT system. Azureus implemented SecureTorrents into their client, which we coded into our tracker. BitComet followed and implemented a similar private flag. Unfortunately, the BitComet authors decided not to code what they said ("BitComet will not add DHT Network as Backup Tracker even all the trackers can not be connected later, and will also disable Peer Exchange between peers") and instead ignore this flag after a period of time. If the BitComet developers create a new version which behaves as it should, we will happily change our stance on this. But at the moment, BitComet is not welcome here. If you want a replacement client, we recommend µTorrent and Azureus.[/quote] Remember that DHT makes things work <i>better</i>. The downside is that anything swapped over the DHT doesn't count towards your precious Oink ratio. SO IT'S BAD.[/quote]