According to unknown client ID problem posted in forum, I think it is the time to explain how BTQueue work in more detail. This post aims to let you know how BTQueue generates its client ID to report to tracker. Since I would like to know which version and release are popular in the wild, so I embedded both version and release to the client ID. Basically, a client ID is a fixed length string at 20 characters in size. For BTQueue, it consists of 4 parts.

Actually, I managed to fix a freezing bug regarding failure during hash check for a week. Unfortunately, I can’t commit the patch to CVS at cvs.sourceforge.net because of connection refused error. It seems sourceforge is trying to force every projects to migrate to Subversion as soon as possible. They don’t want to maintain CVS anymore so CVS is now very unstable and nobody takes core of them for a week.

Welcome back to the text mode. BTQueue 0.1.0 has been released with build 433. In this version, you don’t need to worry about incorrect filename encoding. Since some torrent maker softwares do not encode filename in UTF-8 as specified clearly in the standard specification, the earlier version of BTQueue created unreadable filenames. This problem is gone forever, you can specify a list of possible encodings to try. In case of you don’t provide the correct encoding, the original filename will be used instead of scrambled one. This global preference is in policy.conf.

default_encoding = shift-jis,tis-620

I have just found very comprehensive comparison of various BitTorrent clients at BitTorrent Client Shootout. Below is my summary plus my opinions.

1. BitTorrent Official Client
   1. Clean, clear, simple, and official one, DHT
   2. Open source
   3. Lack of features: download limitation, UPnP doesn’t work properly in some cases, intend to support only Windows
2. uTorrent 

Wow! BTQueue 0.1.0 seems to be the most stable version since the 0.0.1 announced. Anyway, there are still lots of bugs waiting for reporting and resolving. Today I would like to announce the official release of BTQueue 0.1.0 424. Below are change log.

• fixed incorrect error message
• added escape/unescape in xmlrpc
• handled error on startup
• added clear command to clear screen
• added auto dht

To all command-line fanclub, I am very proud to announce the latest release of BTQueue 0.1.0 418. I recommend all you to upgrade as soon as possible to take all advantage of this bug fix version. Below is the list of fixed bugs.

1. Allow to force start a session with "resume" command
2. Handle failure gracefully
3. Support private tracker with malform announce url without failure

As always, all files are available at sf.net.