MSC4287: Sharing key backup preference between clients (#4287)
* First draft of shared-key-backup-preference
* Rename to reflect MSC number
* Update MSC number in title
* Small fixes and corrections
* Mention the weird unstable prefix
* Note that the security problem is less if clients make the setting visible
* Fix wording of 'not perform key backup'
* Improve wording around turning on key backups
* Note that clients should notice when key backup is deleted
* Note that servers can delete key backups already
* Clarify that this only applies to clients that support key backup
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
* Fix extra JSON in account_data response.
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
* Note that clients don't have to monitor account data
* Fix typo
* Clarify the this only applies to client supporting encryption and key backup
Co-authored-by: Travis Ralston <travisr@matrix.org>
* Clarify that we are not requiring monitoring of the setting at all times.
Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>
* Allow clients to consider the setting value as they wish, rather than taking it as gospel
* Note that m. in the unstable prefix was a mistake
* Link to a specific spec version
Co-authored-by: Travis Ralston <travisr@matrix.org>
* Clarify how we can mitigate malicious server control of the setting
* Avoid EITHER and OR by using MAY as suggested by @Johennes
* Make sure we update the property if the client updates it
* Revert "Make sure we update the property if the client updates it"
This is a substantive change, which should not be applied during FCP, so reverting it.
This reverts commit 395b98ac3049fc88b7021436630f61c17c4c2310.
---------
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Co-authored-by: Travis Ralston <travisr@matrix.org>
Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>