Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-01-01 05:28:38 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse source 
Co-authored-by: Matthew Hodgson <matthew@matrix.org>
This commit is contained in:
Richard van der Hoff 2020-10-30 11:16:32 +00:00 committed by GitHub
parent 15f34e5be9
commit e746aa3aad
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
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

@ -105,7 +105,7 @@ upgrades would need considering.
XXX Rooms also need to be able to advertise related spaces, so that users can
discover other, related, rooms.
XXX We also want to be have "secret" rooms within a heirarchy: do this with
XXX We also want to be have "secret" rooms within a hierarchy: do this with
either a "parent" state in the child, or possibly by hashing the room id?
Space-rooms may have `m.room.name` and `m.room.topic` state events in the same
@ -228,7 +228,7 @@ mechanics of propagating changes into real `m.room.power_levels` events.
Several options:
* Push-based:
* Push-based options:
* We require any user who is an admin in the space (ie, anyone who has
permission to change the access rights in the space) to also be admins
@ -263,7 +263,7 @@ Several options:
space, without having any particular control in that group. (XXX: Is that
actually a useful feature, at least as far as PLs are concerned?)
Problem: What do you do if the admin who sets ip the PL relationship
Problem: What do you do if the admin who sets up the PL relationship
disappears? Again, either the humans have to step in and create a new
admin, or maybe we can have multiple admins with random backoff?