Skip to content

Commit

Permalink
Explain rationale for setting server_name when joining upgraded room
Browse files Browse the repository at this point in the history
  • Loading branch information
richvdh committed Oct 22, 2018
1 parent 14b98a0 commit 21a4594
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion proposals/1501-room-version-upgrades.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 21a4594

Please sign in to comment.