From a709671d032f047b5608aa6588f25a4b936a86ab Mon Sep 17 00:00:00 2001 From: Matthew Hodgson Date: Thu, 14 Jan 2021 12:55:20 +0000 Subject: [PATCH] tie break on multiple parents --- proposals/1772-groups-as-rooms.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/proposals/1772-groups-as-rooms.md b/proposals/1772-groups-as-rooms.md index 8ab2f27d9..fa91c45c9 100644 --- a/proposals/1772-groups-as-rooms.md +++ b/proposals/1772-groups-as-rooms.md @@ -148,8 +148,11 @@ relationship can be expressed in one of two ways: `canonical` determines whether this is the main parent for the space. When a user joins a room with a canonical parent, clients may switch to view - the room in the context of that parent space, peeking into it in order to - find other rooms and group them together. + the room in the context of that space, peeking into it in order to find + other rooms and group them together. In practice, well behaved rooms + should only have one `canonical` parent, but given this is not enforced: + if multiple are present the client should select the one with the lowest + room ID, as determined via a lexicographic utf-8 ordering. To avoid abuse where a room admin falsely claims that a room is part of a space that it should not be, clients could ignore such `m.space.parent`