From adbe95259f596c42b9d2bf7c9cdf0582c6300492 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Tue, 20 Apr 2021 11:43:10 -0400 Subject: [PATCH] add link to relevant spec --- ...recate-starting-verifications-without-request.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/proposals/3122-deprecate-starting-verifications-without-request.md b/proposals/3122-deprecate-starting-verifications-without-request.md index 110f1377..9a00699b 100644 --- a/proposals/3122-deprecate-starting-verifications-without-request.md +++ b/proposals/3122-deprecate-starting-verifications-without-request.md @@ -1,10 +1,13 @@ # MSC3122: Deprecate starting key verifications without requesting first -Currently, the spec allows a device to begin a verification via to-device -messages by sending an `m.key.verification.start` event without first sending -or receiving an `m.key.verification.request` message. However, doing so does -not provide a good user experience, and allowing this adds unnecessary -complexity to implementations. +Currently, the [Key verification +framework](https://spec.matrix.org/unstable/client-server-api/#key-verification-framework) +allows a device to begin a verification via to-device messages by sending an +`m.key.verification.start` event without first sending or receiving an +`m.key.verification.request` message. (The last sentence of the 5th paragraph +of the Key verification framework in the unstable spec, as of the time of +writing.) However, doing so does not provide a good user experience, and +allowing this adds unnecessary complexity to implementations. We propose to deprecate allowing this behaviour.