Open Asparagirl opened 10 years ago
I think the best way to handle #56 is to start splitting out the job-queuing logic from bot/brain.rb
into command-line utilities that the bot invokes (yadda shellshock yadda yadda). This'll let a separate Twitter daemon use the same code. (Bonus: it'll also make said job-queuing code much more amenable to automated tests.)
The same pattern can be applied to the rest of the bot's job-management code, which should help in the creation of a tweet-driven UI.
What if we only want to tweet to the bot and not use IRC at all? Or interact solely through e-mail, web hook, REST API, speech recognition, or whatever else comes along?