Features requested

- Add some extension to incomplete files - Support wildcard in add command including recursive

Calculating ratio for very strick tracker

In order to prevent cheating peer in closed tracker, there is a very easy solution to solve this problem. However, it might be too strick. Problem: Some clients do not even try to contact tracker but they are still able to leech using historical peers information. Solution: Count amount of download by size of the torrent immediately when download its metadata Advantage: Disable cheating of unreporting clients Disadvantage: Downloading only some files may not fair

Interesting tracker's promotions

BT is very popular and some trackers do not allow non-member to leech from them to guarantee share ratio of the whole system. Below are interesting promotions for closed tracker.

1. Bonus credit - give extra upload by amount of snatched
2. Delay - do not allow low ratio users to leech new torrents
3. Golden time - turn off delay and count download only a half

In addition, many users have tried to cheat the counting system. It is mostly impossible to prevent cheating due to BT protocol. That means tracker must track not only share ratio, but also list of who want to leech and who finished each torrent for cross checking.

BitTornado 0.3.8 is now out

BitTornado: "LATEST VERSION: 0.3.8 WHAT'S NEW: maintenance release works better with XP SP2 some bugs fixed GUI width problem known, will be fixed later randomized port selection" I have successfully merged changes made in this version into CVS.

Today bug fixed

I have fixed missing quote to attribute of xml element before save. It is necessary to do so because I always unquote when read. Furthermore, I increase default rerequest interval to 20 minutes.

BTQueue 0.0.17 has been released

Due to some minor bugs in 0.0.16, I decided to release this version to fix those bugs. Furthermore, sourceforge got some problems yesterday. No one can download. Link: BTQueue

Bugs in 0.0.16

I've got bug reports of version 0.0.16. Most of them are unnecessary error message, e.g. scrape error due to network failed. Another bug relates to incompatibility of Popen4 on windows since I changed from popen to Popen4. I plan to release 0.0.17 which is a minor bug fix version very soon. Keep your eyes on btqueue!.

BTQueue 0.0.16 at freshmeat

BTQueue 0.0.16 on the front page of freshmeat.

rerequest_interval is set too low

SourceForge.net: Open Discussion: "Though I noticed some trackers banning me after a while. I figured out this was due to the setting rerequest_interval, which was set too low for most other clients and several trackers. I'd suggest setting this to something higher, like 1200 (20minutes), so users won't get banned without knowing why." Due to above suggestion, I will increase rerequest interval to 20 minutes in next version. However, you can set it to whatever you want to fit your need.

BTQueue 0.0.16 has been announced at the front page

BTQueue 0.0.16 has been announced at the front page of sourceforge.net.

Daemon/Remote in BTQueue 0.0.16

Since 0.0.16 introduces many new features, I am trying to explain how to use it efficiently. The most requested feature is to run it in daemon/service mode. Prior to this version, you (and me) have to run btqueue incorperately with screen to make it run likely in background. Actually, only some of you might want this feature and all of them run btqueue on his/her server placed at ISP. BTQueue perfectly fit the need of administrators for remotely leech/seed on share server or office. Today, you don't need screen anymore. All you want is just btqueue! However, old style btqueue is still preserved for short-term running. To run it as a daemon in the background, you have to specify daemon command.

$ btqueue.py daemon

After that, you will immediately return to prompt. Now you are ready to control btqueue anywhere by running command below:

$ btqueue.py remote

By default, btqueue.py will bind itself on localhost (127.0.0.1) to make it more secure. However, sometimes you might want to control it from anywhere. In this case, please change global setting xmlrpc_ip to 0.0.0.0 or another more specific ip. As you should already know, there are 2 ways to modify setting; 1) directly modify policy.conf and 2) call gset command in the btqueue's prompt.

>>> gset xmlrpc_ip 0.0.0.0

After modification, restarting is needed. In remote control mode, you can do whatever you used to do. Note that notifications such as start and terminate are disabled in this mode. Moreover, quiting in this mode will not terminate its daemon. In case of you want to shut down the daemon gracefully, you have to run kill command instead.

BTQueue 0.0.16 is out!

I proundly release BTQueue 0.0.16 (build 240). This version is the major change to improve both functionality and comfortability. You can get it at sourceforget.