You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm, that's a good question. We do keep track of lastMessageTime for the purposes of throttling, so this should not be hard to extend to multiple elections. One caveat, though, is that we might be ending up with significant delays in responses for some of the rooms should there be multiple elections happening at once.
That said, I think a single-account bot that can work with multiple elections at the same time is possible if we switch from dropping messages that come in during the throttle period (current behaviour) in favour of a message queue processed in order regardless of the initiator room with maybe some load balancing to avoid ending up with a LILO queue.
Should this bot be able to run in multiple election rooms, will this cause an issue if it's all on the same Stack Exchange chat account?
Should we need to create mutiple accounts for the bot to utilise in chat?
If possible we should be able to run everything via a single account, which means keeping track of when the last message was sent and then back-off.
The text was updated successfully, but these errors were encountered: