generating meeting and participant-level IDs for communication with rhythm server

[dcalacci]

One issue with the current implementation is that we are using hardcoded meeting IDs (or meeting IDs that are room names) and participant names. We should try to do something like the following:

1. each new room (even if it is a similar room name to a previous room) is assigned a unique identifier, and rhythm-rtc stores this identifier. if you make a new room with the same name as a previous one, it's overwritten.
2. each user in a new room is assigned a unique identifier as well. If I join meeting A, my identifier will be different than my identifier for meeting B.
3. data sent to the rhythm server uses these identifiers for participant IDs and meeting IDs.

Long-term, it would be nice to track participants and meetings over time, but we should first implement sending "correct" data from rhythm-rtc to the rhythm-server, and this is the most straightforward way to do it.

This will mostly be code written in Express on the server-side of rhythm-RTC

[dcalacci]

maybe using the easyRTC participant IDs?

easiest way to do this would be:

• keep a list of all the active rooms in the EasyRTC server
• each time a new room opens, generate a random UUID
• when a participant joins a room, they can make an API call to get the random UUID of their room

that UUID is what is sent to the rhythm-server and is the "true" identifier of a room/meeting, rather than the text name.