I could probably run a tracker/10mbit seeder on d393 instead of providing http services on it. It basically has to be one or the other. If you want torrents on that one then I will work on providing them for the next release past 1.2.
If that is the case then I would recommend to stick to HTTP, since several ISPs do throttle torrents, or users simply can't get them to work properly while HTTP will likely work fine. If there would always be a couple 500KB/s mirrors available then it would be a good idea to run a tracker and encourage that as the main method for distribution but not if it is the main method with next to no alternatives
Actually, I think I have solved this problem. Torrents can use multiple "Web Seeds". You define one or more servers that have the full file in the torrent and that way I can distribute the files from my HTTPd's without having to run a torrent client on the server itself. This enables people to grab the file and distribute via torrent AND download direct. But you are right, if we don't convince people to use torrents over HTTP then the whole system is useless.