Compare commits

...

4 commits

Author SHA1 Message Date
Logan Devine 9da1793f0b
Merge b41698af55 into bf5fbc9945 2026-07-14 16:06:41 -07:00
Logan Devine b41698af55
Remove line wrapping from changelog
Co-authored-by: Travis Ralston <travpc@gmail.com>
2026-07-13 17:56:24 -07:00
Logan Devine 89cc8a71a7
Specify behavior of the m.policy room type, fix changelog
Signed-off-by: Logan Devine <logan@zirco.dev>
2026-07-13 17:45:29 -07:00
Logan Devine 94dd59b049
Spec for MSC3784: Using room type of m.policy for policy rooms
Signed-off-by: Logan Devine <logan@zirco.dev>
2026-07-12 11:21:25 -07:00
3 changed files with 6 additions and 0 deletions

View file

@ -0,0 +1 @@
Introduce room type `m.policy` to indicate rooms likely to contain policy lists, as per [MSC3784](https://github.com/matrix-org/matrix-spec-proposals/pull/3784).

View file

@ -3820,6 +3820,7 @@ the create room request.
In this specification the following room types are specified:
* [`m.space`](#spaces)
* [`m.policy`](#moderation-policy-lists)
Unspecified room types are permitted through the use of
[Namespaced Identifiers](/appendices/#common-namespaced-identifier-grammar).

View file

@ -22,6 +22,10 @@ restrictions on how the rooms can be configured in terms of
[join rules](#mroomjoin_rules), [history visibility](#room-history-visibility),
encryption, etc.
A moderation policy list may be designated by the [`m.policy` room type](#types),
however, policy events may still be sent in rooms without this room type. Sending
messages in rooms with the `m.policy` room type is discouraged, but not forbidden.
There are currently 3 kinds of entities which can be affected by rules:
`user`, `server`, and `room`. All 3 are described with
`m.policy.rule.<kind>` state events. The `state_key` for a policy rule