A realtime channel makes a collaborative cursor notification immediate; a message queue makes its recovery durable. The awkward constraint is that replaying every old coordinate after a reconnect is usually wrong. The durable thing is not an endless trail of mouse movements. It is the latest useful state, plus enough ordering information to reject stale updates. Short answer: use a realtime channel to accelerate live cursor updates and a durable queue or state log to recover after disconnec...