wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

A couple of clarifications

Browse source 
- the body of the tombstone is defined by the server.
- the client can follow tombstones until it finds a live room
This commit is contained in:
Richard van der Hoff 2018-10-17 20:28:53 +01:00
parent b5e5a690f5
commit 14b98a0220
1 changed files with 8 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

7
proposals/1501-room-version-upgrades.md
View file

@ -77,6 +77,9 @@ When this is called, the server:
} }
``` ```
The `body` of the tombstone event is defined by the server (for now, at
least).
* Assuming Alice has the powers to do so, sets the power levels in the old * Assuming Alice has the powers to do so, sets the power levels in the old
room to stop people speaking. In practice, this means setting room to stop people speaking. In practice, this means setting
`events_default` and `invite` to the greater of `50` and `users_default+1`. `events_default` and `invite` to the greater of `50` and `users_default+1`.
@ -96,6 +99,10 @@ Bob's client understands the `m.room.tombstone` event, and:
for a while and eventually fails. Synapse 0.33.3 should at least give a for a while and eventually fails. Synapse 0.33.3 should at least give a
sensible error code.] sensible error code.]
If it turns out that the replacement room also has a tombstone event, the
client may automatically keep following the chain until it reaches a room
that isn't dead.
* Optional extension: if the user is in both rooms, then the "N unread * Optional extension: if the user is in both rooms, then the "N unread
messages" banner when scrolled up in the old room could be made to track messages" banner when scrolled up in the old room could be made to track
messages in the new room (so in practice the user would only ever see the messages in the new room (so in practice the user would only ever see the