drop the recommendation that requests highlight the user
This commit is contained in:
parent
7469198d8b
commit
ab3ed738e4
1 changed files with 3 additions and 5 deletions
|
@ -34,11 +34,9 @@ following properties in its contents:
|
||||||
|
|
||||||
- `body`: a fallback message to alert users that their client does not support
|
- `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
|
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
|
to verify keys. For example, "Alice is requesting to verify keys with you.
|
||||||
trigger a notification so that Bob's client will highlight the room for him,
|
However, your client does not support this method, so you will need to use
|
||||||
making it easier for him to find it. For example, "@bob:example.com: Alice
|
the legacy method of key verification."
|
||||||
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
|
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
|
and instead present the user with an interface to accept or reject the key
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue