From 302d5d87b4138704538f60195878451924561eb4 Mon Sep 17 00:00:00 2001 From: Matthew Hodgson Date: Wed, 13 Jan 2021 17:29:43 +0000 Subject: [PATCH] clarify autojoin and mention 'suggested' rooms --- proposals/1772-groups-as-rooms.md | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/proposals/1772-groups-as-rooms.md b/proposals/1772-groups-as-rooms.md index d4285e6a..0d49dba4 100644 --- a/proposals/1772-groups-as-rooms.md +++ b/proposals/1772-groups-as-rooms.md @@ -183,16 +183,20 @@ available) to join whichever subset of it makes most sense for the client's UX. Obviously auto-joining can be a DoS vector, and we consider it to be antisocial -for a space to try to join its users to more than ~100 children. +for a space to try to autojoin its members to more than 100 children (in total). Clients could display the auto-joined children in the room list whenever the space appears in the list - thus helping users discover other rooms in a space -even if they're not joined to that space. - -XXX: I still think it's more common that a space admin will want users to know -that a child exists (by showing it in the room list), rather than force them to -actually join it. So this would be an `advertise` flag or something on the child. -Matthew to discuss with Nad... +even if they're not joined to that space. For instance, if you join +`#matrix:matrix.org`, your client could show that room in the context of its +parent space, with that space's autojoined children shown alongside it as +siblings. + +It may also be useful to have a way to "suggest" that members of a space +should join certain children (but without actually autojoining them) - to +advertise particular rooms more prominently than in the room directory. +However, this can be added in a later MSC if it's found to be needed in +practice. ### Long description