From 3b35e95630c361b310d9586ef18c9ecf0535b984 Mon Sep 17 00:00:00 2001 From: Kegsay Date: Mon, 19 Jan 2015 17:37:23 +0000 Subject: [PATCH] Tweaks based on feedback --- drafts/general_api.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drafts/general_api.rst b/drafts/general_api.rst index 067abdbd..894deac0 100644 --- a/drafts/general_api.rst +++ b/drafts/general_api.rst @@ -449,8 +449,8 @@ resulting in missing information on the receiving home server. For federation, these problems can be resolved by sending the ``m.room.member`` event as they are in v1 (with ``displayname`` and -``avatar_url`` in the ``content``). They *have* to be sent in the -``content`` as this information needs to be signed. The receiving home +``avatar_url`` in the ``content``). These keys need to be signed so +they cannot be in the ``unsigned`` part of the event. The receiving home server will then extract these keys and create a server-generated ``m.room.member.profile`` event. To avoid confusion with duplicate information, the ``avatar_url`` and ``displayname`` keys should be