Stewards' noticeboard/Archives/2021-04

Removing en.wikivoyage from the global sysops opt-out wikiset

There is consensus to allow global sysops to work on en.wikivoyage: wikivoyage:Special:PermanentLink/4194877. Please remove en.wikivoyage from the global sysops opt-out wikiset. Thanks in advance. Leaderboard (talk) 09:31, 28 April 2021 (UTC)[]

  Done --Martin Urbanec (talk) 09:21, 29 April 2021 (UTC)[]
This section was archived on a request by: Martin Urbanec (talk) 09:21, 29 April 2021 (UTC)[]

New request

Block MCCC214,delete User:MCCC214 and User talk:MCCC214,impersonation for my user name,bad faith,possible is this LTA.--MCC214#ex umbra in solem 09:07, 27 April 2021 (UTC)[]

Well, no. Not that user. In the future, post this on SRG, not here. I handled your request, but please read the information above carefully. You can find "This is not the place for stewards requests". --Sotiale (talk) 11:45, 27 April 2021 (UTC)[]
Oh,I should put this request in Meta:Requests for help from a sysop or bureaucrat.--MCC214#ex umbra in solem 11:51, 27 April 2021 (UTC)[]
This section was archived on a request by: CptViraj (talk) 05:36, 8 May 2021 (UTC)[]

Talk:Global blocks#Time to remove the draft

I have started a conversation to push this from being a non-draft document. Please add all thoughts there.  — billinghurst sDrewth 02:30, 12 April 2021 (UTC)[]

WikimediaMessages for 'global-deleter' group

I just noticed that there are no WikimediaMessages for Pathoschild's global group, so I suggest adding these (see phab:T279828). Since this would overwrite the Localised name of the group ("Pathoschild's global group"), I wanted to ask if the stewards are okay with this change, or if there are any objections. Regards --Zabe (talk) 21:17, 10 April 2021 (UTC)[]

I don't have any strong opinion but I'd leave it as it is. This is a special group created for Pathoschild so he can run his synchbot service. Ideally, that service should've been ported already as a MediaWiki extension. I'd leave it without WikimediaMessages. —MarcoAurelio (talk) 10:27, 11 April 2021 (UTC)[]
I agree with MarcoAurelio. Let's leave it as-is. It's not supposed to be a generic group, it's a sui-generis one, only for this very service. Martin Urbanec (talk) 18:06, 12 April 2021 (UTC)[]

MediaWiki\Revision\RevisionAccessException

Hi someone. I'm not sure if it's a bug. I've got several complaint from local Malay Wikipedians that they were unable to move some pages and the error notice appear just like ones in the section which was: "MediaWiki\Revision\RevisionAccessException" and some numbers. The example page is ms:Bones. We tried to move to "Bones (siri TV)" but we weren't unable to do so. Can someone help to check and if it's a bug, would be great if someone can help to create a task in Phabricator and ping me. Thank you! CyberTroopers (talk) 14:56, 11 April 2021 (UTC)[]

@CyberTroopers: This looks like a bug. You can create a phab task. Add your problem, including the error message shown and also add the steps to reproduce it (see mw:How to report a bug#Reporting a new bug or feature request). Regards --Zabe (talk) 16:18, 11 April 2021 (UTC)[]
@CyberTroopers See phab:T279832. Best, Martin Urbanec (talk) 17:06, 11 April 2021 (UTC)[]
Thanks, I did not catch this one --Zabe (talk) 17:07, 11 April 2021 (UTC)[]
@CyberTroopers For the record, the number is a request ID, a number that uniquely identifies the request that caused the error. Wikimedia system administrators can use request IDs to locate the bug's backtrace, which is extremely helpful when debuging. If you ever see a similar behavior, definitely include that ID in your report, it will be appreciated. Best, Martin Urbanec (talk) 17:12, 11 April 2021 (UTC)[]
@User:Martin Urbanec, @User:Zabe Thank you guys for helping! As per my understanding, the bugs is still under investigation and it might related to upper/lower case something in the script? I hope you guys will figure out the solutions and I'll help whatever I could. As for now, I think we'll use {{R from move}} to move the failed page. CyberTroopers (talk) 14:27, 13 April 2021 (UTC)[]
Yes, it's under active investigation. We're still not sure what exactly caused this bug, but we're working on it. It can be related to literally anyting. Best, Martin Urbanec (talk) 14:32, 13 April 2021 (UTC)[]

Use of special:contact/stewards with email blocked IP addresses?

Hi. The applied block message for numbers of IP ranges is to contact stewards at special:contact/stewards, yet I am seeing email is blocked at the same time. Have stewards confirmed that email can be sent to the contact address when an IP range is blocked as it seems counter-intuitive.  — billinghurst sDrewth 21:49, 26 April 2021 (UTC)[]

Email blocked users cannot use steward contact page
Hello, thanks for bringing this up, @Billinghurst. I just tried it from my own Azure-hosted workstation (you can find recording of my screen in the attached video file). I indeed was not able to use special:Contact/stewards, but I was once I changed the block setting to allow emailing.
In another words, as long as an IP address is blocked with "Email disabled", such IP cannot use special:Contact/stewards (as it is an emailing service). When email is allowed, the IP can freely use special:Contact/stewards (and if the block affects logged-in users, also special:Emailuser).
In my opinion, this behavior of MediaWiki makes sense, as the contact page indeed does email people. The issue is that the global blocking interface does not allow me to control how the local block will look like, it automatically disallows email.
I will ask stewards via the maillist to discuss changing this behavior, and if they agree, I'll create a Phabricator task to get this done.
Best, Martin Urbanec (talk) 09:34, 29 April 2021 (UTC)[]
@Martin Urbanec: Thanks, if you check the steward's email archives you can probably find an email about the coding of the tied together block functionality, as we discussed it about 2014 (?), and it was circa the time that we created that contact methodology. Check with Trijnstel she remembers all those things!  — billinghurst sDrewth 09:53, 29 April 2021 (UTC)[]
@Billinghurst The global blocking interface (I just uploaded a screenshot of it to Commons, so you can see it as well) now allows stewards to disable/enable local (Meta) talk page access per-block, which wasn't the case before (the patch for it got merged during my steward tenure). It shouldn't be hard to add a similar checkbox for email stuff, which sounds to fix this issue, right? Martin Urbanec (talk) 09:56, 29 April 2021 (UTC)[]
@Martin Urbanec: I can't see such an option on the beta cluster. Leaderboard (talk) 11:17, 3 May 2021 (UTC)[]
@Leaderboard: please notice that he is changing the local meta block, not the global one. --Zabe (talk) 11:35, 3 May 2021 (UTC)[]
@Zabe: I'm referring to the screenshot, which shows the global blocking interface, unless I am missing something. Leaderboard (talk) 12:18, 3 May 2021 (UTC)[]
@Leaderboard: sorry, I was confused. But this is odd, when I look at the page the option shows up, but just short (see File:GlobalBlock Beta.webm). --Zabe (talk) 12:45, 3 May 2021 (UTC)[]