New socket stops previous sockets from receiving new data?

[Jose Luis Garcia del Castillo]

Hi all,

Thanks you for an amazing project @brunosimon !

I have ran into this issue where, when running an instance of a host keppler and having multiple spectators connect to it, whichever spectator connects last in time becomes the only one receiving new changes from the presenter, and all previous ones stop receiving them. Weirdly, older sockets do get the orange changes notification next to the file, but not the actual changes.

The problem gets solved if keppler is restarted, and all sockets reset their connections simultaneously. But then, as soon as a new socket connects, problem happens again.

Has anyone experienced this issue? Might this be a node version / dependencies version problem? Can anyone share a node version where keppler works fine?

Thanks!