Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2025-12-26 19:08:38 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Note that redactions of knocks are not a concern

Browse source
This commit is contained in:
Andrew Morgan 2020-10-08 18:04:32 +01:00
parent a924f5b3d5
commit 815dae6eae
1 changed files with 4 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
proposals/2403-knock.md
View file

@ -67,22 +67,10 @@ rules from room version 5 are:
has been banned from 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.
* Under "11. If type is `m.room.redaction`", the following should be added:
```
a. If the type of the `event_id` of the event being redacted is
`m.room.member` and the `membership` field in its `content` dictionary is
`knock`, reject.
```
Notes:
- The server you sent a knock through later should not be able to redact
that knock afterwards. The knock should instead be rejected by whoever
has the authority to.
XXX: Is this the best place in the auth rules to enforce this?
Additionally, note that redactions of knock events are not a concern, as
`membership` keys are excluded from being redacted as defined by all current
room versions.
## Membership changes
Once someone has sent a `knock` membership into the room, the membership for