Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-02 17:54:09 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

add more justification for immutable room types

Browse source
This commit is contained in:
Matthew Hodgson 2021-04-29 21:02:12 +01:00
parent 37e04f72ae
commit 1e2ed52b7e
1 changed files with 8 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
proposals/1772-groups-as-rooms.md
View file

@ -359,10 +359,14 @@ None at present.
### Use a separate state event for type of room ### Use a separate state event for type of room
[MSC1840](https://github.com/matrix-org/matrix-doc/pull/1840) proposes the use [MSC1840](https://github.com/matrix-org/matrix-doc/pull/1840) proposes the use
of a separate `m.room.type` state event to distinguish different room of a separate `m.room.type` state event to distinguish different room types.
types. This implies that rooms can dynamically switch between being a Space, This implies that rooms can dynamically switch between being a Space, and
and being a regular non-Space room. That is not a usecase we consider useful, being a regular non-Space room. That is not a usecase we consider useful, and
and allowing it would impose significant complexity on client implementations. allowing it would impose significant complexity on client and server
implementations. Specifically, client and server implementations who store
spaces separately from rooms would have to support migrating back and forth
between them and dealing with the ambiguities of `room_id`s no longer pointing
to valid spaces, etc.
## Unstable prefix ## Unstable prefix