How to make it so mods can't mute admins etc

How to do...

How to make it so mods can't mute admins etc

Postby Marz » Tue May 19, 2015 4:28 am

I was looking on the feature tracker seeing if mumble was ever going to get something like powerlevels for groups.

On this post: http://sourceforge.net/p/mumble/feature-requests/675/
Apparently it is already possible to make it so one group can't mute another group, but I can't figure out how. Is anyone able to explain this?
Marz
 
Posts: 12
Joined: Mon May 18, 2015 11:07 pm

Re: How to make it so mods can't mute admins etc

Postby kissaki » Sat May 23, 2015 7:11 am

I don’t think that’s possible.

Actually, I guess it’s *your* state (type of user you are) and your permission on the targets position (do you have permission to do that action in that channel?).
I don’t think there is a check whether you are allowed to do action on a user depending on *his* permission.
MumPI: Your Mumble Web Interface in PHP
User avatar
kissaki
Team member
Team member
 
Posts: 1289
Joined: Sat Jan 09, 2010 12:15 pm

Re: How to make it so mods can't mute admins etc

Postby Marz » Mon May 25, 2015 12:14 am

That is what I originally thought. A usergroup power level would be handy, I'm not sure why that feature request was rejected.
Marz
 
Posts: 12
Joined: Mon May 18, 2015 11:07 pm

Re: How to make it so mods can't mute admins etc

Postby Dongus_ » Tue Aug 11, 2015 7:54 pm

Yeah I would love this! There is this one guy who comes on our server, one guys little brother, and as a joke we where thinking about setting up so everybody else could mute him.
Dongus_
 
Posts: 1
Joined: Thu Aug 06, 2015 1:00 am

Re: How to make it so mods can't mute admins etc

Postby fwaggle » Tue Aug 11, 2015 11:44 pm

I think the FR was rejected because Mumble's ACL system is a complicated beast that's already extremely difficult to convey in a UI fashion anyway. Adding another variable into it (user/group levels) could just further lead to more confusion and unexpected edge cases.

Considering we have things like a couple rather nasty audio bugs, likely at least a couple of bugs upstream in Qt that affect us, at least one weird network issue, and a spontaneous database corruption in the client that no one can track down... Better to explicitly reject the feature requests that require a huge amount of engineering than to leave them sit in the tracker forever.

If someone wanted to take it upon themselves to implement this, complete with tests to show it works as expected, I would imagine the official project position is "patches welcome" but a feature request for something of this scope doesn't really make any sense, IMHO.
Full disclosure: I used to run a commercial Mumble host, and my opinions do not reflect the opinions of the Mumble project.
Avatar is stolen from here
User avatar
fwaggle
Team member
Team member
 
Posts: 217
Joined: Tue Oct 06, 2009 10:40 pm
Location: Australia


Return to Usage

Who is online

Users browsing this forum: No registered users and 2 guests

cron