Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-26 04:54:10 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Misc cleanup and clarification for fragments

Browse source
This commit is contained in:
Travis Ralston 2022-05-30 14:45:33 -06:00
parent 0eec78d8d6
commit 41ed640130
3 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
content/rooms/fragments/v9-redactions.md
View file

@ -2,9 +2,6 @@
toc_hide: true
---
{{% added-in this=true %}} `m.room.member` now keep `join_authorised_via_users_server`
in addition to other keys in `content` when being redacted.
{{% boxes/rationale %}}
Without the `join_authorised_via_users_server` property, redacted join events
can become invalid when verifying the auth chain of a given event, thus creating

4
content/rooms/v10.md
View file

@ -44,7 +44,9 @@ use cases should reference.
added "join restrictions" (refined by [room version 9](/rooms/v9)) - both allow
prospective members an avenue to join, however both could not be used at the
same time due to how the join rules work. This room version adds a new
`knock_restricted` join rule as a mix of the two behaviours (first match wins).
`knock_restricted` join rule as a mix of the two behaviours, allowing a user to
join the room if they meet either the `restricted` join rule criteria or the
`knock` join rule criteria - whichever function they're attempting to use.
This room version additionally requires that values in the power levels event
be integers and not string representations, unlike other room versions.

3
content/rooms/v9.md
View file

@ -17,6 +17,9 @@ Clients which implement the redaction algorithm locally should refer to the
### Redactions
{{% added-in this=true %}} `m.room.member` now keep `join_authorised_via_users_server`
in addition to other keys in `content` when being redacted.
{{% rver-fragment name="v9-redactions" %}}
## Server implementation components