mirror of
https://github.com/matrix-org/matrix-spec
synced 2025-12-20 16:38:37 +01:00
add0f2232c
Some checks are pending
Spec / 🔎 Validate OpenAPI specifications (push) Waiting to run
Spec / 🔎 Check Event schema examples (push) Waiting to run
Spec / 🔎 Check OpenAPI definitions examples (push) Waiting to run
Spec / 🔎 Check JSON Schemas inline examples (push) Waiting to run
Spec / ⚙️ Calculate baseURL for later jobs (push) Waiting to run
Spec / 🐍 Build OpenAPI definitions (push) Blocked by required conditions
Spec / 📢 Run towncrier for changelog (push) Waiting to run
Spec / 📖 Build the spec (push) Blocked by required conditions
Spec / 🔎 Validate generated HTML (push) Blocked by required conditions
Spec / 📖 Build the historical backup spec (push) Blocked by required conditions
Spell Check / Spell Check with Typos (push) Waiting to run
26 lines
1.2 KiB
Markdown
26 lines
1.2 KiB
Markdown
---
|
|
---
|
|
{{% added-in v=3 %}} In room versions 1 and 2, redactions were
|
|
explicitly part of the [authorization rules](/rooms/v1/#authorization-rules)
|
|
under Rule 11. As of room version 3, these conditions no longer exist as
|
|
represented by [this version's authorization rules](#authorization-rules).
|
|
|
|
While redactions are always accepted by the authorization rules for
|
|
events, they should not be sent to clients until both the redaction
|
|
event and the event the redaction affects have been received, and can
|
|
be validated. If both events are valid and have been seen by the server,
|
|
then the server applies the redaction if one of the following conditions
|
|
is met:
|
|
|
|
1. The power level of the redaction event's `sender` is greater than or
|
|
equal to the *redact level*.
|
|
2. The domain of the redaction event's `sender` matches that of the
|
|
original event's `sender`.
|
|
|
|
Note that the first condition holds true even when the `sender` doesn't have a
|
|
high enough power level to send the type of event that they're redacting.
|
|
|
|
If the server would apply a redaction, the redaction event is also sent
|
|
to clients. Otherwise, the server simply waits for a valid partner event
|
|
to arrive where it can then re-check the above.
|