Stewards' noticeboard

←Stewards

Stewards' noticeboard

Archives→

Welcome to the stewards ' noticeboard. This message board is for discussing issues on Wikimedia projects that are related to steward work. Please post your messages at the bottom of the page and do not forget to sign it. Thank you.

• This is not the place for stewards requests. To make a new request, see steward requests and requests and proposals .
• For illustration of steward policies and use, see the steward handbook .
• See also: Access to nonpublic personal data policy noticeboard.
• This page is automatically archived by SpBot. Threads older than 30 days will be moved to the archive.

Stewards

• About stewards
• Elections
• History

Requests

• CheckUser information
• Global blocks & locks
• Global rights
• Local bot rights
• Local rights
• Account renaming
• Miscellaneous requests
• URL blacklisting
• Title/username blacklisting

For stewards

• Help
• Policies
• Bugs
• Mailing list
• #wikimedia-stewards^connect

Noticeboards

• Access policy noticeboard
• Stewards' noticeboard

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 2 days and sections whose most recent comment is older than 30 days.

Global interface editor JSON permissions

The global interface editor permission has the ability to edit site CSS, JS, and JSON pages and user CSS and JS, but not user JSON. Is there a reason for this? Global sysops are able to edit all CSS, JS, and JSON pages, so it doesn't seem to be an issue about global remit, and the changelog for GIE doesn't show the edituserjson permission ever being added (or removed). This isn't related to any specific issue – just something I noticed. Giraffer (talk) 13:43, 30 December 2022 (UTC)Moved from SRM, where it was originally added --Martin Urbanec (talk) 13:56, 30 December 2022 (UTC)

I think that groups predates that permission being split and noone ever bothered to add it at Special:GlobalGroupPermissions/global-interface-editor; no objections to it being in there. — xaosflux ^Talk 15:13, 30 December 2022 (UTC)

Fixed -- Amanda (she/her) 14:46, 6 January 2023 (UTC)

Requests for comment/Clarification to Global rename policy

I have opened the above RFC. —MdsShakil (talk) 21:21, 12 January 2023 (UTC)

Global username policy

While the page says that this is a proposed policy, it appears that stewards are already following (examples: 1 2 3). I don't know whether the community have commented on this but this doesn't seem to be the case.

And while I'm here asking about whether this is actually a policy, I have to ask, what is actually the point of this? It adds unnecessary bureaucracy and w:WP:BITE to what was previously a very simple process – someone tells you that you have a bad username, and maybe blocks you for it, then you ask to change it, someone changes it and we move on. Now under this policy/proposed policy/whatever... if you have a username that states a political belief, you will be instantly globally locked losing all preferences and contributions you had made under the account. If you want to get your old account back, you'll have to email stewards at least a couple of times, one to appeal the lock and another to say which new username you prefer. If you are unable to access email then you have no way of getting your old account back and you have to start a new account because you didn't read the global username policy... that isn't linked anywhere at the moment. And I imagine stewards already have to deal with tons of emails about editors having to use proxies and other stuff. Why add this on?

I completely understand locking genuine abusive account names, but locking all the accounts that fall under this criteria seems wrong to me, and I would appreciate other people's input on this. Thanks. --Ferien (talk) 21:08, 30 January 2023 (UTC)

I've just copied the above from what I posted on Talk:Global username policy and added a few more examples following some discussion on #wikimedia-stewards^connect. --Ferien (talk) 21:49, 30 January 2023 (UTC)

Hi Ferien, I'm happy to provide more context for this. The policy proposal created by ~riley in 2020 is not the impetus for locking accounts with abusive usernames. If there is a steward who has cited the proposal for an action, please let me know, because it would be incorrect. Stewards have been locking accounts with abusive usernames looooooong before that proposal, as with other forms of abuse. This isn't an addition, this has always been the case.

The three accounts you linked, however, imo did not need to be locked. The usernames were not abusive, and their issues could have been solved with renames, or by allowing local projects to determine if the usernames are appropriate. I'll raise it with the stewards who locked those accounts. Best, Vermont (🐿️—🏳️‍🌈) 23:49, 31 January 2023 (UTC)

Limited local bureaucrat just for emergency deadminship

To effectively solve the problems involving Chinese Wikisource, may I request allowing any limited bureaucrat just for emergency deadminship per local guideline, please? If yes, I know whom to nominate as a candidate, so we will mostly be much happier once solving the issues. I would like to also ask any disinterested stewards about Stewards/Elections_2023#Election_Committee exceeding the tasks [1] [2] [3] [4] as Stewards/Confirm/2023 will be soon.--Jusjih (talk) 22:34, 31 January 2023 (UTC)

I'm not sure what you're asking in the latter part of your above comment (to me, it seems like a thinly veiled threat against the election committee stewards who took actions against your inappropriate questions). Is my assessment correct, and if so do you believe that to be appropriate behaviour for a Meta-Wiki administrator? — TheresNoTime (talk • they/them) 23:17, 31 January 2023 (UTC)

Seeing Bureaucrat#Removing_access that bugzilla is now phabricator, I am withdrawing this topic for now.--Jusjih (talk) 03:20, 1 February 2023 (UTC)

@Jusjih: I expect a reply to the question I asked you above. This section is not resolved — your conduct has been subpar to say the least. — TheresNoTime (talk • they/them) 04:55, 1 February 2023 (UTC)