From a514485bcb733fb58847872a2ed81723c015b224 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Tue, 5 Nov 2019 16:22:45 -0500 Subject: [PATCH] add note about displaying other events --- proposals/2241-e2e-verification-in-dms.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/proposals/2241-e2e-verification-in-dms.md b/proposals/2241-e2e-verification-in-dms.md index a29d7703..e3d7239f 100644 --- a/proposals/2241-e2e-verification-in-dms.md +++ b/proposals/2241-e2e-verification-in-dms.md @@ -80,6 +80,10 @@ client belongs to, and what state the verification is in. For example: waiting for the request to be accepted, and the sending user's other clients can indicate the that a request was initiated on a different device. +Clients may choose to display or not to display events of any other type that +reference the original request event; but it must not have any effect on the +verification itself. + #### Accepting a key verification To accept a key verification, Bob will send an `m.key.verification.start` event