Users in special groups: can they also see files of "generic" userlist?
Submitted by monsieurX on Mon, 04/23/2012 - 10:54
Forums:
Well, I really wonder if they can.
Supposed I'm an avid sharer of porn. (In reality, I'm not at all, but to understand the logic, you'll see it makes lots of sense. :D)
- All porn stuff be userlist-only, but NOT assigned to any special group.
- Now let's assume I have 1 group of users, called "friends", who are not into porn at all. They don't even want to see that.
But as my assumption is (and the way slskQt is coded/conceived) it ought to be like that, i. e. that they can see the files assigned to their special group *PLUS* the porn.
I'm assuming that since there is no way of assigning a user to a special group BUT preventing him from seeing files assigned to "userlist root group".
- Log in to post comments
Your assumption is correct,
Your assumption is correct, users belonging to a particular group will see all shares available to that group as well as to the userlist in general. Of course, there's no limit to the number of groups a user can be in. If you wanted to make sure only people who are into porn will see those files, following your logic, you could always create a group just for that and tag them as such.
Cheers, Nir
Yes. But I think it would
Yes. But I think it would also come in handy to have an option that users belonging to one special group can ONLY see that group and nothing else.
Think about musical styles!
Supposing that you are an enthusiast of both cheesy bubble-gum pop as well as earthy funk. Most likely you'd want to prevent your funky groovin' fellows from seeing files from Lady Gaga, Britney and Co! So with my suggestion, you could add them to the "funkyfellas" group and they wouldn't even know you had such cheesy stuff! =D
"You can do that," you'll say. "Just by creating another group for the cheesy stuff and adding each user to this group EXCEPT for said funk-lovin' guys."
True, but now let's assume this userlist be an import from Slsk 156 and already got 70 users in! A lovely task having to add each single user to the "cheesypop" group for sure...
However, the second method is more effective: you leave your cheesy pop stuff as USERLIST and then, for the funk-lovin' guys, add these to the "funkyfellas" group *BUT* you do not let them see the files for generic userlist ("root group").
Such as ...
[ ] Users belonging to this group can also see files from generic userlist (i. e. files not assigned to any groups)
What do you think about it?
(In my (made-up) example above, this would make it no longer necessary adding each random "incoming" user to the "porn" group and explicitly taking care to have my "friends" not in that group, which would be much more effort in hindsight)