Splitting participants and sessions

[nickvergessen]

😕 Why?

• Allow groups as participants Synchronize group members in group chat continuously #1329
• Allow email addresses as participants show email invitees #1902
• Persistent guests on page reload Reuse session id for guests to prevent multiple guests appearing on page refresh #1793
• Allow to block guests (as reload recognizes them) Guests can immediately re-join a public meeting after being removed by the moderator #1423

Also there is this crazy idea, that some users want to be in the same conversation multiple times e.g. to sync data from phone to laptop, laptop to desktop, etc.

↔️ Splitting the data

Persistent/shared participant data

• Participant identifier (to map the session data)
• Room id/token
• Participant type
• Identifier: User id, group id, email-address, random-id for guests
• User favorited the room
• Last mention datetime
• Selected notification level
• Last joined call (for the call summary)

Unique session data - Removed when leaving the call/chat

• Participant identifier
• SessionId - random string for WebRTC
• In call flag
• Last ping (is currently only used to timeout users from the call, therefor it does not require to be kept in the participant data)