From 6919bbf80cd952a24b8168d1aac2a01a96699c85 Mon Sep 17 00:00:00 2001 From: Patrick Cloke Date: Fri, 4 Jun 2021 08:33:26 -0400 Subject: [PATCH] Remove bit about user IDs being listed directly. --- proposals/3083-restricted-rooms.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/proposals/3083-restricted-rooms.md b/proposals/3083-restricted-rooms.md index be507cb5..aa8f25e7 100644 --- a/proposals/3083-restricted-rooms.md +++ b/proposals/3083-restricted-rooms.md @@ -39,7 +39,7 @@ Membership in a single space is enough. If the `allow` key is an empty list (or not a list at all), then no users are allowed to join without an invite. Each entry is expected to be an object with the -following keys, or a string representing the MXID of the user exempted: +following keys: * `space`: The room ID of the space to check the membership of. * `via`: A list of servers which may be used to peek for membership of the space. @@ -57,7 +57,6 @@ response with HTTP status code of 403 and an `errcode` of `M_FORBIDDEN`. Unlike the `invite` join rule, confirmation that the `allow` rules were properly checked cannot be enforced over federation by event authorization, so servers in the room are trusted not to allow invalid users to join.[3](#f3) -However, user IDs listed as strings can be properly checked over federation. ## Summary of the behaviour of join rules