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

Explain rationale for setting server_name when joining upgraded room

Browse source
This commit is contained in:
Richard van der Hoff 2018-10-22 17:03:48 +01:00
parent 14b98a0220
commit 21a45948ca
1 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
proposals/1501-room-version-upgrades.md
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.
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
new room, it should hide the old one from the RoomList.