|
|
|
@ -39,10 +39,9 @@ Client behaviour
|
|
|
|
|
The invitee's client may use the ``is_direct`` flag in `m.room.member`_ to
|
|
|
|
|
automatically mark the room as a direct message but this is not required: it
|
|
|
|
|
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`_.
|
|
|
|
|
stores this event in account data using the |/user/<user_id>/account_data/<type>|_ API.
|
|
|
|
|
|
|
|
|
|
The inviter's client should set the ``is_direct`` flag to .. |/createRoom|_
|
|
|
|
|
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
|
|
|
|
@ -50,6 +49,6 @@ person's profile picture would imply the ``is_direct`` flag should be set.
|
|
|
|
|
|
|
|
|
|
Server behaviour
|
|
|
|
|
----------------
|
|
|
|
|
When the ``is_direct`` flag is given to .. |/createRoom|_, 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.
|
|
|
|
|