Phoenix25
commented
10 years ago Hmm. No 4 Only tagged people can see them? That.. is counter-productive and confusing no? if people belonging to the given wall can't see what's going on. Considering No.1, No.2 & No.3, i can stack them as the domains continuously increase form 3 to 1 Nos 5 & 6 are a completely different thing. i check for access and then make another option for them to unsubscribe/subscrbe.
On Sat, May 31, 2014 at 4:15 AM, AbdealiJK notifications@github.com wrote:
@Phoenix25 https://github.com/Phoenix25 The post level is_public thing is not enough..
What we need is something like this :
On the right corner, make a dropdown box. When clicked, it gives something like :
Access rights : (for person who created or to whose wall it is)
- Let all users see this post
- Only members of this wall + tagged members can see this post
- Only members of this wall can see this post
- Only tagged members can see this post
- I don't want to see this (remove user from accessing this post) Notifications :
- Notify me of any further updates related to this post (if already notified, give option to de-notify)
Now, when we do this ... all access rights filters will change. Make a new branch. This will take quite a lot of testing to figure out.
— Reply to this email directly or view it on GitHub https://github.com/The-WebOps-Club/fest-api/issues/89.
AbdealiLoKo
@Phoenix25 The post level is_public thing is not enough..
What we need is something like this :
On the right corner, make a dropdown box. When clicked, it gives something like :
Access rights : (for person who created or to whose wall it is)
Now, when we do this ... all access rights filters will change. Make a new branch. This will take quite a lot of testing to figure out.