And this is the exact issue people hit early on with prosemirror-collab performance;
Interesting. I’ve never heard of this from any of the various people I’m working with who have been using prosemirror-collab for years. Is this really something that came up for you, outside of synthetic benchmarks? Because it seems to require A) constant typing without pause, and B) high latencies.
This is not to say this isn’t an issue—I can see how it could theoretically happen—but I’m wondering if it is a common enough issue to complicate the protocol for.