From: Paul L. A. <pl...@so...> - 2004-08-04 19:47:23
|
Tim Riker writes: > Some thoughts on the way forward (in no particular order): > 2) we need a new framework to better support tons of modules. We also need a far more flexible configuration format. One that is capable of specifying (with relative ease, probably using inheritance and over-riding) that on server X, channel Y, the bot need not be addressed for most commands but must be addressed for command Z. It would probably be good if extension modules, if enabled by the configuration, can pass back to the main program what to look for rather than having stuff like /Zippy/ coded into the main program. Resolving conflicts would require some thought (probably first registered, first tried). At least that way people could submit extension modules that don't require a patch to the main routine. In fact, it would be even better if that was done in the configuration file. So where you enable Zippy you also specify that it should look for /Zippy/i or /Be Zippy/ or whatever. You'd have to analyse everything the bot and existing extensions currently look for to generalize it as much as possible without overcomplicating it. If no search criteria are specified then hardwired defaults in the module are used instead. That way you don't have to do anything unless two modules conflict or you don't like what the bot is looking for, and if the module is searching for something impossible to specify in whatever syntax we use that's OK too. > 3) I'd like to see sql backend instead of dbm. I'd prefer sqlite and > mysql, and any more that others want to add. sqlite allows for simple file > based access like dbm, but with the richer search capabilities. Not everyone is in a position to get MySQL or sqlite set up for them. It's rare, but it happens. But most *nix boxes will allow even unprivileged users to call ndbm/gbdm/db. It would be nice if it were possible to choose at configure time which to use. That would mean abstracting the existing db calls. It would also permit alternative SQL databases to be added as required. > 4) I'd like to get as many of the infobot clones, and forks to join back > into the main tree. More eyes, more hands = more progress. But the reason there were so many forks is that nobody could agree on how to proceed. I suspect you may end up with more arguments than progress... > 5) I'd like to add email, web, and local admin interfaces at least. email > for things like CIA does now: Local admin interface can be as simple as listening on a port on the loopback address. Use your favourite telnet program and just type "forget Bush". For the local interface the bot would react exactly as if it had been /msgd - no need to address it no matter what the config says. -- Paul Allen Softflare Support |