Matt Molyneaux
Matt Molyneaux
`p` should catch network errors and shorten them to something more user-friendly Example proxy error: ``` Traceback (most recent call last): File "/home/moggers/workspace/p/env/bin/p", line 5, in pkg_resources.run_script('p==0.1', 'p') File "/home/moggers/workspace/p/env/lib/python2.7/site-packages/pkg_resources.py",...
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...
``` 09:06 &moggers87 | !reply
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.
We need a logger facility and some way of catching tracebacks.