Merge pull request #168 from matrix-org/markjh/client_config
Add API for setting client config
This commit is contained in:
commit
a20a49abf6
5 changed files with 170 additions and 5 deletions
27
specification/modules/account_data.rst
Normal file
27
specification/modules/account_data.rst
Normal file
|
@ -0,0 +1,27 @@
|
|||
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
|
||||
----------------
|
||||
|
||||
{{v2_account_data_http_api}}
|
Loading…
Add table
Add a link
Reference in a new issue