From 1f1e3c9a0f1574eaa5a589c60e5aba09b2d4822b Mon Sep 17 00:00:00 2001 From: Richard van der Hoff Date: Mon, 16 Nov 2020 11:50:17 +0000 Subject: [PATCH] MSC1840 is in --- proposals/1772-groups-as-rooms.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/proposals/1772-groups-as-rooms.md b/proposals/1772-groups-as-rooms.md index b683011c..452ca131 100644 --- a/proposals/1772-groups-as-rooms.md +++ b/proposals/1772-groups-as-rooms.md @@ -41,8 +41,9 @@ Spaces are referred to primarily by their alias, for example Space-rooms are distinguished from regular messaging rooms by the `m.room.type` of `m.space` (see -[MSC1840](https://github.com/matrix-org/matrix-doc/pull/1840)). XXX nobody has -convinced me this is actually required. +[MSC1840](https://github.com/matrix-org/matrix-doc/pull/1840)). This allows +clients to offer slightly customised user experience depending on the purpose +of the room. Space-rooms may have `m.room.name` and `m.room.topic` state events in the same way as a normal room. @@ -590,8 +591,8 @@ child rooms? Seems to have some of the same problems as inheriting PLs. ## Dependencies - * (possibly?) [MSC1840](https://github.com/matrix-org/matrix-doc/pull/1840) - for room types. + * [MSC1840](https://github.com/matrix-org/matrix-doc/pull/1840) for room + types. * [MSC2753](https://github.com/matrix-org/matrix-doc/issues/2753) for effective peeking over the C/S API. @@ -638,6 +639,7 @@ development: Proposed final identifier | Purpose | Development identifier ------------------------------- | ------- | ---- +`m.space` | room type | `org.matrix.msc1772.space` `m.space.child` | event type | `org.matrix.msc1772.space.child` `m.space.parent` | event type | `org.matrix.msc1772.space.parent` `m.room.power_level_mappings` | event type | `org.matrix.msc1772.room.power_level_mappings`