I did something similar with Slack as the transport layer. Threads work well as conversation context — the bot fetches previous thread messages and rebuilds the full history before each request. The part that got tricky was queueing.
The CLI can only handle one request at a time, so I ended up building a request queue that announces your position ("you're #3 in line").
IRC being single threaded probably has the same constraint. How do you handle concurrent users?
The CLI can only handle one request at a time, so I ended up building a request queue that announces your position ("you're #3 in line").
IRC being single threaded probably has the same constraint. How do you handle concurrent users?