So I was sitting back wondering if maybe a couple other features have the possibility of being implemented at all.
The first one I was curious about is also another hook option, I know that hash verification can take a few seconds to a few minutes depending upon how much data you are trying to push out. Is it possible to get a hook option after the verification has completed? I know that tailing the debug file would give me this, I was hoping to not have to build a logging dependency into my wrappers / hooks.
Second, is the ability to have a whitelist / blacklist tracker list. If I were to specify a group of trackers in the config file with say bt-tracker-whitelist then my client could then only connect to those hosts, as well as having the option to blacklist certain trackers, using bt-tracker-blacklist, that way I'm not connecting to places I feel are less than reputable. An example line would be bt-tracker-whitelist=http://example.com,http://announce.example2.com
Third, is the ability to encrypt the password stored in the config file for the xml-rpc-passwd. SHA1, MD5, something else besides plaintext would be awesome.
And finally, going way out on a limb, would be the ability to set a challenge password for all of my clients, that way if they didn't have / know the challenge password they wouldn't be able to interact with one another. This is just thought of as a way to implement some what of security mechanism for swarms inside of large environments.
I appreciate anything you could do with these ideas, I greatly appreciate what you have done thus far with the program; I'm finding it very useful and easy to leverage on a large scale. Thanks...