Consider a proposed page for a gaming watch party: playback acknowledgments have stopped advancing for part of the room, while chat still shows typing indicators and read receipts. The on-call sees active connections and a healthy transport dashboard. Neither answers the useful question: which viewers applied the latest playback command? This is a diagnostic scenario, not a report of a production incident.
Short answer: use host-authoritative playback when one designated controller should decide the room's timeline; consider peer consensus when the room must agree on control changes without that single decision point. In either design, specify delivery and recovery separately. Agreement about a command does not demonstrate that every viewer received it, and a typing indicator cannot serve as a playback acknowledgment.
For a server application, including one implemented in Node.js, that distinction belongs in the event contract before the transport choice.…