Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2025-12-28 19:48:37 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

remove 'one big event' proposal

Browse source
This commit is contained in:
Richard van der Hoff 2020-10-20 12:00:53 +01:00
parent 417501d8cc
commit 96cd76c868
1 changed files with 3 additions and 36 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -35,42 +35,9 @@ Represent groups by rooms rather than a custom first-class entity.
We reserve aliases which begin with a `+` to represent groups - e.g. the room
for group `+test:example.com` is `#+test:example.com`.
We introduce a `m.room.groups` state event which defines how a room should
behave as a group - i.e. the rooms which it groups together, and any subgroups
nested within it.
```json
{
"type": "m.room.groups",
"contents": {
"rooms": [
{
"room": "#room1:example.com",
},
{
"room": "#room2:example.com",
"autojoin": true
},
{
"room": "#room3:example.com",
},
],
"subgroups": [
{
"group": "+something:example.com",
},
{
"group": "+otherthing:example.com",
},
]
},
}
```
XXX: alternatively, perhaps all the rooms and subgroups should be their own
state event with a unique state key, ensuring that this can scale to large
groups and doesn't have to be edited atomically. A key like `present: true`
would be needed to distinguish from a deleted state event. Something like:
We introduce `m.room.group` and `m.room.subgroup` events which define the rooms
and subgroups within the group. A `present: true` key is included to
distinguish from a deleted state event. Something like:
```json
{