Queue messages until "condition" is met

[optimumtact]

Consider that you often cannot send irc join messages until you have gone through at least the basic connection to the irc serv.

the bot currently has some hardcoded logic to queue any and all join events until it sees the end of the message of the day, or the no motd response and then it sends all queued channel join events.

This would be quite useful if this abstraction could be extended to support generic queueing for outgoing bot events.

The current plan looks a little something like this

a dict of {stateflag -> list} where the list is a list of held outbound events

when the stateflag is set to true, the queued list of events is sent and all future events pertaining to this stateflag are sent immediately.

If the stateflag is toggled back to false then they start queueing again.

I have not yet encountered any other items that would potentially need this yet, but I can think of a few uses where a module might find it useful, hence the generalisation

[optimumtact]

Now that I think about it, it's plausible that spam control could potentially be handled through this, as a default filter applied to every single item, so if the spam limit flag goes on, events would be queued