I know that, I was asking for ideas on alternate profile fields. I'm adding registration IP. I'm building the backend one class at a time, and logins will probably be last.
By the way, sessions aren't at all necessary for registration unless you want to log in automatically after registration. Generally not worth it if you require email verification, as I'm planning.

I recomend you taking off secondary email, most of people just got one email

take off location and question and answer.
Unless location is 100% vital.
For account recovery you can recover it via email, no need for a secret question (which is invariably more insecure than a password. Secret questions ENCOURAGE people to have bad answers)

Location, question, answer and secondary email are all optional fields. I probably should have said something about that.
Anyway, I'm reworking my original plan; I'm going to have all database management done through Ruby scripts. I've successfully created a way of communicating between the two languages, so everything should be sweet.

Here's a more basic one.

http://www.box.net/shared/p3n1ilgkf1

And Die class.

http://www.box.net/shared/zmp8ozr9jd

First, (Toribash Lua)

[12:53:43] <~ryan> i think an on_specs_update hook would be nice
[12:56:45] <~ryan> so, add_hook('specs_update', '', function(action, nick[, reason]) echo(nick .. " has " .. action .. " the server."); if reason then 
                   echo("(" .. reason .. ")") end) -- specs_change works too
[12:57:51] <~ryan> action is either 'left' or 'joined', nick is obvious and the reason could be 'ping timeout' or 'no response' or whatever
[12:58:38] <~ryan> those [] weren't really necessary but yeah

Thoughts?

Second, I'll probably start working on the site again later, I've suddenly felt the urge to do stuff in Perl. Just cannot get enough RegEx.
I'll probably make another IRC bot sometime in the next couple of days. I think I'll take a different approach this time: building a database of possible commands and their appropriate responses. Commands should be recognised by RegEx (duh) and the database's response will be eval()'d and the results printed to the channel. I'm not a fan of eval() in any language, but there's an extremely low probability of unintentionally creating malicious code in my database.

That java thingy looked interesting, but it was a bitch to read because of the indentation. Couldn't tell what was in which block. :<

It's a W.I.P.

Sorry to inconvenience you, lol.

So I've decided I'm going to take a different approach to furthering my own knowledge of C++ (I pretty much only have a grasp on the basics right now). I'm going to create a text-based game in a language I already know (most likely PHP, with some AJAX), then rewrite it in C++. This way, I'll be learning, doing something productive, and have a clear objective all at the same time.

I've created my own esoteric language, kind of brainfuck-esque.
Once this event is over, I'll post about it in detail.