Latency issues causing out-of-sync OT issues

[Luna-Klatzer]

When writing a file with multiple issues using a remote server where the latency can be >100ms, the various clients can receive so-called state inconsistency errors where OT transformations are incorrectly applied and then cause inconsistencies.

To fix this, we simply need to enforce a general rule of absolute eventual truth by making the client and server reshuffle transformations based on the date, meaning that each version of the file will eventually receive all the transformations and can build together the file. While this may mean more processing as sometimes a few dozen transformations will need to be reverted, pushed on top of new intermediate OT transformations and then applied again, this would ensure that all clients and the server share an absolute truth based on the UNIX timestamp which is using milliseconds i.e. can compare OT transformations very accurately.

This is also something which is shown off in this demo: https://operational-transformation.github.io/