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

Namespace the allow type.

Browse source
This commit is contained in:
Patrick Cloke 2021-06-15 13:11:57 -04:00 • committed by Richard van der Hoff
parent 955160c750
commit 486026a711
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -20,12 +20,12 @@ to trust for membership. For example:
"join_rule": "restricted",
"allow": [
{
"type": "room-membership",
"type": "m.room_membership",
"room": "!mods:example.org",
"via": ["example.org"]
},
{
"type": "room-membership",
"type": "m.room_membership",
"room": "!users:example.org",
"via": ["example.org"]
}
@ -42,7 +42,7 @@ 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:
* `type`: `"room-membership"` to describe that we are allowing access via room
* `type`: `"m.room_membership"` to describe that we are allowing access via room
membership. Future MSCs may define other types.
* `room`: The room ID to check the membership of.
* `via`: A list of servers which may be used to peek for membership of the room.
@ -98,8 +98,8 @@ The `restricted` join rule will be included in a future room version to allow
servers and clients to opt-into the new functionality.
During development, an unstable room version of `org.matrix.msc3083` will be used.
Since the room version namespaces the behaviour, the `allow` key and the
`restricted` value do not need unstable prefixes.
Since the room version namespaces the behaviour, the `allow` key and value, as well
as the `restricted` join rule value do not need unstable prefixes.
## Alternatives