mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-03-13 06:54:10 +01:00
Defer a TODO to the future.
This commit is contained in:
parent
e7041525bf
commit
6d007e83ca
|
|
@ -72,8 +72,6 @@ exception that `invite_state` sent along with invites should be amended to
|
||||||
include the `m.room.create` event, to allow clients to discern whether an
|
include the `m.room.create` event, to allow clients to discern whether an
|
||||||
invite is to a space-room or not.
|
invite is to a space-room or not.
|
||||||
|
|
||||||
XXX: Should we also include a MSC2946 summary of the space in the invite too?
|
|
||||||
|
|
||||||
### Relationship between rooms and spaces
|
### Relationship between rooms and spaces
|
||||||
|
|
||||||
The intention is that rooms and spaces form a hierarchy, which clients can use
|
The intention is that rooms and spaces form a hierarchy, which clients can use
|
||||||
|
|
@ -295,8 +293,11 @@ One way this might be implemented is:
|
||||||
* [MSC2946](https://github.com/matrix-org/matrix-doc/issues/2946): Spaces
|
* [MSC2946](https://github.com/matrix-org/matrix-doc/issues/2946): Spaces
|
||||||
Summary API.
|
Summary API.
|
||||||
|
|
||||||
* [MSC2962](https://github.com/matrix-org/matrix-doc/issues/2962): Group
|
* [MSC2962](https://github.com/matrix-org/matrix-doc/issues/2962): Managing
|
||||||
access control via Spaces.
|
power levels via Spaces.
|
||||||
|
|
||||||
|
* [MSC3083](https://github.com/matrix-org/matrix-doc/issues/3083): Restricting
|
||||||
|
room membership based on space membership.
|
||||||
|
|
||||||
* [MSC2753](https://github.com/matrix-org/matrix-doc/issues/2753) for
|
* [MSC2753](https://github.com/matrix-org/matrix-doc/issues/2753) for
|
||||||
effective peeking over the C/S API.
|
effective peeking over the C/S API.
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue