Clarify that verifications without a request only happens over to-device (#1345)
This commit is contained in:
parent
1e393fbf92
commit
64922771d4
2 changed files with 3 additions and 1 deletions
|
@ -551,7 +551,8 @@ then the device IDs should be compared instead. If the two
|
|||
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
|
||||
When verifying using to-device messages, an `m.key.verification.start`
|
||||
message can also be sent independently of any
|
||||
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.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue