| 3 | | Any ideas what you'd like to call the parameter? |
| | 3 | It's kind of a tricky concept. 'Visibility' currently seems to only apply to public groups (as mentioned above, setting visibility to "public" for a private or hidden group has no result). |
| | 4 | |
| | 5 | Public group |
| | 6 | visibility => public | non-members can view |
| | 7 | visibility => private | group members only |
| | 8 | |
| | 9 | Private or hidden groups |
| | 10 | visibility => public | no possible audience |
| | 11 | visibility => private | group members only |
| | 12 | |
| | 13 | Do we need to add a new parameter or expand the visibility parameter we have? Would it make more sense to have two parameters, one that applies to public group situations and one that applies to private groups? (I'm throwing out hidden groups since they're implicitly private.) I can imagine plugins that should be: |
| | 14 | |
| | 15 | • visible to every visitor, public or private group |
| | 16 | • visible to logged-in visitors, public or private group |
| | 17 | • visible to group members only, public or private group |
| | 18 | • visibility should reflect group visibility (public for public groups, group members only for private groups) |
| | 19 | |
| | 20 | I'm sort of thinking that two parameters has a nice symmetry: |
| | 21 | 'public_group_visibility' => [anyone, logged-in, group-members, group-admins] |
| | 22 | 'private_group_visibility' => [anyone, logged-in, group-members, group-admins] |
| | 23 | |
| | 24 | Privacy is always hard, and it's easy to come up with overly complicated schemes. Thanks for considering this problem. |