If you’re using Turbo broadcasts to make a page collaborative, you might have noticed that the default refresh approach adds latency: an extra round trip, a debounce delay, and a flood of simultaneous requests when many users are connected. Broadcasting a replace action with the content directly fixes most of that, but it opens up a race condition where updates can arrive out of order. Here’s how to get fast, immediate updates without sacrificing correctness: When broadcasting a Turbo refresh is not enough: faster UX with versioned immediate updates