You could use something like setInterval to get the room list on a loop. There is no way to watch for it to be emitted though.

First off, you shouldn't do this. It's meant to be a state, which holds data. Not a lot more than that.

That said, if you really want to, you can add a @nonenumerable or @nosync attribute to the room variable. to make it not serialized.

This is likely standard and comes with Discourse.

Specifically:

We use this information strictly to personalise your experience in this community, as well as to associate the posts you make to your user account. During the registration step you were asked to provide a username and email address, you can also optionally provide additional information to complete your user profile on this website.

We retain this information for the life of your user account, and you are able to withdraw consent at any time by deleting your account. At any time you may request a copy of your contribution to this website, via your Rights & Consent page.

This is just telling you that your username will be associated with your posts.

Occasionally, we may send emails to your registered email address in order to provide updates and/or to notify you of new activity that is pertinent to you. You can customise the frequency of the community digest (including disabling it outright), as well as select which types of notifications to receive via email, via your user settings page. Unless explicitly changed in your user settings, this community delivers email digests every .

This is telling you that you will get email notifications from the forum.

There is nothing being harvested here. You don't see this when you sign up for a phpbb forum, but they do it anyway - Discourse is just more explicit.

Right now you are not able to. You can, however, client.send() specific parts to specific clients so the knowledge remains private.

You can use a database to do this, or redis. But you can't just share variables between rooms as they should be treated as if they have no way to communicate with each other.

A sample project or code snippet would go a long way to helping figure out what's going on.

You will not be able to easily restart game loops and etc after the server restarts. The best you can do is persist the relevant state to the DB and load it when the room is created again.

One thing you can do is set room.autoDispose to false, which will let it keep going after all users have disconnected.

I wasn't having a ton of luck compiling uws. For me, I downgraded from node 9 to node 8.9.3 and uws started working for me again.