MegBot
MegBot copied to clipboard
tsyesika
IRC bot with plugins to make it easily extendable
Currently we load standard plugins and libraries via a path set in the config. This doesn't work if the user has installed MegBot via `python setup.py install` and then runs...
[This core plugin](https://github.com/xray7224/MegBot/blob/master/megbot/core/delegator.py) has at least 3 ways it can call event handlers from plugins: * `connection.hooker.hook(connection, info)` which is labelled as "old system" * `connection.handler.event(event)` which is labelled as...
We need some way of making a plugin "greedy" or maybe just ignore `!command` messages.
Currently we have this horrible situation where each connection has its own thread, and each call to a plugin is spun off into a separate thread too. This isn't too...
At the moment we connect, sit there until we time out and then restart the connection. We need to deal with two situations here: - our old connection hasn't timed...
We've got zero flood protection in our CTCP module at the moment. This is a well known attack, so shouldn't be too hard to mitigate.
It'd be cool if we could have support for multiple languages in megbot. We have two options, we can do it per channel/network/plugin or whatever and/or we could do it...
Currently IRC objects is this big fat library fulll of classes which really don't represent what it originally was meant to be. I think we need to keep IRC objects...
To fix all the encoding bugs we have now and in the future I think we need to convert data when we get it in to unicode on all inputs...