All awareness messages are echoed

mif · November 1, 2022, 5:34pm

Here we’re sending awareness updates to changedClients

yjs/y-websocket/blob/master/bin/utils.js#L120-L124


      
          encoding.writeVarUint8Array(encoder, awarenessProtocol.encodeAwarenessUpdate(this.awareness, changedClients))
          const buff = encoding.toUint8Array(encoder)
          this.conns.forEach((_, c) => {
            send(this, c, buff)
          })

And changedClients almost always contains the node that originates the change. As a result, you can see that every awareness message you send to the server echoed back to the browser which is actually noop (because the local clock is already >=).
Why we can’t just filter out the “original” client connection from the receivers?