@ -17,7 +17,7 @@ and servers can implement the ignoring of users.
To ignore a user, effectively blocking them, the client should add the
To ignore a user, effectively blocking them, the client should add the
target user to the `m.ignored_user_list` event in their account data
target user to the `m.ignored_user_list` event in their account data
using [`/user/<user_id>/account_data/<type>`](/client-server-api/#put_matrixclientr0useruseridaccount_datatype). Once ignored, the client will no longer receive events sent by
using [`/user/<user_id>/account_data/<type>`](/client-server-api/#put_matrixclientv3useruseridaccount_datatype). Once ignored, the client will no longer receive events sent by
that user, with the exception of state events. The client should either
that user, with the exception of state events. The client should either
hide previous content sent by the newly ignored user or perform a new
hide previous content sent by the newly ignored user or perform a new
The primary motivation for this API is exchanging data that is
The primary motivation for this API is exchanging data that is
meaningless or undesirable to persist in the room DAG - for example,
meaningless or undesirable to persist in the room DAG - for example,
one-time authentication tokens or key data. It is not intended for
one-time authentication tokens or key data. It is not intended for
conversational data, which should be sent using the normal [`/rooms/<room_id>/send`](/client-server-api/#put_matrixclientr0roomsroomidsendeventtypetxnid) API for
conversational data, which should be sent using the normal [`/rooms/<room_id>/send`](/client-server-api/#put_matrixclientv3roomsroomidsendeventtypetxnid) API for
consistency throughout Matrix.
consistency throughout Matrix.
#### Client behaviour
#### Client behaviour
To send a message to other devices, a client should call
To send a message to other devices, a client should call
[`/sendToDevice`](/client-server-api/#put_matrixclientr0sendtodeviceeventtypetxnid). Only one message can be sent to each device per
[`/sendToDevice`](/client-server-api/#put_matrixclientv3sendtodeviceeventtypetxnid). Only one message can be sent to each device per
transaction, and they must all have the same event type. The device ID
transaction, and they must all have the same event type. The device ID
in the request body can be set to `*` to request that the message be
in the request body can be set to `*` to request that the message be
sent to all known devices.
sent to all known devices.
If there are send-to-device messages waiting for a client, they will be
If there are send-to-device messages waiting for a client, they will be
returned by [`/sync`](/client-server-api/#get_matrixclientr0sync), as detailed in [Extensions to /sync](/client-server-api/#extensions-to-sync). Clients should
returned by [`/sync`](/client-server-api/#get_matrixclientv3sync), as detailed in [Extensions to /sync](/client-server-api/#extensions-to-sync). Clients should
inspect the `type` of each returned event, and ignore any they do not
inspect the `type` of each returned event, and ignore any they do not
understand.
understand.
@ -33,7 +33,7 @@ understand.
Servers should store pending messages for local users until they are
Servers should store pending messages for local users until they are
successfully delivered to the destination device. When a client calls
successfully delivered to the destination device. When a client calls