Turns out the problem was not a race condition, but the server part of cursorBroadcast being activated even if the client part wasn't (e.g. on a text document)
Nope, it was both, I guess: Race condition (server sending messages over the wire before the client has registered the streams) and cursorBroadcast sending messages for the wrong document type.
Turns out the problem was not a race condition, but the server part of cursorBroadcast being activated even if the client part wasn't (e.g. on a
text
document)