From 158146ed3f2394955f77ae1a48d8c097fd433324 Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 19 Jul 2023 14:21:57 +0100 Subject: [PATCH] Clarify that this does not affect auth rules --- proposals/3901-deleting-state.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/proposals/3901-deleting-state.md b/proposals/3901-deleting-state.md index 55005cbeb3d..76e62121c7a 100644 --- a/proposals/3901-deleting-state.md +++ b/proposals/3901-deleting-state.md @@ -357,6 +357,9 @@ value is the ID of the `m.room.create` event of the new room. (This makes a later step, automatically accepting these invitations, possible - see sub-proposal 3). +Note that this behaviour does not affect the auth rules for either room in any +way: the server simply sends invitations on behalf of the upgrading user. + #### Specific spec wording changes In point 3 of Server behaviour: @@ -471,6 +474,10 @@ true, the server should auto-join the user to the new room by emitting an the old room (excluding `join_authorised_via_users_server`, which should be omitted since the user is invited, so does not need additional authorisation). +Note that this behaviour does not affect the auth rules for either room in any +way: the server simply accepts invitations on behalf of the user under these +circumstances. + ### Potential issues ### Alternatives