From 96b6fb0129131e7adf6bc0c0c9c0dc57f91d7f2e Mon Sep 17 00:00:00 2001 From: David Baker Date: Thu, 6 Oct 2016 11:16:56 +0100 Subject: [PATCH] 'In the m.room.member' event --- specification/modules/dm.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/specification/modules/dm.rst b/specification/modules/dm.rst index 26c5d85a..f46a01a5 100644 --- a/specification/modules/dm.rst +++ b/specification/modules/dm.rst @@ -36,10 +36,11 @@ Events 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 |/user//account_data/|_ API. +The invitee's client may use the ``is_direct`` flag in the `m.room.member`_ +event 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 +|/user//account_data/|_ API. The inviter's client should set the ``is_direct`` flag to |/createRoom|_ whenever the flow the user has followed is one where their