Allow renaming and adding user ranks.
For our channel on our Cytube install, we'd like to add a new rank that's lower than moderator called "Broadcaster" that can modify the playlist, but nothing more.
Possibly, but it would require a fair bit of work. I'll think about the best way of doing this.
Shouldn't this be what the Rank numbers should allow? I don't understand the reason for ranks 3-9 because they're all treated as administrators currently.
I don't understand the reason for ranks 3-9 because they're all treated as administrators currently.
I kinda agree with that, it is large gap.
The difficulty isn't so much in re-allocating ranks, it's in migrating existing ranks. How do I re-scale the ranks for people who have used 3-9 as different seniority for admins?
I suppose I could just double it and make 2-10 moderator and 11-20 admin, but that might create more confusion.
Maybe you could make it so there's a textarea in the channel options that lists all the ranks, like "Broadcaster,VIP,Moderator,Technical Administrator,Administrator,Super Administrator" Additionally, being able to specify the color of ranks or add an icon similar to the afk or leader icons for certain usergroups would be useful for differentiating between technical administrators and moderating administrators.
On Sat, Aug 10, 2013 at 10:35 PM, Calvin Montgomery < [email protected]> wrote:
The difficulty isn't so much in re-allocating ranks, it's in migrating existing ranks. How do I re-scale the ranks for people who have used 3-9 as different seniority for admins?
I suppose I could just double it and make 2-10 moderator and 11-20 admin, but that might create more confusion.
— Reply to this email directly or view it on GitHubhttps://github.com/calzoneman/sync/issues/252#issuecomment-22451274 .
How do I re-scale the ranks for people who have used 3-9 as different seniority for admins?
Marking seniority in that way treats the ranks as vanity flags when their permissions are effectively all the same. I don't think permission ranks are the place for superfluous flags.
As for re-scaling, I would edit the user database to change all the ranks of users with a 4-9 rank to 3, change the channel owner's rank from 10 to 4, and adjust the ranges of numbers to which the "Administrator" title corresponds from 3-10 to 3-4. Then, the ranks would more clearly equate to their permissions. Once that's done, additional ranks could be coded.
The main trouble I'm seeing with that, however, would be that a server admin would have to run a converter script or edit their database manually before going live after their next pull from git.
@PseudonymRS CyTube just isn't built to support custom ranks right now. I'll consider it for the future but it's not top priority
@ipatjolvur The rank 10 for channel founder was established arbitrarily, in the hopes that I could reserve space for future expansion of ranks. Of course now it is clear that was probably not the best course of action but I have to work with it and determine the best case of moving forward.
You've probably already considered this, but I'll put it out there anyway:
Another course would be to convert numerical ranks to enumerated ranks. Then, you could control the corresponding numbers in the code while users and server admins would only see the text-based enumerated ranks. The addition of new ranks could theoretically then be seamless when updating installations.
Have there been any recent thoughts on custom ranks? My server has been asking for an emote role below moderator, so at first I tried a Rank=1.3 before thinking to first check what the db stores it as. Currently I was planning on just removing Owner and giving the others a bump everywhere in the codebase, but if there's another role requested then... yeah another role bump.
I realize it may be the case that custom roles are not on y'alls radar at the moment, but have there there been any discussions documenting a general direction roles are headed? I'll probably just do the global emote rank bump for the time being (as I forsee per-channel custom ranks actually being pretty difficult, nevermind the migration would likely break your users existing scripts), but if I get a second request I'd like to help contribute to whatever direction is decided.
Thanks
I'd like to move away from numeric ranks and towards a role based system instead. The strict numeric hierarchy is too rigid for how people actually end up using the permission system in practice (and as you've discovered, it becomes annoying to subdivide). There could be some mapping of "default roles" to existing numeric ranks to facilitate the transition.
I suppose you tried 1.3 by seeing leader=1.5 which was already a hack to work around this but in the leader case it isn't persisted.
With all that said, I haven't actually planned to work on this or concretely specified the proposal.