From b379c42e88fa9c2013a91a7a6991e865d08ba05a Mon Sep 17 00:00:00 2001 From: Patrick Cloke Date: Thu, 6 May 2021 12:34:08 -0400 Subject: [PATCH] Add context about why stripped events are returned. --- proposals/2946-spaces-summary.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/proposals/2946-spaces-summary.md b/proposals/2946-spaces-summary.md index 52bf574a1..d66aa7c28 100644 --- a/proposals/2946-spaces-summary.md +++ b/proposals/2946-spaces-summary.md @@ -106,7 +106,7 @@ Response fields: in [MSC1772](https://github.com/matrix-org/matrix-doc/pull/1772). * **`events`**: `m.space.child` events of the returned rooms. For each event, only the following fields are returned: `type`, `state_key`, `content`, `room_id`, - `sender`. + `sender`.[1](#f1) Errors: @@ -219,3 +219,10 @@ The client-server API will be: The server-server API will be: `/_matrix/federation/unstable/org.matrix.msc2946/spaces/{roomID}` + +## Footnotes + +[1]: The rationale for including stripped events here is to reduce +potential dataleaks (e.g. timestamps, `prev_content`, etc.) and to ensure that +clients do not treat any of this data as authoritative (e.g. if it came back +over federation). The data should not be persisted as actual events.[↩](#a1)