wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Apply suggestions from code review

Browse source 
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
This commit is contained in:
Patrick Cloke 2021-07-20 12:28:55 -04:00 • committed by Richard van der Hoff
parent d329c216c4
commit 27bee1bad8
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
proposals/3083-restricted-rooms.md
View file

@ -64,7 +64,7 @@ the user is not a member of at least one of the rooms, the homeserver should ret
an error response with HTTP status code of 403 and an `errcode` of `M_FORBIDDEN`. an error response with HTTP status code of 403 and an `errcode` of `M_FORBIDDEN`.
It is possible for a resident homeserver (one which receives a `/make_join` / It is possible for a resident homeserver (one which receives a `/make_join` /
`/send_join` request to not know if the user is in some of the allowed rooms (due `/send_join` request) to not know if the user is in some of the allowed rooms (due
to not participating in them). If the user is not in any of the allowed rooms that to not participating in them). If the user is not in any of the allowed rooms that
are known to the homeserver it should return an error response with HTTP status code are known to the homeserver it should return an error response with HTTP status code
of 400 with an `errcode` of `M_UNABLE_TO_AUTHORISE_JOIN`. The joining server should of 400 with an `errcode` of `M_UNABLE_TO_AUTHORISE_JOIN`. The joining server should
@ -74,7 +74,7 @@ with HTTP status code of 403 and an `errcode` of `M_FORBIDDEN`. Note that it is
configuration error if there are allowed rooms with no participating authorised configuration error if there are allowed rooms with no participating authorised
servers. servers.
A chosen resident homeserver might also be unable to issue invites, in this case A chosen resident homeserver might also be unable to issue invites; in this case
it should return an error response with HTTP status code of 400 and an `errcode` it should return an error response with HTTP status code of 400 and an `errcode`
of `M_CANNOT_ALLOW`. The joining server should attempt to join via another of `M_CANNOT_ALLOW`. The joining server should attempt to join via another
resident homeserver. resident homeserver.
@ -84,7 +84,7 @@ the `restricted` join rule has the same behavior as `public`, with the additiona
caveat that servers must ensure that: caveat that servers must ensure that:
* The user's previous membership was `invite` or `join`, or * The user's previous membership was `invite` or `join`, or
* The `m.room.member` event with a `membership` of `join` has a valid signature * The join event has a valid signature
from a homeserver whose users have the power to issue invites. This implies from a homeserver whose users have the power to issue invites. This implies
that: that: