Type Alias SessionMembershipData

The RTC application defines the type of the RTC session.

The id of this session. A session can never span over multiple rooms so this id is to distinguish between multiple session in one room. A room wide session that is not associated with a user, and therefore immune to creation race conflicts, uses the call_id: "".

Optional field that contains the creation of the session. If it is undefined the creation is the origin_server_ts of the event itself. For updates to the event this property tracks the origin_server_ts of the initial join event.

• If it is undefined it can be interpreted as a "Join".
• If it is defined it can be interpreted as an "Update"

The Matrix device ID of this session. A single user can have multiple sessions on different devices.

Optionally we allow to define a delta to the created_ts that defines when the event is expired/invalid. This should be set to multiple hours. The only reason it exist is to deal with failed delayed events. (for example caused by a homeserver crashes)

A list of possible foci this uses knows about. One of them might be used based on the focus_active selection system.

The focus selection system this user/membership is using.

If the application = "m.call" this defines if it is a room or user owned call. There can always be one room scroped call but multiple user owned calls (breakout sessions)