[11:39] <tsimpson> rww: it's not nick based, it's identify-msg bases (which lets you know if the current nick is identified with services)
[11:40] <tsimpson> though the supybot user database is nick/host based, so it's a manual process to add new nicks
[11:40] <tsimpson> patch if you have a better idea :)
[11:46] <IdleOne> why does the bot use nick/host for the user database if it already checks if the user is identified with services to the correct account?
[11:53] <IdleOne> if that is a silly question please tell me :/
[12:04] <tsimpson> its users database is based on nick and host, but we also verify that the nick is identified
[12:04] <tsimpson> instead of using passwords with the bot
[12:05] <IdleOne> right, I get that. Why not make the user database account based. so that when it checks if the user is identified to the correct account it does need to also check what nick it is using
[12:05] <IdleOne> does not need*
[12:17] <tsimpson> IdleOne: because, it's the supybot database and I don't control that
[12:17] <tsimpson> and because someone will have to write the account checking part
[12:18] <IdleOne> I nominate rww
[12:18] <tsimpson> right now it checks that the nick you're using is identified to the account which owns it, and then checks if the nick/host is in the users database
[13:26] <DJones> popey: Thanks for the quick reaction banning energy
[13:27] <popey> np
[13:27] <popey> i dont do much op duties, sorry
[14:27] <DJones> no worries