@spectator1: good spotting. Exactly the way I would fix it.
Every time I see that nick I think of bob, but I guess you were probably around for all those fun and games, you old fart
The next release will probably be nothing like the last one.
That one was a bit rushed and shoddy, this one is from ground up. It'll have a lot more features though.
It'll also more than likely be split into two branches, one for public and one for private.
To adress a couple of points raised by Lope333:
Captcha systems are designed as a way of determining whether the poster is human rather than spam prevention. A human could post 100 times a minute even with a captcha in place. If someone starts to bomb your forums with posts, I always see it as better to deal with that person rather than limit all your other users.
Requiring username and password for upload is a waste of time with this code really. The cookies are protected by having the IP address hashed into them, taking out a major source of account hacks. It still leaves 3 possibilities.
1) They know your password, in which case this will not stop them.
2) They are on your computer. This would stop them, but if they are using your computer they can more than likely bluff an admin into resetting their password. The next version will include a recovery script for passwords, which means they could do it without involving an admin.
3) Database hacks. Although I'm fairly confident there are no SQL holes, it's a remote possibility. If this happens though, there are bigger problems than torrents being uploaded. Even if we require a password, there is nothing to stop someone with database access from running a rainbow table attack.
The next version will tie uploaded torrents to specific users for the purposes of being able to edit. Code can either be modded in to do what you want, or I may include some of it by default. Either way, I'll throw in an anonymous box for uploads so they can keep their names from the top lists.
On the subject of ratios, it's something I'm debating. At revolt we don't use ratios for anything. It's a small place and we figure a user is worth more than a number. If I leave out ratios, it might encourage more sites to run a similar system and mark the code as being for smaller groups (mainly friends). It also removes the problem of ratio cheaters completely.
Lots of smaller, friendlier sites with lower operating costs is how I'd like to see the torrent scene go to make things harder on the mafiaa, but people will run the sites they want to run.
If I include ratios, it makes the site more durable for a range of uses, but still encourages ratio logging and leaves the problem of cheats.
If ratios are included, I cannot include any of the code I have written for detecting various cheat clients by name, as this would give the makers clues to improve their cheats. The best that could be included in a public release is a speed reporter, and this only catches the most stupid cheats rather than the worst ones.
I'm toying with various ideas to allow seedtime as a point system, but without some ratio inclusion that discriminates against seedboxes which seed to high ratios for a very short time.
Whatever happens, I'll be redoing the sysdev site to include some forums, so we should be able to at least have a mod section.