You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background: If an Olm session "wedges", we will attempt to work around it by starting a new session. Later, when either side wants to send another olm message, it will use the most recent Olm session -- ie, the new session.
However: when sessions are imported from legacy crypto, their "creation_time" and "last_used_time" are both set 50000 years in the future. (They are set in milliseconds rather than seconds. See also matrix-org/matrix-rust-sdk#2974, matrix-org/matrix-rust-sdk#2973.) That means that the imported session will always be used in preference to any newer sessions.
The text was updated successfully, but these errors were encountered:
Background: If an Olm session "wedges", we will attempt to work around it by starting a new session. Later, when either side wants to send another olm message, it will use the most recent Olm session -- ie, the new session.
However: when sessions are imported from legacy crypto, their "creation_time" and "last_used_time" are both set 50000 years in the future. (They are set in milliseconds rather than seconds. See also matrix-org/matrix-rust-sdk#2974, matrix-org/matrix-rust-sdk#2973.) That means that the imported session will always be used in preference to any newer sessions.
The text was updated successfully, but these errors were encountered: