From fd0c90964400b5cc05dfb24b2163fbefa8cfc197 Mon Sep 17 00:00:00 2001 From: Patrick Cloke Date: Thu, 22 Jul 2021 10:17:37 -0400 Subject: [PATCH] Clarifications. Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> --- proposals/3083-restricted-rooms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/3083-restricted-rooms.md b/proposals/3083-restricted-rooms.md index 4994ed06..a8b2af3d 100644 --- a/proposals/3083-restricted-rooms.md +++ b/proposals/3083-restricted-rooms.md @@ -82,7 +82,7 @@ resident homeserver. From the perspective of the [auth rules](https://spec.matrix.org/unstable/rooms/v1/#authorization-rules), the `restricted` join rule has the same behavior as `public`, with the additional -caveat that servers must ensure that: +caveat that servers must ensure that, for `m.room.member` events with a `membership` of `join`: * The user's previous membership was `invite` or `join`, or * The join event has a valid signature from a homeserver whose users have the