The Netflux WebSocket endpoint delays replies for no good reason

The current implementation collects the replies and sends them when receiving the next message. I don't understand the reason behind this. One effect of this is that when someone leaves the session, the rest are notified with a delay. This makes it hard to know reliably how many users are currently in the realtime session, e.g. if we want to do some special action when a user remains alone in the session.