From d9815af4cc8ad4025f90d08e0ed3e5b142e94418 Mon Sep 17 00:00:00 2001 From: Sorunome Date: Mon, 30 Aug 2021 16:24:33 +0200 Subject: [PATCH] MSC2582: Remove mimetype from EncryptedFile object (#2582) * add proposal * Update proposals/2582-remove-mimetype-from-encrypted-file.md Co-authored-by: Hubert Chathi * Update proposals/2582-remove-mimetype-from-encrypted-file.md Co-authored-by: Hubert Chathi Co-authored-by: Hubert Chathi --- .../2582-remove-mimetype-from-encrypted-file.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 proposals/2582-remove-mimetype-from-encrypted-file.md diff --git a/proposals/2582-remove-mimetype-from-encrypted-file.md b/proposals/2582-remove-mimetype-from-encrypted-file.md new file mode 100644 index 00000000000..3b1f83c7a06 --- /dev/null +++ b/proposals/2582-remove-mimetype-from-encrypted-file.md @@ -0,0 +1,12 @@ +# Remove `mimetype` from `EncryptedFile` object + + +## Proposal +The example in the spec currently lists `mimetype` in the [examples for `EncryptedFile`](https://matrix.org/docs/spec/client_server/r0.6.1#extensions-to-m-message-msgtypes) but not in +the object definition. As that is duplicate information of the `info` block of file events, the +mimetype should just be removed alltogether. + + +## Potential issues +Some clients might depend on this. However, as of August 2021, all known clients have +been confirmed to not use this.