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
Admin actions sometimes conflict with other player actions. For example an admin clicks "Next Speaker" immediately after someone has clicked "I'm finished speaking" which results in a topic being skipped.
We could solve this with some kind of timer that rejects multiple actions that happen too close together. But I think it would be easier to add an undo button for admins.
The text was updated successfully, but these errors were encountered:
I think switching to a time-series database would make this undo-action much easier, compared the the current document nosql style.
The current implementation doesn't even track changes atomically.
It could thereby only revert the complete state as it was for the admin. Intermediate changes would be lost.
To send and process only atomic changes would also help greatly.
I'd love to explore this a bit more and play with it :)
Admin actions sometimes conflict with other player actions. For example an admin clicks "Next Speaker" immediately after someone has clicked "I'm finished speaking" which results in a topic being skipped.
We could solve this with some kind of timer that rejects multiple actions that happen too close together. But I think it would be easier to add an undo button for admins.
The text was updated successfully, but these errors were encountered: