From 8fc472c13c34d8112301c0549f690b3348de3ee9 Mon Sep 17 00:00:00 2001 From: Kegan Dougal Date: Mon, 12 Jan 2015 13:29:48 +0000 Subject: [PATCH] Clarify rejected events better. --- drafts/general_api.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/drafts/general_api.rst b/drafts/general_api.rst index 0d5fde0c..50e55df2 100644 --- a/drafts/general_api.rst +++ b/drafts/general_api.rst @@ -184,7 +184,9 @@ Message Events Ordering Notes: after. Rejected events: - A home server may find out via federation that it should not have accepted - an event (e.g. to send a message/state event in a room). + an event (e.g. to send a message/state event in a room). For example, it may + send an event to another home server and receive an auth event stating + that the event should not have been sent. - If this happens, the home server will send a ``m.room.redaction`` for the event in question. This will be a local server event (not shared with other servers). @@ -551,8 +553,8 @@ Notes: - This is represented on the event stream as an event lacking a ``content`` key (for symmetry with ``prev_content``) -Patching power levels ``[Draft`` -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Patching power levels ``[Draft]`` +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Inputs: - Room ID - Key to update