Jasin 11 Posted June 24, 2014 Posted June 24, 2014 It seems mediabrowser has a blacklist way of access. Where if I add anything, all users have access and you have to go to each user to block access. Might be better to have a whitelist where they are denied by default and you give access. Also it would be nice to click on a library and see the user list where you could change access to the users there instead of having to go to each user. 3
Deathsquirrel 745 Posted June 24, 2014 Posted June 24, 2014 What's the use case? If you want the feature explaining why may be helpful. Without that info it's pretty easy to dismiss many feature requests as the user not taking advantage of the current controls. For example, you can setup users that have access to different libraries. You can setup users that have access to all libraries but are restricted by parental rating. In either of those scenarios a user will not necessarily get access to media as soon as you add it. If you explain how the existing tech doesn't meet your needs it helps the devs understand what you're trying to accomplish. They may not build what you ask for but may offer some other way, now or in the future, to accomplish that same goal.
Luke 42078 Posted June 24, 2014 Posted June 24, 2014 I think this is a valid request and could potentially happen, but we're not just going to flick the switch because there's poor usability involved. You guys will be happy, and others will be asking why they can't see anything. So while this might be a good idea, it's more or less held up until we can find time to rework the process of adding the content, so that you can choose up front who gets it and who doesn't.
Jasin 11 Posted June 24, 2014 Author Posted June 24, 2014 (edited) What's the use case? If you want the feature explaining why may be helpful. Without that info it's pretty easy to dismiss many feature requests as the user not taking advantage of the current controls. Very easy, Say I have 10 people with accounts. Including family members and kids. I could add an adult library (Or just stuff I don't want them to have access to) Then they all have instant access. If I forget, it can cause issues. I would rather add a library and then decide who gets access. I think this is a valid request and could potentially happen, but we're not just going to flick the switch because there's poor usability involved. You guys will be happy, and others will be asking why they can't see anything. So while this might be a good idea, it's more or less held up until we can find time to rework the process of adding the content, so that you can choose up front who gets it and who doesn't. Understandable but my 2nd suggestion would help this some. Once I am in the library seeing who has/does not have access. Edited June 24, 2014 by Jasin
Koleckai Silvestri 1154 Posted June 25, 2014 Posted June 25, 2014 The first suggested change has been suggested before. So far the developers feel the current method fits the needs of most users. I like your second idea. Would give a way to control access easier.
CBers 7450 Posted June 25, 2014 Posted June 25, 2014 As Wayne Luke says, many people have said the same. Hopefully your comment is the "straw that breaks the camels back".
Deathsquirrel 745 Posted June 25, 2014 Posted June 25, 2014 So the issue is that when a media folder is added it defaults to being available to all existing users? Don't know if it's worth solving, not my call, but I'd suggest the simplest method to solve it and address Luke's concern is for the tool that comes up when you click Add Media Folder to either have a checkbox for 'Add Media Folder to all Users' or to list all current users with check boxes that can be selected to add that folder to that user's account. If either option were added I'd suggest it default to adding the folder to all user accounts as that's the current behavior. 1
Koleckai Silvestri 1154 Posted June 25, 2014 Posted June 25, 2014 (edited) The biggest issue with defaulting to add to all users is it goes against all best security practices. Personally, I am not adverse to a link that adds permission to all existing users when you add a Media Folder or Channel. If this link isn't selected, no permissions should be added for non-admin users or a list of users with checkboxes should be supplied. When a new user is added, it should have no access not global access. These are my opinions though. I can work with the current scheme even though it is backward. Edited June 25, 2014 by Wayne Luke 3
Deathsquirrel 745 Posted June 25, 2014 Posted June 25, 2014 I expect relatively few people even want that sort of security. Most users are likely perfectly happy doing parental controls by rating and have very few user accounts to begin with. If that's correct then making the default to not add a media folder to all users will generate more postings from confused users than the reverse. Guess it comes down to the question of what percentage of MB3 admins are managing a bunch of user accounts that are all supposed to see different media folders and that regularly add new media folders. Before changing such a default from simple to complex I'd at least run a survey.
bigjohn 753 Posted June 25, 2014 Posted June 25, 2014 I agree with Wayne Luke, it is backward. I understand why it needs to be that way for the initial installation, and it makes sense for all media to be available to the initial admin user. Access to any media folder should be restricted by default for all other users. I had hundreds of items that did not have ratings, so using the ratings system can take a lot of work to get it right. There are a lot of movies that just do not have an official rating, for whatever reason. Besides, maybe I don't want to limit my parents by ratings, but don't particularly want to share certain collections with them either. I understand I can go in and remove access, but forgetting to remove access can have worse consequences than forgetting to grant access. 1
Koleckai Silvestri 1154 Posted June 25, 2014 Posted June 25, 2014 Any change definitely needs to be thought through. If the change is implemented, existing installations shouldn't be affected. Just inherit the permissions set up as they are. It should only affect new users and installations.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now