As usual, I’ve been mulling over BitTorrent; it’s pretty simple in nature, yet still intriguing. I like it’s building upon prior foundations, it’s simple hashing and sockets… well, ok, so it mimmics the web. I can get over that. ;)
Of course, this is a double-edged sword. I happened to play off my own thoughts as to the delicate nature of this application, finding yet another issue.
Note that I have the server set to upload 25k/s max. This is the headless client, and of course, the latest 3.2 release; the CVS -CURRENT code exhibits this same issue. The client is also based off of 3.2, and contains no internal edits by myself – it merely has a slightly modified GUI front end from the default BitTorrent.
I’m really having internal conflicts with this. Do I submit a patch publically, thus letting the world know what’s wrong, and perhaps killing BitTorrent on the whole for most users at this point? Do I tell Bram and wait aeons ot see if someone else finds, and misuses this?
It feels almost as though BitTorrent is already in it’s death throws. BitTorrent is based upon ‘fair use’, for the most part, assuming that people will be willing to keep their application open post-download, just to be fair and share it with others. This issue, well, only adds to the impact of the freeloaders; if they can steal your file and bypass your superficial throttle…
This issue is prevelant in ALL versions of BitTorrent to date.