Coalesce rapid mouse movements in games

Games generate a LOT of mouse movement events, which are each propagated to all clients. We should be able to reduce this. For example, suppose each client tracked when it already had a mouse movement sent within the last 50 milliseconds; and if so, coalesced all consecutive mouse events and postponed broadcasting them until 50 milliseconds had passed.

We could also look into a trick similar to the redraw-avoidance. It's less straight-forward, though, because even if the MouseMovement doesn't modify local states, it still needs to be sent because it might matter in whatever (as yet unknown) state the game will be in, in the merged canonical event stream. So that's not great. BUT, if we could introspect that MouseMovement events are always the identity function for a given game, then we could save a lot of traffic.

It's not immediately clear to me how to discover this. @nomeata knows a fair bit about this: any ideas?

El issue no identifica archivos, pruebas ni puntos de entrada. Comienza localizando el manejo de eventos de movimiento del ratón y la ruta de broadcast al cliente; después, compárala con el mecanismo para evitar redibujados mencionado aquí. Se considera terminado cuando se haya establecido un enfoque seguro para combinar eventos o detectar identidades y se haya validado que el comportamiento de los eventos del juego sigue siendo correcto.