You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
27 lines
680 B
ReStructuredText
27 lines
680 B
ReStructuredText
9 years ago
|
Client Config
|
||
|
|
=============
|
||
|
|
|
||
|
9 years ago
|
.. _module:account_data:
|
||
|
9 years ago
|
|
||
|
|
Clients can store their config on their homeserver. This config will be synced
|
||
|
|
between different devices and can persist across installations on a particular
|
||
|
|
device.
|
||
|
|
|
||
|
|
The config may be either global or scoped to a particular rooms.
|
||
|
|
|
||
|
|
Events
|
||
|
|
------
|
||
|
|
|
||
|
9 years ago
|
The client recieves the config as a event in the ``account_data`` sections
|
||
|
9 years ago
|
of a v2 /sync.
|
||
|
|
|
||
|
|
These events can also be received in a v1 /events response or in the
|
||
|
9 years ago
|
``account_data`` section of a room in v1 /initialSync. ``m.tag``
|
||
|
9 years ago
|
events appearing in v1 /events will have a ``room_id`` with the room
|
||
|
|
the tags are for.
|
||
|
|
|
||
|
|
Client Behaviour
|
||
|
|
----------------
|
||
|
|
|
||
|
9 years ago
|
{{v2_account_data_http_api}}
|