17:58 <cmartin123> Does all the behaviour of the bot have to be defined before bot.start is called?

18:03 <dominikh> no.

18:04 <waxjar> you can register new plugins and unregister plugins while running, i'm not sure about individual commands.

18:04 <dominikh> every matcher can be created/manipulated/removed

18:04 <dominikh> s/matcher/handler

18:04 <dominikh> s/$/at runtime

18:07 <cmartin123> I want to send a message to a irc user in response to an event from an event-driven websocket server, but I want the bot to be connected throughout the time the websocket is open. As soon as I call bot.start, the execution flow is blocked, right.

18:09 <dominikh> you can call start in a thread of its own.

18:13 <cmartin123> Then I can use call bot.on, and do User('user', bot).msg, etc, while the bot is running in it's own thread?

18:16 <dominikh> I don't see why you'd need bot.on though. Do you want to create new things to react on, or just send someone a message

18:18 <dominikh> but yes, you could use bot.on

18:18 <cmartin123> Just send somebody a message, but I was just wondering

18:19 <cmartin123> That helps a lot, thanks

18:19 <dominikh> :)

19:03 <ColdBlooder> Sorry if its off topic but is there a way to scan if incoming tor user on the server side? (A bot could do this but its propably more efficent to handle that on the irc server)

19:03 <ColdBlooder> and hi :)

19:08 <dominikh> rather off topic :) there are lists of TOR exit nodes. freenode, e.g. has some rules regarding tor, so does oftc

19:09 <dominikh> so yes, quite possibly

19:10 <dominikh> gotta leave now though.

19:10 <ColdBlooder> Wish i could get bopm to work. GOnna try using a bot for it now. (Still gonna be a while before im "good enough" in ruby to tackle it though)

19:10 <ColdBlooder> ok, cya!