All awareness messages are echoed

Here we’re sending awareness updates to changedClients

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?