Fires whenever a room's account_data is updated.
Fires when the status of a transmitted event is updated.
When an event is first transmitted, a temporary copy of the event is inserted into the timeline, with a temporary event id, and a status of 'SENDING'.
Once the echo comes back from the server, the content of the event (MatrixEvent.event) is replaced by the complete event from the homeserver, thus updating its event id, as well as server-generated fields such as the timestamp. Its status is set to null.
Once the /send request completes, if the remote echo has not already arrived, the event is updated with a new event id and the status is set to 'SENT'. The server-generated fields are of course not updated yet.
If the /send fails, In this case, the event's status is set to 'NOT_SENT'. If it is later resent, the process starts again, setting the status to 'SENDING'. Alternatively, the message may be cancelled, which removes the event from the room, and sets the status to 'CANCELLED'.
This event is raised to reflect each of the transitions above.
Fires when the logged in user's membership in the room is updated.
Fires whenever the name of a room is updated.
Fires whenever a receipt is received for a room
Fires when an event we had previously received is redacted.
(Note this is not fired when the redaction happens before we receive the event).
Fires when an event that was previously redacted isn't anymore. This happens when the redaction couldn't be sent and was subsequently cancelled by the user. Redactions have a local echo which is undone in this scenario.
Fires when a new room summary is returned by /sync
.
See https://spec.matrix.org/v1.8/client-server-api/#_matrixclientv3sync_roomsummary for full details
Fires whenever a room's tags are updated.
Fires when a new poll instance is added to the room state