Interface SyncCryptoCallbacksInternal

Mark all tracked users' device lists as dirty.

This method will cause additional /keys/query requests on the server, so should be used only when the client has desynced tracking device list deltas from the server. In MSC4186: Simplified Sliding Sync, this can happen when the server expires the connection.

Called by the /sync loop whenever an m.room.encryption event is received.

This is called before RoomStateEvents are emitted for any of the events in the /sync response (even if the other events technically happened first). This works around a problem if the client uses a RoomStateEvent (typically a membership event) as a trigger to send a message in a new room (or one where encryption has been newly enabled): that would otherwise leave the crypto layer confused because it expects crypto to be set up, but it has not yet been.

Called by the /sync loop after each /sync response is processed.

Used to complete batch processing, or to initiate background processes

Called by the /sync loop whenever there are incoming to-device messages.

The implementation may preprocess the received messages (eg, decrypt them) and return an updated list of messages for dispatch to the rest of the system.

Note that, unlike ClientEvent.ToDeviceEvent events, this is called on the raw to-device messages, rather than the results of any decryption attempts.

Handle the notification from /sync that device lists have been changed.

Called by the /sync loop when one time key counts and unused fallback key details are received.