Short answer: when designing reliable updates for a collaborative whiteboard, make the realtime channel lifecycle treat typing indicators and read receipts as expiring evidence, not durable state; bind every signal to a participant session and channel epoch, then reject late evidence at the receiver.
That decision keeps presence accuracy honest without asking an ephemeral channel to provide ledger semantics. A canvas operation may deserve durable sequencing, replay, reconciliation, and an audit trail. “Mina is typing” does not. A read receipt sits between those categories: it can affect user expectations, but it reports an observation rather than changing the board. Mixing all three into one undifferentiated stream makes reconnect behavior look easy while quietly allowing a stale packet to resurrect a departed participant.
This is an architecture decision record for a collaborative whiteboard used in a fintech workflow, where a reviewer may annotate a settlement diagram while another participant reads it.…