When the bot receives op privs, it will check who is online in the channel that doesn't have op privs which it would normally provide and does so. THus, one needs only to op the bot and everyone else will automatically get ops as configured. When two bots are in a channel (providing each other backup), it attempts to smartly remove the nick the other bot op'd so as not to repeat it.
Added a channel state so that it doesn't tick off the server attempting to give op privileges, when it doesn't yet have them. However, once it has been give op privileges, then it will start doing so. Similarly, if the bot has been deop'd (-o), it will stop attempting to give out privileges.
Add 'password <password>' to the server section of the configuration No attempt to encrypt the password as it is passed somewhat plain text across the pipe anyway This does a very basic job looking for the server to say that the nick is registered and that you need to identify yourself. When it receives that message, it sends the expected /msg NickServ identify <password> message. This is to support FreeNode.