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

md

Browse source
This commit is contained in:
Matthew Hodgson 2019-01-03 18:55:58 +00:00
parent 346f7ac113
commit 1e81fbd2d8
1 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -105,11 +105,12 @@ it may be overengineered.
Instead, the common case is wanting to define a group where some users are
publicly visible as members, and others are not. This is what the current use
cases require today. A simple way of achieving would be to create a subgroup
for the private members - e.g. have +sensitive:matrix.org and +sensitive-
private:matrix.org. The membership of `+sensitive-private:matrix.org` is set up
with `m.room.join_rules` to not to allow peeking; you have to be joined to see
the members, and users who don't want to be seen by the public to be member of
the group are added to the subgroup.
for the private members - e.g. have `+sensitive:matrix.org` and
`+sensitive-private:matrix.org`. The membership of
`+sensitive-private:matrix.org` is set up with `m.room.join_rules` to not to
allow peeking; you have to be joined to see the members, and users who don't
want to be seen by the public to be member of the group are added to the
subgroup.
XXX: is there a use case today for having a group where users are unaware of the
other users' membership? e.g. if I am a member of `+scandalous:matrix.org`