From dcd6de59cdca0fb47162dde8ffa4a5f096641463 Mon Sep 17 00:00:00 2001 From: Patrick Cloke Date: Thu, 22 Jul 2021 10:18:14 -0400 Subject: [PATCH] De-indent section. --- proposals/3083-restricted-rooms.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/proposals/3083-restricted-rooms.md b/proposals/3083-restricted-rooms.md index a8b2af3d0..501625a56 100644 --- a/proposals/3083-restricted-rooms.md +++ b/proposals/3083-restricted-rooms.md @@ -92,22 +92,22 @@ caveat that servers must ensure that, for `m.room.member` events with a `members include the MXID of a local user who could issue an invite in the content with the key `join_authorised_via_users_server`. The actual user chosen is arbitrary. - This implies that: +The changes to the auth rules imply that: - * A join event issued via `/send_join` is signed by not just the requesting - server, but also the resident server.[3](#f3) +* A join event issued via `/send_join` is signed by not just the requesting + server, but also the resident server.[3](#f3) - In order for the joining server to receive the proper signatures the join - event will be returned via `/send_join` in the `event` field. - * The auth chain of the join event needs to include events which prove - the homeserver can be issuing the join. This can be done by including: + In order for the joining server to receive the proper signatures the join + event will be returned via `/send_join` in the `event` field. +* The auth chain of the join event needs to include events which prove + the homeserver can be issuing the join. This can be done by including: - * The `m.room.power_levels` event. - * The join event of the user specified in `join_authorised_via_users_server`. + * The `m.room.power_levels` event. + * The join event of the user specified in `join_authorised_via_users_server`. - It should be confirmed that the authorising user is in the room. (This - prevents situations where any homeserver could process the join, even if - they weren't in the room, under certain power level conditions.) + It should be confirmed that the authorising user is in the room. (This + prevents situations where any homeserver could process the join, even if + they weren't in the room, under certain power level conditions.) The above creates a new restriction on the relationship between the resident servers used for `/make_join` and `/send_join` -- they must now both go to