I’ve managed to do this, in a way. I pass the current clientID from the client to the server when connecting to websockets. I use this clientID to set an awareness state on the server and I also start the server-side clock at 1, so that it gets accepted by clients. And then that sort of works
Of course it’s a hack, but I’m not sure what the correct approach would be. Maybe something like an auth exchange, where the clients ask the server “Who am I?” and then set the local state accordingly. I wouldn’t like local user information to “win” though, so I need to find a way to verify it with every awareness update.
That’s it for now, I’ll update this conversation when I have a solution.