From f9c9fce1ad9389e6d161c40063b6aa18e13917d6 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Tue, 18 May 2021 13:04:11 -0400 Subject: [PATCH] Deprecate verifications that don't begin with a request. --- content/client-server-api/modules/end_to_end_encryption.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md index bbacad6e..cbd4f161 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -528,7 +528,9 @@ method, then the verification should be cancelled with a `code` of `m.unexpected_message`. An `m.key.verification.start` message can also be sent independently of any -request, specifying the verification method to use. +request, specifying the verification method to use. This behaviour is +deprecated, and new clients should not begin verifications in this way. +However, clients should handle such verifications started by other clients. Individual verification methods may add additional steps, events, and properties to the verification messages. Event types for methods defined