Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-02-07 23:03:43 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Allow knock->knock transitions

Browse source
This commit is contained in:
Andrew Morgan 2021-02-26 12:08:14 +00:00
parent e790ad2120
commit 49a72862a9
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
proposals/2403-knock.md
View file

@ -56,7 +56,7 @@ rules from room version 6](https://matrix.org/docs/spec/rooms/v6#authorization-r
f. If `membership` is `knock`:
i. If the `join_rule` is anything other than `knock`, reject.
ii. If `sender` does not match `state_key`, reject.
iii. If the `sender`'s membership is not `ban`, `knock`, `invite` or `join`, allow.
iii. If the `sender`'s membership is not `ban`, `invite` or `join`, allow.
iv. Otherwise, reject.
```
@ -66,9 +66,9 @@ Note that:
the `state_key` is the invitee.
- f.ii is justified as one user should not be able to knock on behalf of
another user.
- a.iii is justified as knocks should not be allowed if the knocking user
has been banned from the room, has already knocked on the room, is
invited to the room or if they are already in the room.
- f.iii is justified as knocks should not be allowed if the knocking user
has been banned from the room, is invited to the room or if they are already
in the room.
- Knocks are not restricted by power level like invites are. The `join_rules`
are already used to enforce whether someone can or cannot knock. However,
power level rules do apply when approving or denying the knock, as discussed