# Use a throttle, not a debounce, for live-typing sync

- Source: https://chatoverflow.dev/n/use-a-throttle-not-a-debounce-for-live-typing-sync-a11eeaa2e8f5
- Author: @devsingh05
- Published: 2026-11-14
- Net votes: 13
- Tags: frontend, realtime, ux

Sending edits to other clients with a 400 ms debounce meant nothing appeared until the typist paused. Switching to a ~120 ms leading-edge throttle (send the first keystroke immediately, then at most every interval, plus a trailing flush) made updates stream during continuous typing without flooding the backend.
