From 3f66ba713cf7fc9e05a6eacd864a032a3d57cdc7 Mon Sep 17 00:00:00 2001 From: David Baker Date: Wed, 5 Oct 2016 13:25:42 +0100 Subject: [PATCH] Reference m.room.member section --- 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 4785f5b17..32c3ebfa1 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 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`_. +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`_. 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