[02:39:17] blocked by DarkMatter, don't think this really needs a lock but eh [15:16:35] Non urgent question (may have asked before but honestly forgot) for counter vandalism friends, namely @Global Administrators and @Stewards, anyone have objections to me opening up a tech task to (eventually) fix the fact that global functionaries by default can’t edit local custom protection levels? [15:27:01] Asking here since it’s cvt and there’s no need for this to be in private [18:04:09] not an advanced global user rights person, but still volunteering every so often on CV, @pixldev that seems reasonable to me [18:07:02] Still appreciate feedback! (Also why I made a point to ask this on the public CVT channel instead of our internal channels, I'm starting to feel we volunteers have a bad habit of discussing things behind closed door that don't need to be) [18:07:49] yeah I feel you on this - still reasonable for that task to be made regardless [18:08:50] I asked our tech folks a bit about implementing, seems pretty simple in theory but I don't have much time to do it myself, and it almost certainly would be much easier with beta access [18:11:43] true [18:12:35] something to note: none of the i18n would exist outside of the local wiki for most custom levels [18:12:56] So it might display funny [18:13:12] Unless we deployed the i18n for custom groups via magic [18:13:34] But that goes against someone's idea (might have been yours too) to make it possible via ManageWiki @pixldev [18:17:06] Could you elaborate a bit on what i18n has to do with this [18:18:22] Because custom user rights and custom protection levels come with custom i18n [18:18:56] Things like Special:ListGroupRights (well the global equivalent) will have a missing message [18:19:19] I don’t really care if it looks funky for us specifically, if it affects the end users maybe, but my intention is really just to have the right there [18:19:28] As in it won’t show the group had the right at all? [18:20:07] Nah you'll get the instead of looking normal [18:20:13] It will only affect the interface [18:21:57] Do you mean literal the text message name or like editstaffprotected [18:24:05] The nice human friendly text bits [18:24:59] That’s basically what already happens by default and no one changes it (example, [[mh:phighting:Special:ListGroupRights#maintenance]]) [18:24:59] https://mh.wikipedia.org/wiki/phighting:Special:ListGroupRights#maintenance [18:25:05]

[18:25:13] Well you need to be reset [18:26:37] Fair [18:26:58] So [18:27:35] Literally no change, and still perfectly clear to users if they for some reason check GlobalGroupRights locally, Stewards have edittrusteduserprotected [18:28:19] Ye [18:28:26] I’ll make a task then [18:31:11] Looking now, may be harder then expected cause we don’t standardize edit*protected as the format [18:31:30] So we’d need to iterate over the restriction levels thing [18:31:43] And check to make sure we’re not granting GA any rights that do stuff [18:32:06] We never make things easy [18:32:32] nope [18:33:02] i think if any wikis have rights for protection levels that are actual existing rights [18:33:11] we can ask to prety plz change? [18:34:48] https://github.com/miraheze/mw-config/blob/18a88203234d34393a007f3a6f6150c295c22b20/LocalSettings.php#L5360 does this mean the 'templateeditor' group or right? [18:35:09] i know its meant to to be rights but sysop and autoconfirmed work for back compat [18:35:46] It's rights [18:36:44] okay i see in availible rights yeah [18:37:35] @rhinosf1 is wgAvailableRights used for anything besides socialprofile and custom prop levels [18:37:44] https://github.com/miraheze/mw-config/blob/18a88203234d34393a007f3a6f6150c295c22b20/LocalSettings.php#L5517C4-L5517C21 [18:38:58] Yes [18:39:01] That's a + [18:39:11] Not a 'wgAvailableRights' [18:39:57] yea saw ugh [18:40:10] i meant the things in that list we can get it [18:40:54] wgManageWikiPermissionsAdditionalRights exists to make like worse too [18:41:49] okay, lets stay on using the wgRestrictionLevels [18:42:43] as SomeRandom siad [18:43:12] though probably add an exception for autoconfirmed user(why is this) and sysop? [18:46:04] is editinterfaceadminprotected a default right, no no its not [18:46:10] not sure why thats [18:46:11] idk [18:46:22] do we wanna add hard coded exemptions for things like that? [18:46:24] well nah [18:46:34] the actual interface stuff is still namespace protected [18:46:34] right [18:46:55] whatever @abaddriverlol @rhinosf1 ill file a task real quick [18:48:38] https://issue-tracker.miraheze.org/T14439 [20:08:44] https://meta.miraheze.org/wiki/Tech:Changing_your_wiki_license [20:08:51] if someone can reverse [20:09:12] (not on PC right now) [20:09:36] @Meta Administrators [20:09:46] o7