Comment 13 for bug 190964

While I suppose this one is rather hard to fix, too, kindly check whether the following proposal is good enough to be implemented to finally get rid of this issue.
If I am not mistaken, when the client is truly connected, then there must be users available on the hub, at least one, which is the client itself.
Based on this I was thinking of whether it would be possible to do a user count several seconds after the client receives the connected state, and if the amount of the users cannot be determined (or equals zero), then an automated reconnect should be issued by the client itself.