From ab3ed738e4b49fec76f0aecca4b210bc7afe57f2 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Tue, 8 Oct 2019 16:27:53 -0400 Subject: [PATCH] drop the recommendation that requests highlight the user --- proposals/2241-e2e-verification-in-dms.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/proposals/2241-e2e-verification-in-dms.md b/proposals/2241-e2e-verification-in-dms.md index f049540c..9d53a290 100644 --- a/proposals/2241-e2e-verification-in-dms.md +++ b/proposals/2241-e2e-verification-in-dms.md @@ -34,11 +34,9 @@ following properties in its contents: - `body`: a fallback message to alert users that their client does not support the key verification framework, and that they should use a different method - to verify keys. The message should contain Bob's Matrix ID in order to - trigger a notification so that Bob's client will highlight the room for him, - making it easier for him to find it. For example, "@bob:example.com: Alice - is requesting to verify keys with you. However, your client does not support - this method, so you will need to use the legacy method of key verification." + to verify keys. For example, "Alice is requesting to verify keys with you. + However, your client does not support this method, so you will need to use + the legacy method of key verification." Clients that do support the key verification framework should hide the body and instead present the user with an interface to accept or reject the key