|
|
|
@ -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``
|
|
|
|
|
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.
|
|
|
|
|
The inviter's client should set the ``is_direct`` flag to ``createRoom``
|
|
|
|
|
(`Creation`_) 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``, the home server must
|
|
|
|
|
set the ``is_direct`` flag in the invite member event for any users invited
|
|
|
|
|
in the ``createRoom`` call.
|
|
|
|
|
When the ``is_direct`` flag is given to ``createRoom`` (`Creation`_), the home
|
|
|
|
|
server must set the ``is_direct`` flag in the invite member event for any users
|
|
|
|
|
invited in the ``createRoom`` call.
|
|
|
|
|