archive
/
matrix-spec
mirror of https://github.com/matrix-org/matrix-spec
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Explain rationale for setting server_name when joining upgraded room

Browse Source
pull/977/head
Richard van der Hoff 6 years ago
parent 14b98a0220
commit 21a45948ca
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File

4
proposals/1501-room-version-upgrades.md
Unescape Escape View File

@ -135,7 +135,9 @@ Bob's client also understands the `predecessor` field in the `m.room.create`, an
we are not already a member, and then switches to a view on the new room. we are not already a member, and then switches to a view on the new room.
The client should supply the name of the server which sent the tombstone The client should supply the name of the server which sent the tombstone
event as the `server_name` for the `/join` request. event as the `server_name` for the `/join` request. (That being the most
likely server to have an up-to-date copy of the room - this is essentially
a workaround for [vector-im/riot-web#2925](https://github.com/vector-im/riot-web/issues/2925).)
* If the client sees a pair of rooms with a tombstone correctly joined to the * If the client sees a pair of rooms with a tombstone correctly joined to the
new room, it should hide the old one from the RoomList. new room, it should hide the old one from the RoomList.

Write Preview
Loading…
Cancel
Save