From 21a45948caebd1bf15d6d39d8932accbd65765ff Mon Sep 17 00:00:00 2001 From: Richard van der Hoff Date: Mon, 22 Oct 2018 17:03:48 +0100 Subject: [PATCH] Explain rationale for setting server_name when joining upgraded room --- proposals/1501-room-version-upgrades.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/proposals/1501-room-version-upgrades.md b/proposals/1501-room-version-upgrades.md index fc0bf71e..3a726250 100644 --- a/proposals/1501-room-version-upgrades.md +++ b/proposals/1501-room-version-upgrades.md @@ -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.