From 09b0848cc85480f659fa17d113cba42b560691ce Mon Sep 17 00:00:00 2001 From: Kegan Dougal Date: Mon, 18 Jan 2021 15:54:51 +0000 Subject: [PATCH] Add 'version' field --- proposals/2946-spaces-summary.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/proposals/2946-spaces-summary.md b/proposals/2946-spaces-summary.md index 94135d94b..773a8fcef 100644 --- a/proposals/2946-spaces-summary.md +++ b/proposals/2946-spaces-summary.md @@ -225,9 +225,10 @@ Justifications for the request API shape are the same as before with one excepti the server should not return node information under `rooms` nor should it return _any state events in this room_. NB: state events which _point to_ this room should still be included. -The response body remains unchanged from the client format. Servers are unable to verify the auth chain of the returned events -as they are typically not joined to the rooms returned. Servers MUST NOT persist these events in any potential room DAG that may -be created if the server were to join the room. +The response body remains unchanged from the client format with the exception of a `version` field added to each room object under `rooms`. +Servers MUST use this field to determine how to decode the events in `events`. If the room version is unknown, the server may ignore these +events/rooms. Servers are unable to verify the auth chain of the returned events as they are typically not joined to the rooms returned. +Servers MUST NOT persist these events in any potential room DAG that may be created if the server were to join the room. Sending server behaviour: - When walking the spaces graph, if the server is not joined to a given room, remember the `via` server names and the room ID.