From 22188ebfebb291ffb30a879045499aef12a9fef1 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Sun, 10 Feb 2019 19:54:20 -0700 Subject: [PATCH] Further clarify why membership events are not to be transferred --- specification/modules/room_upgrades.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/specification/modules/room_upgrades.rst b/specification/modules/room_upgrades.rst index 889c1068..f1861f72 100644 --- a/specification/modules/room_upgrades.rst +++ b/specification/modules/room_upgrades.rst @@ -61,7 +61,11 @@ When the client requests to upgrade a known room to a known version, the server: * ``m.room.join_rules`` * ``m.room.power_levels`` - Membership events should not be transferred to the new room. + Membership events should not be transferred to the new room due to technical limitations + of servers not being able to impersonate people from other homeservers. Additionally, + servers should not transfer state events which are sensitive to who sent them, such as + events outside of the Matrix namespace where clients may rely on the sender to match + certain criteria. 4. Moves any local aliases to the new room. 5. Sends a ``m.room.tombstone`` event to the old room to indicate that it is not intended