Notes
Stuff we've spoken about
-
command_and_wait, util provided functionality that takes a command for a server, blocks until response, and returns the response for modules to use for things like checking if a PM wasn't delivered due to user offline or channel banlists, etc.
- See here: SendAndWait
-
The more module convenience the better,
things like event.isadmin and the like might be really handy, or that can be left for module writer I suppose. I think it's nice thoughWe will do this through utilities. -
In Servers settings, change structure to dict where servername is the key and corresponding serveropts are the value to ensure unique (and existent) server names at configuration level
-
Finalize how we're doing logging
-
Cache aliases (ultra low priority)
-
Webhelpers dependency. How many dependencies are we okay with?
-
Replace webhelpers with your custom DISTANCE_IN_TIME thing from your old bbm.. I was just using it as placeholder. -
lol scratch that, I guess write a new one...
-
Support multiple aliases for commands (Mapping.command should be Mapping.commands, a tuple)
-
I guess this should allow for non-tuple, too, because ("COMMAND",) is kinda lame.
-
Allow config to supply alternate nicks to use before trying nicksuffix on alterCollidedNick
- Reconsider auto alias adding sometime... Maybe make this optional
- lol for butt module, make a bestofbutts
botinst wrapper for context aware things like bot.say (auto messages to event.channel)? Maybe this falls under too much preprocessing too
Maybe wrap the wrappa Done.
- Tell preprocessing
- Goes hand in hand with alias preprocessing
- lol forget about this until 100 years
Getters/setters (Server object -> back to getter from Settings?)lol no?- Module dependencies: consider more automated ways of handling it
- db.py util shouldn't do anything when run on its own. Method to explicitly init would be a good idea.