From 7cde3193e535aa3510fc008fb8ce55617815a194 Mon Sep 17 00:00:00 2001 From: manuroe Date: Thu, 7 Feb 2019 10:29:30 +0100 Subject: [PATCH] Key backup: Explain `hash` better --- proposals/1219-storing-megolm-keys-serverside.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/proposals/1219-storing-megolm-keys-serverside.md b/proposals/1219-storing-megolm-keys-serverside.md index 22e57968..069021c8 100644 --- a/proposals/1219-storing-megolm-keys-serverside.md +++ b/proposals/1219-storing-megolm-keys-serverside.md @@ -172,7 +172,10 @@ On success, returns a JSON object with keys: - `auth_data` (object): Required. Same as in the body parameters for `POST /room_keys/version`. - `version` (string): Required. The backup version. -- `hash` (string): Required. A hash value representing stored keys. +- `hash` (string): Required. The hash value which is an opaque string + representing stored keys in the backup. Client can compare it with the `hash` + value they received in the response of their last key storage request. + If not equal, another matrix client pushed new keys to the backup. - `count` (number): Required. The number of keys stored in the backup. Error codes: @@ -243,7 +246,8 @@ Body parameters: On success, returns a JSON object with keys: -- `hash` (string): Required. The new hash value representing stored keys. +- `hash` (string): Required. The new hash value representing stored keys. See +`GET /room_keys/version/{version}` for more details. Error codes: