wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Merge pull request #3185 from matrix-org/travis/clarify/1772

Browse source 
Mention expected client behaviour of unknown types on MSC1772
This commit is contained in:
Travis Ralston 2021-05-10 11:50:43 -06:00 • committed by Richard van der Hoff
commit 71a0f9f9a2
1 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -45,7 +45,11 @@ depending on the purpose of the room. Currently, no server-side behaviour is
expected to depend on this property. A `type` property on the `m.room.create` expected to depend on this property. A `type` property on the `m.room.create`
event is used to ensure that a room cannot change between being a space-room event is used to ensure that a room cannot change between being a space-room
and a non-space room. For more information, see the "Rejected Alternatives" and a non-space room. For more information, see the "Rejected Alternatives"
section below. section below. Additionally, no client behaviour is recommended for handling
unknown room types given the potential for legacy data: clients are free to
make their own decisions about hiding unknown room types from users, though
should note that a future conversation-like type (for example) might be
introduced and could be considered "unknown" by older versions of their client.
As with regular rooms, public spaces are expected to have an alias, for example As with regular rooms, public spaces are expected to have an alias, for example
`#foo:matrix.org`, which can be used to refer to the space. `#foo:matrix.org`, which can be used to refer to the space.