wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Linkify endpoints properly

Browse source
This commit is contained in:
David Baker 2016-10-05 18:19:17 +01:00
parent 2259a00ba2
commit 2a987c3369
2 changed files with 6 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

3
specification/client_server_api.rst
View file

@ -1246,6 +1246,9 @@ have to wait in milliseconds before they can try again.
.. |/events| replace:: ``/events``
.. _/events: #get-matrix-client-%CLIENT_MAJOR_VERSION%-events
.. |/createRoom| replace:: ``/createRoom``
.. _/createRoom: #post-matrix-client-%CLIENT_MAJOR_VERSION%-createroom
.. |/rooms/<room_id>/initialSync| replace:: ``/rooms/<room_id>/initialSync``
.. _/rooms/<room_id>/initialSync: #get-matrix-client-%CLIENT_MAJOR_VERSION%-rooms-roomid-initialsync

6
specification/modules/dm.rst
View file

@ -42,14 +42,14 @@ may for example, prompt the user, ignore the flag altogether. To do this, it
stores this event in account data using the ``account_data`` API: see `Client
Config`_.
The inviter's client should set the ``is_direct`` flag to ``createRoom``
(`Creation`_) whenever the flow the user has followed is one where their
The inviter's client should set the ``is_direct`` flag to .. |/createRoom|_
whenever the flow the user has followed is one where their
intention is to speak directly with another person, as opposed to bringing that
person in to a shared room. For example, clicking on, 'Start Chat' beside a
person's profile picture would imply the ``is_direct`` flag should be set.
Server behaviour
----------------
When the ``is_direct`` flag is given to ``createRoom`` (`Creation`_), the home
When the ``is_direct`` flag is given to .. |/createRoom|_, the home
server must set the ``is_direct`` flag in the invite member event for any users
invited in the ``createRoom`` call.