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.
|
|
|
|
Client Config
|
|
|
|
|
=============
|
|
|
|
|
|
|
|
|
|
.. _module:account_data:
|
|
|
|
|
|
|
|
|
|
Clients can store custom config data for their account on their homeserver.
|
|
|
|
|
This account data will be synced between different devices and can persist
|
|
|
|
|
across installations on a particular device. Users may only view the account
|
|
|
|
|
data for their own account
|
|
|
|
|
|
|
|
|
|
The account_data may be either global or scoped to a particular rooms.
|
|
|
|
|
|
|
|
|
|
Events
|
|
|
|
|
------
|
|
|
|
|
|
|
|
|
|
The client recieves the account data as events in the ``account_data`` sections
|
|
|
|
|
of a v2 /sync.
|
|
|
|
|
|
|
|
|
|
These events can also be received in a v1 /events response or in the
|
|
|
|
|
``account_data`` section of a room in v1 /initialSync. ``m.tag``
|
|
|
|
|
events appearing in v1 /events will have a ``room_id`` with the room
|
|
|
|
|
the tags are for.
|
|
|
|
|
|
|
|
|
|
Client Behaviour
|
|
|
|
|
----------------
|
|
|
|
|
|
|
|
|
|
{{account_data_http_api}}
|
