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

spaces are *primarily* referred to by their room ID.

Browse source
This commit is contained in:
Richard van der Hoff 2021-03-17 13:27:57 +00:00
parent acdb6f1c3d
commit 2e6d7d1c54
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -37,14 +37,14 @@ unspecified.
Each space is represented by its own room, known as a "space-room". The rooms Each space is represented by its own room, known as a "space-room". The rooms
within the space are determined by state events within the space-room. within the space are determined by state events within the space-room.
Spaces are referred to primarily by their alias, for example
`#foo:matrix.org`.
Space-rooms are distinguished from regular messaging rooms by the presence of a Space-rooms are distinguished from regular messaging rooms by the presence of a
`type: m.space` property in the `m.room.create` event. This allows clients to `type: m.space` property in the `m.room.create` event. This allows clients to
offer slightly customised user experience depending on the purpose of the offer slightly customised user experience depending on the purpose of the
room. Currently, no server-side behaviour is expected to depend on this property. room. Currently, no server-side behaviour is expected to depend on this property.
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.
Space-rooms may have `m.room.name` and `m.room.topic` state events in the same Space-rooms may have `m.room.name` and `m.room.topic` state events in the same
way as a normal room. way as a normal room.