idno
ACLs don't work as expected when leaving groups
While trying to do this:
- Alice joins Group
- Alice creates Group content
- Alice leaves Group
- See my own content from Group
I encountered this error:
- Alice can no longer access anything she has created previously
Some other notes:
Now, I would expect that you should always be able to see content you have created... but is this true in all cases? Or is the fact that my group content is no longer available to me when I leave the expected behaviour.
Discuss.
/cc @benwerd
Give us some context, it'd also be really handy if you could tell us the contents of your version.known file
I'm wondering whether we need to mirror the owner/container model from e.g. elgg...
I strongly don't think people who have left a group should see anything from that group. I'm not sure what, eg, Facebook does here, but it would be worth looking into.
On Tue, Apr 3, 2018 at 3:06 AM, Marcus Povey [email protected] wrote:
I'm wondering whether we need to mirror the owner/container model from e.g. elgg...
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/idno/Known/issues/1832#issuecomment-378198188, or mute the thread https://github.com/notifications/unsubscribe-auth/AAmF6BgAwq90KIVYg9ljs9Bd_oG5WEX7ks5tk0mrgaJpZM4Od34a .
-- Ben Werdmuller http://goog_1933028737 werd.io | @benwerd https://twitter.com/benwerd
+1 (510) 283-3321
Group content yes, but what about your own stuff?
Perhaps it's an edge case, but for example if I was collaborating on something, or for example submitting coursework, I would be thinking this is "mine", but if it is shared with others via the group, it could become available as soon as I left that workgroup or the group dissolved.
Ignore what I said about owner/container, I was sleepy, but I think the owner should always have access...
I think the right answer is going to be “whatever is least confusing to a non-technical user”. I’m not sure what that is right now, but that’s why I’m suggesting looking at comparable behavior in something like Facebook - they will likely have done real user research on it.
On Thu, Apr 5, 2018 at 11:11 PM Marcus Povey [email protected] wrote:
https://github.com/idno/Known/issues/1832#issuecomment-379109915Group content yes, but what about your own stuff?
Perhaps it's an edge case, but for example if I was collaborating on something, or for example submitting coursework, I would be thinking this is "mine", but if it is shared with others via the group, it could become available as soon as I left that workgroup or the group dissolved.
Ignore what I said about owner/container, I was sleepy, but I think the owner should always have access...
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/idno/Known/issues/1832#issuecomment-379158127, or mute the thread https://github.com/notifications/unsubscribe-auth/AAmF6DJ1Vb7W6Ioz-TiV2m4L4TCIXjgmks5tlwb3gaJpZM4Od34a .
-- Ben Werdmuller http://goog_1933028737 werd.io | @benwerd https://twitter.com/benwerd
+1 (510) 283-3321
I'm thinking of a specific (and probably edge) case here which I can't really talk about, although you are familiar with, where group content appeared in a personal feed / folders as well as group. Under these circumstances where someone has their own portfolio + uses groups to share with others, it is definitely confusing when a user leaves the group and suddenly they can't access their work.
In a wider friendface style group, yes you're probably right, no access makes sense.
Since Known doesn't really have native group support I guess it doesn't really matter, I was more flagging that the current ACL model will be confusing in circumstances (which will crop up a lot in Edu) where someone works on something and uses a group to share with others.