A multiplayer cursor looks like a drawing problem. It is a timing problem.
Everyone else in the file is a stream of sparse positions that arrive late, out of order, and sometimes not at all. The screen redraws about sixty times a second. The positions do not. Almost every frame you paint is therefore something you made up, and the whole craft of the feature is in how you make it up.
π Live, with every table computed in your browser by the same engine: https://dev48.in/design/day83-presence-cursors.html
π΄ The wire is simulated
There is no socket here. A seeded transport models a 90 ms latency floor, 100 ms of uniform jitter and a 12% drop rate , and the clock is an explicit fixed 16 ms step, so the replay is a pure function of (seed, settings) and reproduces byte for byte. The digest over every rendered position of every frame is 31da09e9 on every machine.
What that costs: the point estimates below are properties of this draw.β¦