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

Inline "[New in this version]" in auth rules

Browse source 
This makes it much easier to see exactly what is new, and what is existing.
This commit is contained in:
Richard van der Hoff 2022-10-04 18:03:15 +01:00
parent 16f0ec9861
commit c50b3e808a
5 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/rooms/fragments/v3-auth-rules.md
View file

@ -2,7 +2,7 @@
toc_hide: true toc_hide: true
--- ---
{{% added-in this=true %}} In room versions 1 and 2, events need a {{< added-in this=true >}} In room versions 1 and 2, events need a
signature from the domain of the `event_id` in order to be considered signature from the domain of the `event_id` in order to be considered
valid. This room version does not include an `event_id` over federation valid. This room version does not include an `event_id` over federation
in the same respect, so does not need a signature from that server. in the same respect, so does not need a signature from that server.

4
content/rooms/v3.md
View file

@ -89,7 +89,7 @@ The complete structure of a event in a v3 room is shown below.
### Authorization rules ### Authorization rules
{{% added-in this=true %}} `m.room.redaction` events are no longer {{< added-in this=true >}} `m.room.redaction` events are no longer
explicitly part of the auth rules. They are still subject to the explicitly part of the auth rules. They are still subject to the
minimum power level rules, but should always fall into "11. Otherwise, minimum power level rules, but should always fall into "11. Otherwise,
allow". Instead of being authorized at the time of receipt, they are allow". Instead of being authorized at the time of receipt, they are
@ -97,7 +97,7 @@ authorized at a later stage: see the [Handling Redactions](#handling-redactions)
section below for more information. section below for more information.
<!-- set withVersioning=true so we get all the "new in this version" stuff --> <!-- set withVersioning=true so we get all the "new in this version" stuff -->
{{% rver-fragment name="v3-auth-rules" withVersioning=true %}} {{< rver-fragment name="v3-auth-rules" withVersioning=true >}}
## Unchanged from v2 ## Unchanged from v2

2
content/rooms/v7.md
View file

@ -32,7 +32,7 @@ as do the versions v6 is based upon.
### Authorization rules ### Authorization rules
{{% added-in this=true %}} For checks performed upon `m.room.member` events, a {{< added-in this=true >}} For checks performed upon `m.room.member` events, a
new point for `membership=knock` is added. new point for `membership=knock` is added.
Events must be signed by the server denoted by the `sender` property. Events must be signed by the server denoted by the `sender` property.

4
content/rooms/v8.md
View file

@ -83,11 +83,11 @@ room without invite. Otherwise, the room version inherits all properties of
### Authorization rules ### Authorization rules
{{% added-in this=true %}} For checks performed upon `m.room.member` events, new {{< added-in this=true >}} For checks performed upon `m.room.member` events, new
points for handling `content.join_authorised_via_users_server` are added (Rule 4.2 points for handling `content.join_authorised_via_users_server` are added (Rule 4.2
and 4.3.5). and 4.3.5).
{{% rver-fragment name="v8-auth-rules" %}} {{< rver-fragment name="v8-auth-rules" withVersioning=true >}}
### Redactions ### Redactions

2
content/rooms/v9.md
View file

@ -62,7 +62,7 @@ completeness.
### Authorization rules ### Authorization rules
{{% rver-fragment name="v8-auth-rules" %}} {{< rver-fragment name="v8-auth-rules" >}}
### State resolution ### State resolution