Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-01-10 18:03:41 +01:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

we don't actually know which session got stuck, so rate-limit by device

Browse source
This commit is contained in:
Hubert Chathi 2018-11-14 10:19:11 -05:00
parent d0bfdc13af
commit 495df02da6
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
proposals/1719-olm_unwedging.md
View file

@ -13,10 +13,11 @@ session, to the other party in order to inform them of the new session. To
send a dummy message, clients may send an event with type `m.dummy`, and with
empty contents.
If the corrupted session has already been replaced, the receiving device should
do nothing, under the assumption that the message from the corrupted session
was sent before the sender was informed of the replacement session, in order to
avoid creating too many extra sessions.
In order to avoid creating too many extra sessions, a client should rate-limit
the number of new sessions it creates per device that it receives a message
from; the client should not create a new session with another device if it has
already created one for that given device in the past 1 hour. (TODO: is 1 hour
the right amount of time?)
The spec currently says, "If a client has multiple sessions established with
another device, it should use the session from which it last received a