From 22f7eaae0c0595ef8d9a57ee9ee80cca920932d4 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Tue, 3 Dec 2019 22:03:21 -0500 Subject: [PATCH] add example --- proposals/2366-key-verification-accept.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/proposals/2366-key-verification-accept.md b/proposals/2366-key-verification-accept.md index 0fded02eb..9dd7a401b 100644 --- a/proposals/2366-key-verification-accept.md +++ b/proposals/2366-key-verification-accept.md @@ -7,6 +7,16 @@ experienced users through the verification process, especially if they are not verifying in-person, but are using a trusted but remote channel of verification (such as telephone or video conference). +As an example, let us say that Alice is an experienced Matrix user and is +introducing Bob to the wonders of federated communications. Alice wants to +verify keys with Bob, so she clicks on the "Verify" button in her client on +Bob's profile (which sends a `m.key.verification.request` message to Bob). +Bob's device receives the verification request and prompts Bob to accept the +verification request. At this point, under the current framework, Bob is +responsible for choosing the verification method to use. However, with this +proposal, Bob would be able to just accept the verification request without +choosing a method, and allow Alice to choose the verification method. + ## Proposal A new event type is added to the key verification framework: