mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-03-26 13:04:10 +01:00
Misc cleanup and clarification for fragments
This commit is contained in:
parent
0eec78d8d6
commit
41ed640130
|
|
@ -2,9 +2,6 @@
|
||||||
toc_hide: true
|
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 %}}
|
{{% boxes/rationale %}}
|
||||||
Without the `join_authorised_via_users_server` property, redacted join events
|
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
|
can become invalid when verifying the auth chain of a given event, thus creating
|
||||||
|
|
|
||||||
|
|
@ -44,7 +44,9 @@ use cases should reference.
|
||||||
added "join restrictions" (refined by [room version 9](/rooms/v9)) - both allow
|
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
|
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
|
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
|
This room version additionally requires that values in the power levels event
|
||||||
be integers and not string representations, unlike other room versions.
|
be integers and not string representations, unlike other room versions.
|
||||||
|
|
|
||||||
|
|
@ -17,6 +17,9 @@ Clients which implement the redaction algorithm locally should refer to the
|
||||||
|
|
||||||
### Redactions
|
### 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" %}}
|
{{% rver-fragment name="v9-redactions" %}}
|
||||||
|
|
||||||
## Server implementation components
|
## Server implementation components
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue