mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-08-04 06:57:48 +02:00
Compare commits
4 commits
59b92ce9e6
...
656bf61a3c
| Author | SHA1 | Date | |
|---|---|---|---|
|
656bf61a3c | ||
|
|
1449321ea1 | ||
|
|
ba960f8d32 | ||
|
|
8bedf3882c |
6
.github/_typos.toml
vendored
6
.github/_typos.toml
vendored
|
|
@ -3,6 +3,12 @@ extend-exclude = ["/themes", "/attic", "/data-definitions", "*.css", "syntax.scs
|
|||
|
||||
[default]
|
||||
check-filename = true
|
||||
extend-ignore-re = [
|
||||
# Ignore lines that start with `# Copyright ` (i.e. comments containing a
|
||||
# copyright statement in YAML files), they may contain a first or last name
|
||||
# that can be wrongfully detected as typos.
|
||||
"(?Rm)^#\\s*Copyright\\s.*$",
|
||||
]
|
||||
|
||||
[default.extend-identifiers]
|
||||
au1ba7o = "au1ba7o"
|
||||
|
|
|
|||
|
|
@ -0,0 +1 @@
|
|||
Clarify formats of string types.
|
||||
|
|
@ -0,0 +1 @@
|
|||
Clarify formats of string types.
|
||||
|
|
@ -0,0 +1 @@
|
|||
Clarify formats of string types.
|
||||
1
changelogs/internal/newsfragments/2373.clarification
Normal file
1
changelogs/internal/newsfragments/2373.clarification
Normal file
|
|
@ -0,0 +1 @@
|
|||
Ignore typos in copyright statements.
|
||||
|
|
@ -90,11 +90,11 @@ room that the event was sent to or dismissing a notification in order
|
|||
for the event to count as "read". Clients SHOULD NOT send read receipts
|
||||
for events sent by their own user.
|
||||
|
||||
Similar to the rules for sending receipts, threaded receipts should appear
|
||||
in the context of the thread. If a thread is rendered behind a disclosure,
|
||||
the client hasn't yet shown the event (or any applicable read receipts)
|
||||
to the user. Once they expand the thread though, a threaded read receipt
|
||||
would be sent and per-thread receipts from other users shown.
|
||||
Similar to the rules for sending receipts, [threaded receipts](#threaded-read-receipts)
|
||||
should appear in the context of the thread. If a thread is rendered behind a
|
||||
disclosure, the client hasn't yet shown the event (or any applicable read
|
||||
receipts) to the user. Once they expand the thread though, a threaded read
|
||||
receipt would be sent and per-thread receipts from other users shown.
|
||||
|
||||
A client can update the markers for its user by interacting with the
|
||||
following HTTP APIs.
|
||||
|
|
@ -232,5 +232,5 @@ MUST NOT appear in this federated `m.receipt` EDU.
|
|||
|
||||
#### Security considerations
|
||||
|
||||
As receipts are sent outside the context of the event graph, there are
|
||||
no integrity checks performed on the contents of `m.receipt` events.
|
||||
As receipts are sent outside the context of the [event graph](/#event-graphs),
|
||||
there are no integrity checks performed on the contents of `m.receipt` events.
|
||||
|
|
|
|||
|
|
@ -1,20 +1,20 @@
|
|||
|
||||
### Voice over IP
|
||||
|
||||
This module outlines how two users in a room can set up a Voice over IP
|
||||
(VoIP) call to each other. Voice and video calls are built upon the
|
||||
WebRTC 1.0 standard. Call signalling is achieved by sending [message
|
||||
events](#events) to the room. In this version of the spec, only two-party
|
||||
communication is supported (e.g. between two peers, or between a peer
|
||||
This module outlines how two users in a room can set up a Voice over IP (VoIP)
|
||||
call to each other. Voice and video calls are built upon the [WebRTC 1.0
|
||||
standard](https://www.w3.org/TR/webrtc/). Call signalling is achieved by sending
|
||||
[message events](#events) to the room. In this version of the spec, only
|
||||
two-party communication is supported (e.g. between two peers, or between a peer
|
||||
and a multi-point conferencing unit). Calls can take place in rooms with
|
||||
multiple members, but only two devices can take part in the call.
|
||||
|
||||
All VoIP events have a `version` field. This is used to determine whether
|
||||
devices support this new version of the protocol. For example, clients can use
|
||||
this field to know whether to expect an `m.call.select_answer` event from their
|
||||
opponent. If clients see events with `version` other than `0` or `"1"`
|
||||
(including, for example, the numeric value `1`), they should treat these the
|
||||
same as if they had `version` == `"1"`.
|
||||
this field to know whether to expect an [`m.call.select_answer`](#mcallselect_answer)
|
||||
event from their opponent. If clients see events with `version` other than `0`
|
||||
or `"1"` (including, for example, the numeric value `1`), they should treat
|
||||
these the same as if they had `version` == `"1"`.
|
||||
|
||||
Note that this implies any and all future versions of VoIP events should be
|
||||
backwards-compatible. If it does become necessary to introduce a non
|
||||
|
|
@ -29,10 +29,10 @@ lowercase alphanumeric characters is recommended. Parties in the call are identi
|
|||
`(user_id, party_id)`.
|
||||
|
||||
The client adds a `party_id` field containing this ID to the top-level of the content of all VoIP events
|
||||
it sends on the call, including `m.call.invite`. Clients use this to identify remote echo of their own
|
||||
events: since a user may call themselves, they cannot simply ignore events from their own user. This
|
||||
field also identifies different answers sent by different clients to an invite, and matches `m.call.candidates`
|
||||
events to their respective answer/invite.
|
||||
it sends on the call, including [`m.call.invite`](#mcallinvite). Clients use this to identify remote echo
|
||||
of their own events: since a user may call themselves, they cannot simply ignore events from their own
|
||||
user. This field also identifies different answers sent by different clients to an invite, and matches
|
||||
[`m.call.candidates`](#mcallcandidates) events to their respective answer/invite.
|
||||
|
||||
A client implementation may choose to use the device ID used in end-to-end cryptography for this purpose,
|
||||
or it may choose, for example, to use a different one for each call to avoid leaking information on which
|
||||
|
|
@ -44,15 +44,16 @@ A grammar for `party_id` is defined [below](#grammar-for-voip-ids).
|
|||
#### Politeness
|
||||
In line with [WebRTC perfect negotiation](https://w3c.github.io/webrtc-pc/#perfect-negotiation-example)
|
||||
there are rules to establish which party is polite in the process of renegotiation. The callee is
|
||||
always the polite party. In a glare situation, the politeness of a party is therefore determined by
|
||||
whether the inbound or outbound call is used: if a client discards its outbound call in favour of
|
||||
an inbound call, it becomes the polite party.
|
||||
always the polite party. In a [glare](#glare) situation, the politeness of a party is therefore
|
||||
determined by whether the inbound or outbound call is used: if a client discards its outbound call
|
||||
in favour of an inbound call, it becomes the polite party.
|
||||
|
||||
#### Call Event Liveness
|
||||
`m.call.invite` contains a `lifetime` field that indicates how long the offer is valid for. When
|
||||
a client receives an invite, it should use the event's `age` field in the sync response plus the
|
||||
time since it received the event from the homeserver to determine whether the invite is still valid.
|
||||
The use of the `age` field ensures that incorrect clocks on client devices don't break calls.
|
||||
[`m.call.invite`](#mcallinvite) contains a `lifetime` field that indicates how long the offer is
|
||||
valid for. When a client receives an invite, it should use the event's `age` field in the
|
||||
[`GET /sync`](#get_matrixclientv3sync) response plus the time since it received the event from the
|
||||
homeserver to determine whether the invite is still valid. The use of the `age` field ensures that
|
||||
incorrect clocks on client devices don't break calls.
|
||||
|
||||
If the invite is still valid *and will remain valid for long enough for the user to accept the call*,
|
||||
it should signal an incoming call. The amount of time allowed for the user to accept the call may
|
||||
|
|
@ -83,7 +84,7 @@ Clients should aim to send a small number of candidate events, with guidelines:
|
|||
|
||||
#### End-of-candidates
|
||||
An ICE candidate whose value is the empty string means that no more ICE candidates will
|
||||
be sent. Clients must send such a candidate in an `m.call.candidates` message.
|
||||
be sent. Clients must send such a candidate in an [`m.call.candidates`](#mcallcandidates) message.
|
||||
The WebRTC spec requires browsers to generate such a candidate, however note that at time of writing,
|
||||
not all browsers do (Chrome does not, but does generate an `icegatheringstatechange` event). The
|
||||
client should send any remaining candidates once candidate generation finishes, ignoring timeouts above.
|
||||
|
|
@ -130,36 +131,48 @@ or not there have been any changes to the Matrix spec.
|
|||
A call is set up with message events exchanged as follows:
|
||||
|
||||
```nohighlight
|
||||
Caller Callee
|
||||
[Place Call]
|
||||
m.call.invite ----------->
|
||||
m.call.candidate -------->
|
||||
[..candidates..] -------->
|
||||
[Answers call]
|
||||
<--------------- m.call.answer
|
||||
m.call.select_answer ----------->
|
||||
[Call is active and ongoing]
|
||||
<--------------- m.call.hangup
|
||||
+---------+ +---------+
|
||||
| Caller | | Callee |
|
||||
+---------+ +---------+
|
||||
| |
|
||||
(Places Call) |
|
||||
|------- m.call.invite ------->|
|
||||
|----- m.call.candidate ------>|
|
||||
|----- [..candidates..] ------>|
|
||||
| |
|
||||
| (Answers call)
|
||||
|<------ m.call.answer --------|
|
||||
|--- m.call.select_answer --->|
|
||||
. .
|
||||
. (Call is active and ongoing) .
|
||||
. .
|
||||
| (Ends call)
|
||||
|<------ m.call.hangup --------|
|
||||
```
|
||||
|
||||
Or a rejected call:
|
||||
|
||||
```nohighlight
|
||||
Caller Callee
|
||||
m.call.invite ------------>
|
||||
m.call.candidate --------->
|
||||
[..candidates..] --------->
|
||||
[Rejects call]
|
||||
<-------------- m.call.hangup
|
||||
+---------+ +---------+
|
||||
| Caller | | Callee |
|
||||
+---------+ +---------+
|
||||
| |
|
||||
(Places Call) |
|
||||
|------- m.call.invite ------->|
|
||||
|----- m.call.candidate ------>|
|
||||
|----- [..candidates..] ------>|
|
||||
| |
|
||||
| (Rejects call)
|
||||
|<------ m.call.reject --------|
|
||||
```
|
||||
|
||||
Calls are negotiated according to the WebRTC specification.
|
||||
|
||||
In response to an incoming invite, a client may do one of several things:
|
||||
* Attempt to accept the call by sending an `m.call.answer`.
|
||||
* Actively reject the call everywhere: send an `m.call.reject` as per above, which will stop the call from
|
||||
ringing on all the user's devices and the caller's client will inform them that the user has
|
||||
rejected their call.
|
||||
* Attempt to accept the call by sending an [`m.call.answer`](#mcallanswer).
|
||||
* Actively reject the call everywhere: send an [`m.call.reject`](#mcallreject) as per above, which
|
||||
will stop the call from ringing on all the user's devices and the caller's client will inform
|
||||
them that the user has rejected their call.
|
||||
* Ignore the call: send no events, but stop alerting the user about the call. The user's other
|
||||
devices will continue to ring, and the caller's device will continue to indicate that the call
|
||||
is ringing, and will time the call out in the normal way if no other device responds.
|
||||
|
|
@ -224,8 +237,8 @@ As calls are "placed" to rooms rather than users, the glare resolution
|
|||
algorithm outlined below is only considered for calls which are to the
|
||||
same room. The algorithm is as follows:
|
||||
|
||||
- If an `m.call.invite` to a room is received whilst the client is
|
||||
**preparing to send** an `m.call.invite` to the same room:
|
||||
- If an [`m.call.invite`](#mcallinvite) to a room is received whilst the
|
||||
client is **preparing to send** an `m.call.invite` to the same room:
|
||||
- the client should cancel its outgoing call and instead
|
||||
automatically accept the incoming call on behalf of the user.
|
||||
- If an `m.call.invite` to a room is received **after the client has
|
||||
|
|
|
|||
|
|
@ -35,6 +35,8 @@ paths:
|
|||
example: "!wefuh21ffskfuh345:example.com"
|
||||
schema:
|
||||
type: string
|
||||
format: mx-room-id
|
||||
pattern: "^!"
|
||||
- in: path
|
||||
name: receiptType
|
||||
description: |-
|
||||
|
|
@ -62,6 +64,8 @@ paths:
|
|||
example: $1924376522eioj:example.com
|
||||
schema:
|
||||
type: string
|
||||
format: mx-event-id
|
||||
pattern: "^\\$"
|
||||
requestBody:
|
||||
content:
|
||||
application/json:
|
||||
|
|
@ -72,7 +76,8 @@ paths:
|
|||
type: string
|
||||
x-addedInMatrixVersion: "1.4"
|
||||
description: |-
|
||||
The root thread event's ID (or `main`) for which
|
||||
The [thread root](/client-server-api/#threading)'s
|
||||
[event ID](/appendices#event-ids) (or `main`) for which
|
||||
thread this receipt is intended to be under. If
|
||||
not specified, the read receipt is *unthreaded*
|
||||
(default).
|
||||
|
|
|
|||
|
|
@ -36,6 +36,8 @@ paths:
|
|||
example: "@alice:example.com"
|
||||
schema:
|
||||
type: string
|
||||
format: mx-user-id
|
||||
pattern: "^@"
|
||||
- in: path
|
||||
name: roomId
|
||||
description: The room in which the user is typing.
|
||||
|
|
@ -43,6 +45,8 @@ paths:
|
|||
example: "!wefh3sfukhs:example.com"
|
||||
schema:
|
||||
type: string
|
||||
format: mx-room-id
|
||||
pattern: "^!"
|
||||
requestBody:
|
||||
content:
|
||||
application/json:
|
||||
|
|
|
|||
|
|
@ -44,6 +44,8 @@ paths:
|
|||
type: array
|
||||
items:
|
||||
type: string
|
||||
format: uri
|
||||
pattern: "^turns?:"
|
||||
description: A list of TURN URIs
|
||||
ttl:
|
||||
type: integer
|
||||
|
|
|
|||
|
|
@ -1,44 +1,37 @@
|
|||
{
|
||||
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
||||
"type": "object",
|
||||
"description": "This event is sent by the callee when they wish to answer the call.",
|
||||
"x-weight": 40,
|
||||
"allOf": [{
|
||||
"$ref": "core-event-schema/room_event.yaml"
|
||||
}],
|
||||
"properties": {
|
||||
"content": {
|
||||
"type": "object",
|
||||
"allOf": [{
|
||||
"$ref": "core-event-schema/call_event.yaml"
|
||||
}],
|
||||
"properties": {
|
||||
"answer": {
|
||||
"type": "object",
|
||||
"title": "Answer",
|
||||
"description": "The session description object",
|
||||
"properties": {
|
||||
"type": {
|
||||
"type": "string",
|
||||
"enum": ["answer"],
|
||||
"description": "The type of session description."
|
||||
},
|
||||
"sdp": {
|
||||
"type": "string",
|
||||
"description": "The SDP text of the session description."
|
||||
}
|
||||
},
|
||||
"required": ["type", "sdp"]
|
||||
},
|
||||
"sdp_stream_metadata": {
|
||||
"$ref": "components/sdp_stream_metadata.yaml"
|
||||
}
|
||||
},
|
||||
"required": ["answer"]
|
||||
},
|
||||
"type": {
|
||||
"type": "string",
|
||||
"enum": ["m.call.answer"]
|
||||
}
|
||||
}
|
||||
}
|
||||
$schema: https://json-schema.org/draft/2020-12/schema
|
||||
|
||||
type: object
|
||||
description: This event is sent by the callee when they wish to answer the call.
|
||||
x-weight: 40
|
||||
allOf:
|
||||
- $ref: core-event-schema/room_event.yaml
|
||||
properties:
|
||||
content:
|
||||
type: object
|
||||
allOf:
|
||||
- $ref: core-event-schema/call_event.yaml
|
||||
properties:
|
||||
answer:
|
||||
type: object
|
||||
title: Answer
|
||||
description: The session description object
|
||||
properties:
|
||||
type:
|
||||
type: string
|
||||
enum:
|
||||
- answer
|
||||
description: The type of session description.
|
||||
sdp:
|
||||
type: string
|
||||
description: The SDP text of the session description.
|
||||
required:
|
||||
- type
|
||||
- sdp
|
||||
sdp_stream_metadata:
|
||||
$ref: components/sdp_stream_metadata.yaml
|
||||
required:
|
||||
- answer
|
||||
type:
|
||||
type: string
|
||||
enum:
|
||||
- m.call.answer
|
||||
|
|
|
|||
|
|
@ -1,53 +1,47 @@
|
|||
{
|
||||
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
||||
"type": "object",
|
||||
"description": "This event is sent by the caller when they wish to establish a call.",
|
||||
"x-weight": 10,
|
||||
"allOf": [{
|
||||
"$ref": "core-event-schema/room_event.yaml"
|
||||
}],
|
||||
"properties": {
|
||||
"content": {
|
||||
"type": "object",
|
||||
"allOf": [{
|
||||
"$ref": "core-event-schema/call_event.yaml"
|
||||
}],
|
||||
"properties": {
|
||||
"offer": {
|
||||
"type": "object",
|
||||
"title": "Offer",
|
||||
"description": "The session description object",
|
||||
"properties": {
|
||||
"type": {
|
||||
"type": "string",
|
||||
"enum": ["offer"],
|
||||
"description": "The type of session description."
|
||||
},
|
||||
"sdp": {
|
||||
"type": "string",
|
||||
"description": "The SDP text of the session description."
|
||||
}
|
||||
},
|
||||
"required": ["type", "sdp"]
|
||||
},
|
||||
"lifetime": {
|
||||
"type": "integer",
|
||||
"description": "The time in milliseconds that the invite is valid for. Once the invite age exceeds this value, clients should discard it. They should also no longer show the call as awaiting an answer in the UI."
|
||||
},
|
||||
"invitee": {
|
||||
"type": "string",
|
||||
"description": "The ID of the user being called. If omitted, any user in the room can answer.",
|
||||
"x-addedInMatrixVersion": "1.7"
|
||||
},
|
||||
"sdp_stream_metadata": {
|
||||
"$ref": "components/sdp_stream_metadata.yaml"
|
||||
}
|
||||
},
|
||||
"required": ["offer", "lifetime"]
|
||||
},
|
||||
"type": {
|
||||
"type": "string",
|
||||
"enum": ["m.call.invite"]
|
||||
}
|
||||
}
|
||||
}
|
||||
$schema: https://json-schema.org/draft/2020-12/schema
|
||||
|
||||
type: object
|
||||
description: This event is sent by the caller when they wish to establish a call.
|
||||
x-weight: 10
|
||||
allOf:
|
||||
- $ref: core-event-schema/room_event.yaml
|
||||
properties:
|
||||
content:
|
||||
type: object
|
||||
allOf:
|
||||
- $ref: core-event-schema/call_event.yaml
|
||||
properties:
|
||||
offer:
|
||||
type: object
|
||||
title: Offer
|
||||
description: The session description object
|
||||
properties:
|
||||
type:
|
||||
type: string
|
||||
enum:
|
||||
- offer
|
||||
description: The type of session description.
|
||||
sdp:
|
||||
type: string
|
||||
description: The SDP text of the session description.
|
||||
required:
|
||||
- type
|
||||
- sdp
|
||||
lifetime:
|
||||
type: integer
|
||||
description: The time in milliseconds that the invite is valid for. Once the invite age exceeds this value, clients should discard it. They should also no longer show the call as awaiting an answer in the UI.
|
||||
invitee:
|
||||
type: string
|
||||
description: The ID of the user being called. If omitted, any user in the room can answer.
|
||||
x-addedInMatrixVersion: '1.7'
|
||||
format: mx-user-id
|
||||
pattern: "^@"
|
||||
sdp_stream_metadata:
|
||||
$ref: components/sdp_stream_metadata.yaml
|
||||
required:
|
||||
- offer
|
||||
- lifetime
|
||||
type:
|
||||
type: string
|
||||
enum:
|
||||
- m.call.invite
|
||||
|
|
|
|||
|
|
@ -1,29 +1,23 @@
|
|||
{
|
||||
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
||||
"type": "object",
|
||||
"description": "This event is sent by the caller's client once it has decided which other client to talk to, by selecting one of multiple possible incoming `m.call.answer` events. Its `selected_party_id` field indicates the answer it's chosen. The `call_id` and `party_id` of the caller is also included. If the callee's client sees a `select_answer` for an answer with party ID other than the one it sent, it ends the call and informs the user the call was answered elsewhere. It does not send any events. Media can start flowing before this event is seen or even sent. Clients that implement previous versions of this specification will ignore this event and behave as they did before.",
|
||||
"x-addedInMatrixVersion": "1.7",
|
||||
"x-weight": 50,
|
||||
"allOf": [{
|
||||
"$ref": "core-event-schema/room_event.yaml"
|
||||
}],
|
||||
"properties": {
|
||||
"content": {
|
||||
"type": "object",
|
||||
"allOf": [{
|
||||
"$ref": "core-event-schema/call_event.yaml"
|
||||
}],
|
||||
"properties": {
|
||||
"selected_party_id": {
|
||||
"type": "string",
|
||||
"description": "The `party_id` field from the answer event that the caller chose."
|
||||
},
|
||||
},
|
||||
"required": ["selected_party_id"]
|
||||
},
|
||||
"type": {
|
||||
"type": "string",
|
||||
"enum": ["m.call.select_answer"]
|
||||
}
|
||||
}
|
||||
}
|
||||
$schema: https://json-schema.org/draft/2020-12/schema
|
||||
|
||||
type: object
|
||||
description: This event is sent by the caller's client once it has decided which other client to talk to, by selecting one of multiple possible incoming `m.call.answer` events. Its `selected_party_id` field indicates the answer it's chosen. The `call_id` and `party_id` of the caller is also included. If the callee's client sees a `select_answer` for an answer with party ID other than the one it sent, it ends the call and informs the user the call was answered elsewhere. It does not send any events. Media can start flowing before this event is seen or even sent. Clients that implement previous versions of this specification will ignore this event and behave as they did before.
|
||||
x-addedInMatrixVersion: '1.7'
|
||||
x-weight: 50
|
||||
allOf:
|
||||
- $ref: core-event-schema/room_event.yaml
|
||||
properties:
|
||||
content:
|
||||
type: object
|
||||
allOf:
|
||||
- $ref: core-event-schema/call_event.yaml
|
||||
properties:
|
||||
selected_party_id:
|
||||
type: string
|
||||
description: The `party_id` field from the answer event that the caller chose.
|
||||
required:
|
||||
- selected_party_id
|
||||
type:
|
||||
type: string
|
||||
enum:
|
||||
- m.call.select_answer
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ properties:
|
|||
type: object
|
||||
description: |-
|
||||
A collection of users who have sent `m.read` receipts for
|
||||
this event. The string key is the user ID the receipt
|
||||
this event. The string key is the user ID the receipt
|
||||
belongs to.
|
||||
patternProperties:
|
||||
"^@": &receiptUserMap
|
||||
|
|
@ -46,10 +46,10 @@ properties:
|
|||
type: string
|
||||
x-addedInMatrixVersion: "1.4"
|
||||
description: |-
|
||||
The root thread event's ID (or `main`) for which
|
||||
thread this receipt is intended to be under. If
|
||||
not specified, the read receipt is *unthreaded*
|
||||
(default).
|
||||
The [thread root](/client-server-api/#threading)'s
|
||||
[event ID](/appendices#event-ids) (or `main`) for which
|
||||
thread this receipt is intended to be under. If not
|
||||
specified, the read receipt is *unthreaded* (default).
|
||||
"m.read.private":
|
||||
type: object
|
||||
description: |-
|
||||
|
|
|
|||
|
|
@ -1,29 +1,27 @@
|
|||
{
|
||||
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
||||
"type": "object",
|
||||
"title": "Typing Event",
|
||||
"description": "Informs the client of the list of users currently typing.",
|
||||
"allOf": [{
|
||||
"$ref": "core-event-schema/event.yaml"
|
||||
}],
|
||||
"properties": {
|
||||
"content": {
|
||||
"type": "object",
|
||||
"properties": {
|
||||
"user_ids": {
|
||||
"type": "array",
|
||||
"items": {
|
||||
"type": "string"
|
||||
},
|
||||
"description": "The list of user IDs typing in this room, if any."
|
||||
}
|
||||
},
|
||||
"required": ["user_ids"]
|
||||
},
|
||||
"type": {
|
||||
"type": "string",
|
||||
"enum": ["m.typing"]
|
||||
}
|
||||
},
|
||||
"required": ["type", "content"]
|
||||
}
|
||||
$schema: https://json-schema.org/draft/2020-12/schema
|
||||
|
||||
type: object
|
||||
title: Typing Event
|
||||
description: Informs the client of the list of users currently typing.
|
||||
allOf:
|
||||
- $ref: core-event-schema/event.yaml
|
||||
properties:
|
||||
content:
|
||||
type: object
|
||||
properties:
|
||||
user_ids:
|
||||
type: array
|
||||
items:
|
||||
type: string
|
||||
format: mx-user-id
|
||||
pattern: "^@"
|
||||
description: The list of user IDs typing in this room, if any.
|
||||
required:
|
||||
- user_ids
|
||||
type:
|
||||
type: string
|
||||
enum:
|
||||
- m.typing
|
||||
required:
|
||||
- type
|
||||
- content
|
||||
|
|
|
|||
Loading…
Reference in a new issue