mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-08-04 06:57:48 +02:00
Compare commits
5 commits
2c19f16f6c
...
f802f81de6
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
f802f81de6 | ||
|
|
4c2bb5aae1 | ||
|
|
b41698af55 | ||
|
|
89cc8a71a7 | ||
|
|
94dd59b049 |
1
changelogs/client_server/newsfragments/2411.feature
Normal file
1
changelogs/client_server/newsfragments/2411.feature
Normal 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).
|
||||
|
|
@ -0,0 +1 @@
|
|||
Use MXC URI type for all user `avatar_url` fields. Contributed by @networkException.
|
||||
|
|
@ -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).
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -54,7 +54,8 @@ properties:
|
|||
example: true
|
||||
avatar_url:
|
||||
type: string
|
||||
format: uri
|
||||
format: mx-mxc-uri
|
||||
pattern: "^mxc:\\/\\/"
|
||||
description: The URL for the room's avatar, if one is set.
|
||||
example: "mxc://example.org/abcdef"
|
||||
join_rule:
|
||||
|
|
|
|||
|
|
@ -340,7 +340,8 @@ paths:
|
|||
description: The display name of the user this object is representing.
|
||||
avatar_url:
|
||||
type: string
|
||||
format: uri
|
||||
format: mx-mxc-uri
|
||||
pattern: "^mxc:\\/\\/"
|
||||
description: The avatar of the user this object is representing, as an [`mxc://`
|
||||
URI](/client-server-api/#matrix-content-mxc-uris).
|
||||
description: A map from user ID to a RoomMember object.
|
||||
|
|
|
|||
|
|
@ -238,7 +238,8 @@ paths:
|
|||
title: Display name
|
||||
avatar_url:
|
||||
type: string
|
||||
format: uri
|
||||
format: mx-mxc-uri
|
||||
pattern: "^mxc:\\/\\/"
|
||||
title: Avatar Url
|
||||
events_before:
|
||||
type: array
|
||||
|
|
|
|||
|
|
@ -90,7 +90,8 @@ paths:
|
|||
description: The display name of the user, if one exists.
|
||||
avatar_url:
|
||||
type: string
|
||||
format: uri
|
||||
format: mx-mxc-uri
|
||||
pattern: "^mxc:\\/\\/"
|
||||
example: mxc://bar.com/foo
|
||||
description: The avatar url, as an [`mxc://`
|
||||
URI](/client-server-api/#matrix-content-mxc-uris),
|
||||
|
|
|
|||
|
|
@ -172,6 +172,8 @@ paths:
|
|||
example: John Doe
|
||||
avatar_url:
|
||||
type: string
|
||||
format: mx-mxc-uri
|
||||
pattern: "^mxc:\\/\\/"
|
||||
description: |-
|
||||
The avatar URL for the user's avatar. MUST either be omitted or set to
|
||||
`null` if the user does not have an avatar set.
|
||||
|
|
|
|||
|
|
@ -12,6 +12,8 @@
|
|||
"properties": {
|
||||
"avatar_url": {
|
||||
"type": "string",
|
||||
"format": "mx-mxc-uri",
|
||||
"pattern": "^mxc:\\/\\/",
|
||||
"description": "The current avatar URL for this user, if any."
|
||||
},
|
||||
"displayname": {
|
||||
|
|
|
|||
|
|
@ -53,7 +53,8 @@ properties:
|
|||
avatar_url:
|
||||
description: 'The avatar URL for this user, if any.'
|
||||
type: string
|
||||
format: uri
|
||||
format: mx-mxc-uri
|
||||
pattern: "^mxc:\\/\\/"
|
||||
displayname:
|
||||
description: 'The display name for this user, if any.'
|
||||
type:
|
||||
|
|
|
|||
Loading…
Reference in a new issue