From bd09c90b4745b2fb78a17e9ae29a1b5ab80a21aa Mon Sep 17 00:00:00 2001 From: Tulir Asokan Date: Sat, 4 Apr 2026 15:55:50 +0300 Subject: [PATCH] Define where to find via for following tombstone/predecessor Signed-off-by: Tulir Asokan --- changelogs/client_server/newsfragments/2352.clarification | 1 + content/client-server-api/modules/room_upgrades.md | 4 ++++ 2 files changed, 5 insertions(+) create mode 100644 changelogs/client_server/newsfragments/2352.clarification diff --git a/changelogs/client_server/newsfragments/2352.clarification b/changelogs/client_server/newsfragments/2352.clarification new file mode 100644 index 00000000..0bc52f95 --- /dev/null +++ b/changelogs/client_server/newsfragments/2352.clarification @@ -0,0 +1 @@ +Clarify how to find `via` parameter when following room upgrades. diff --git a/content/client-server-api/modules/room_upgrades.md b/content/client-server-api/modules/room_upgrades.md index 230f7a8f..5a586be8 100644 --- a/content/client-server-api/modules/room_upgrades.md +++ b/content/client-server-api/modules/room_upgrades.md @@ -20,6 +20,10 @@ old room. Another approach may be to virtually merge the rooms such that the old room's timeline seamlessly continues into the new timeline without the user having to jump between the rooms. +When joining a room using the room ID in an `m.room.tombstone` event or +`predecessor` field on `m.room.create`, clients SHOULD parse the event +sender and use the resulting server name as a `via` parameter. + {{% http-api spec="client-server" api="room_upgrades" %}} #### Server behaviour