Jump to content

Steward requests/Miscellaneous/2023-12

Add links
From Meta, a Wikimedia project coordination wiki
< Steward requests | Miscellaneous
Latest comment: 1 year ago by Martin Urbanec in topic Manual requests


Manual requests

Latest comment: 1 year ago49 comments27 people in discussion

bigdelete needed for ko:도전!_골든벨의_에피소드_목록

Status:    Done

This article is subject to deletion under new local policy(ko:백:목록 문서), however kowiki administrators cannot able to delete this article due to 5000+ edits made in this article. Please delete this article with BigDelete function. --*Youngjin (talk) 10:20, 30 November 2023 (UTC)

Deleted :-) Vermont (🐿️—🏳️‍🌈) 17:56, 30 November 2023 (UTC)

Fix MediaWiki:Common.css on ugwikt

Status:    Done

The local common.css including ".ns-0 h2" setting（wikt:ug:MediaWiki:Common.css#L-39). This affects the display of the title bar under Timeless Skin. I think it will be fine by changing it to ".ns-0 #mw-content-text h2" I checked the local sysop group and interface-admin, there is only abuse filter in sysop group. Since the impact is smaller and there are fewer local participants, I am making the request directly here, please understand. --LaMagiaaa (talk) 14:51, 1 December 2023 (UTC)

@LaMagiaaa have you tried this (such as via your own user/common.css) across various skins (esp the default reader skin) on that project? — xaosflux Talk 15:06, 1 December 2023 (UTC)
I didn't write that on my css. Actually, I found this on Wiktionary in other languages (for example, kawikt). Since the part he's responsible for is similar, I just submitted it here. I just tested the effect of ugwikt’s current CSS on other skins and found no problems. Since the application scope of the newly replaced code is smaller than the original one, my technical level does not allow me to test it on the local wiki in this case. Precisely because the scope has become smaller, I think there will be no problem with the new code.
If you still think I need a local test, please reply again and I'll try my best. Thanks. LaMagiaaa (talk) 15:51, 1 December 2023 (UTC) Since I had some time to spare, I ran a local test. I set a color and style that I had never seen on the wiki and looked at all the supported skins. Only the places I expected changed, and the rest of the places maintained the local site-wide css settings. I think no problem will occur.--LaMagiaaa (talk) 06:54, 2 December 2023 (UTC)
Done — xaosflux Talk 12:06, 9 December 2023 (UTC)

kmwiktionary: collapsible boxes to work on mobile

Status:    Not done

Please add the following scripts in Mediawiki namespace: navframe.js, common.js, common.css, mobile.css. Please also change the namespace and its talk page to translated one: "Wiktionary" → "វិគីនានុក្រម". Thank you. — RalvahKaset (talk) 06:01, 18 April 2023 (UTC)

@RalvahKaset, for the latter one you have to follow Requesting wiki configuration changes, it is not changed with an on wiki edit. --Base (talk) 00:54, 22 April 2023 (UTC)
I see, thank you. So I'd like to retain the former request only. RalvahKaset (talk) 02:59, 22 April 2023 (UTC)
@RalvahKaset, the two scripts in navframe and common .js pages seem to be almost the same. Do you really need both? @Ladsgroup, @Krinkle, @MusikAnimal, @Matma Rex, could any of you review if that script is safe? I am not too sure about that id concatenation, but my JS knowledge is rather basic.--Base (talk) 00:50, 17 November 2023 (UTC)
yeah, that script seems to have unsafe concat. Amir (talk) 23:00, 18 November 2023 (UTC)
@RalvahKaset The wiki has a mw-collapsible feature that works on all wikis by default, and does not require custom NavFrame script. Does this satisfy the needs of kmwiktionary? See mw:Manual:Collapsible_elements for examples. Krinkle (talk) 02:47, 17 November 2023 (UTC)
Not done no response to concerns. — xaosflux Talk 12:09, 9 December 2023 (UTC)

Wikifunctions GS

Status:    Not done

Hi stewards. There has not been a discussion on wikifunctions about opting in to the global sysops group, and per Global sysops#Scope I don't think the wiki meets either criteria for the group to be active. Until there is a local discussion I think the wiki should be removed from the group. Thanks, --DannyS712 (talk) 23:16, 8 December 2023 (UTC)

@DannyS712: all new projects are part of the GS group (it is an opt-out group). If there is sufficient community and support, the project is welcome to withdraw after establishing a local consensus in a well advertised, well attended discussion. — xaosflux Talk 11:59, 9 December 2023 (UTC)
@Xaosflux that seems to be counter to the scope documented on the global sysops page. Yes as a new wiki it was part of the GS scope but once it no longer meets the criteria for GS it is against policy for a GS to use the tools there and so the wiki should be added to the wikiset. Looking at the history of the wiki set as well (Special:WikiSets/7) it seems that a discussion is only needed to opt out when the wiki is within the scope of the group or opt in when not in scope. Please reconsider --DannyS712 (talk) 16:23, 9 December 2023 (UTC)
Not done @DannyS712 I'm not going to opt-out this new wiki based on the request of one user. That project doesn't yet even have permanent administrators. I suggest you start a discussion at f:Wikifunctions:Project chat to determine if the developing community agrees with you or not first. You may appeal this decision at Stewards' noticeboard if you wish (please @ping prior participants above). — xaosflux Talk 18:27, 9 December 2023 (UTC)
Comment Comment See Steward_requests/Miscellaneous/2022-01#Add_azwiki_into_Opt-out_GSwikiset, a similar request to opt-out a wiki that currently does not meet default criteria for opt-in to the GS wikiset, but its community has never objected to GS acting there. If I may ask, is there a need to prevent global sysops from acting when urgent? Apart from other reasons, I would rather not have another project vulnerable to LTAs/vandals that deliberately target/exploit non-GS wikis with few active sysops like GRP. Please note that this is just my 2c and I do not mean to prevent another steward from applying the current policy as it is written now. I just think we need a RfC to establish (or make it clear to avoid confusion) that, outside default opt-in criteria, global sysops may act on emergencies if the project has not explicitly opted out. Perhaps Global_sysops#Scope could be changed a bit. — Elton (talk) 17:34, 9 December 2023 (UTC)
I think my fellow stewards are right on point here. Meeting the requirements to qualify for GS not to use their tools (which could change based on activity) vs. permanently opting out are two very different things. It's a big decision for a wiki to opt-out of GS and responsibility is high. We are conservative in our handling of advanced rights when looking at wikis because we've seen their worst sides on a global scale. That said, I would completely accept a discussion like Xaosflux mentions should the community thinks it's ready.
The GS policy could use better clarification, but the working consensus I think by most stewards right now is we would not action this request. -- Amanda (she/her) 20:01, 9 December 2023 (UTC)
@AmandaNP who said this was permanent? The history of the wiki set shows that wikis that are removed from the group due to not meeting the scope criteria (but not wikis that opt-out via a discussion) can be re-added without an opt-in discussion the same way. I'll start a local discussion though. DannyS712 (talk) 21:30, 9 December 2023 (UTC)

en-Wikipedia deletion of article with >5000 revisions

Status:    Done

I just closed an AfD on English Wikipedia here. Consensus was for deletion. However, I am technically prevented from deleting the page, as it has more than 5000 revisions. I understand this rule was put in place to prevent accidental deletions to important backend pages. However, this is a regular article (linked here). I'm requesting that a steward delete the page. Thank you. --Ganesha811 (talk) 13:25, 13 December 2023 (UTC)

@Ganesha811, done. Please proceed with fixing red links at your discretion. You may also want to check these subpages. Regards. —Teles «Talk ˱C L @ S˲» 16:37, 14 December 2023 (UTC)
Thank you! Ganesha811 (talk) 16:48, 14 December 2023 (UTC)

Please help us modify CSS on Min Dong Wikipedia

Status:    Done

Min Dong Wikipedia (https://cdo.wikipedia.org/) currently lacks interface-admin. Please help us modify Common.css according to cdo:MediaWiki討論:Common.css#Modification requests. Yejianfei (talk) 03:42, 21 December 2023 (UTC)

@Yejianfei: I have moved this request from M:RFH since that page is for help on meta and this is the page for help on other wikis --DannyS712 (talk) 08:58, 21 December 2023 (UTC)
Done--16:32, 21 December 2023 (UTC)

Please take a look...

Status:    Done

Helper123422 [1] harasment and vandalism in Spanish Wikibooks and (possibly) in Russian Wikibooks. Regards! Esteban (talk) 18:26, 22 December 2023 (UTC)

Locked, although this request should have been made at SRG . Sgd. —Hasley 19:00, 22 December 2023 (UTC)

Arabic Wikipedia protest forced logout script

Status:    Done

First of all: I am not writing here to prevent the protest itself. I don't think this is the right venue to discuss this.

However, there is one thing that, in my opinion, needs steward intervention, and it is the way they enforce the protest. The protest script enforces logout of everyone who views Arabic Wikipedia. This happens without warning and may lead to people beginning to edit anonymously in other projects without knowing what they are doing (it nearly happened to me). I think this is an unreasonable way of protesting because it affects users globally, even those who never had an intention to edit it but just opened a link, either via an interwiki or because of the news.

I would like to ask a steward (you need to grant yourself local interface admin rights first) to remove this specific part of the protest, potentially replacing it with any other code with the same effect but without logout.

For obvious reasons I unfortunately cannot discuss this locally. Thanks — NickK (talk) 07:38, 23 December 2023 (UTC)

  • Comment Comment All forms of arwiki protest (for 24 hours) done with arwiki community approval. Regarding "without warning", the code include mw.notify part, that a warning appears before you log out. Maybe you mean to notify the globally community before the protest? Question Question: "replacing it with any other code with the same effect but without logout", any suggestions? --Alaa :)..! 08:02, 23 December 2023 (UTC)
    @علاء: I trust you that there was a community approval, although I obviously cannot check it now. My issue is that there is no warning before the logout, so a user opening any Arabic Wikipedia page doesn't know (and definitely does not expect) they will be immediately logged out. I also tried again now and I did not see any warning, maybe it is not visible because of the banner.
    On the second part: it looks like you are already preventing all edits, why do you need to log users out? When Ukrainian Wikipedia had a protest almost in January 2014, we did not have to log anyone out, it worked well without. Other protests, like the SOPA/PIPA in the English Wikipedia in 2012, also did not log users out — NickK (talk) 08:24, 23 December 2023 (UTC)
Hello NickK, In fact, I did not participate in the discussion (due to personal circumstances), but I read the entire discussion and the final conclusion/summary there. Regarding the warning before logout, here an example (someone posted about the notice they encountered when forced logout). About the second part, I think the community want to avoid the feature of disabling the filter when a certain number of hits occurs? I read that arwiki community mentioned on the discussion the ukwiki (2014) and enwiki (2012) examples. Note that JavaScript codes can also be overridden. I would like to point out that I am not in a position to discuss "the protest itself"; as you know it's a community consensus. Feedback is required to avoid any problems similar to what was mentioned above (problems that were not taken into account by the community), I will definitely pass it on to the community --Alaa :)..! 08:40, 23 December 2023 (UTC)
I think I might have seen this message but because I was switched from Monobook in English to 2022 Vector in Arabic I probably missed it. Because I cannot read Arabic, I had an interface in English to be able to understand system messages. The logout prevents non-Arabic speakers from understanding what is happening (and I guess there will be more of them than usual because of the news). And from user-friendliness perspective, if an action leads to a logout (in this case opening of any page in Arabic Wikipedia does), there should be a clear message before a user does this action, which is clearly impossible here — NickK (talk) 09:14, 23 December 2023 (UTC)
I think there are alternative methods of preventing others from editing, such as using title blacklist (.*). Automatically logging everyone off without any notification is annoying and can cause privacy issues as users may leak their IP address when they are logging out. SCP-2000 13:01, 23 December 2023 (UTC)
  • I agree that the forced logout part of the code should be removed. Visiting arwiki after seeing the protest link and clicking it unexpectedly logged me out on enwiki, mediawikiwiki, commons, etc. I have two factor authentication, so this also means I have to two factor again in many places, including my desktop, laptop, and phone. –Novem Linguae (talk) 13:14, 23 December 2023 (UTC)
  • I also want to say that this is unacceptable to do given the SUL implications and that code should be removed by any steward without putting the request ‘on hold’ given the urgency of this issue. I agree with the protest that Arabic Wikipedia is doing, but it does not mean that every single user that visits that wiki needs to be logged out of all projects in continuity (thankfully, that didn’t happen to me, but I empathise with others). stjn[ru] 13:38, 23 December 2023 (UTC)

Thanks for all what you mentioned, we (arwiki community) are currently working on resolving the "logout" point. --Alaa :)..! 14:17, 23 December 2023 (UTC)

Done --Alaa :)..! 14:35, 23 December 2023 (UTC)

This seems not to be solved. I got logged out and additionally my browser crashed. GPSLeo (talk) 20:34, 23 December 2023 (UTC)
@GPSLeo, can you please bypass your cache, then try again? --Alaa :)..! 20:40, 23 December 2023 (UTC)
Yeah seems to have been a cache problem. GPSLeo (talk) 20:47, 23 December 2023 (UTC)

Draft deletion

Status:    Done

Hi! I'm a sysop on the French Wikipedia. A user is creating quite a lot of articles thanks to his/her draft. However, he/she copies and pastes the content every time instead of moving his draft by renaming it. After giving him the advice to do so, he/she asks me to delete his/her draft. However, since it has more than 5,000 revisions, I cannot seem to do it. Could you please do it? Thanks! --Antimuonium (talk) 09:06, 26 December 2023 (UTC)

Done — xaosflux Talk 10:01, 26 December 2023 (UTC)

Move request

Status:    Requires a Phabricator ticket

Move the following pages to the project namespace:

Initially, I submitted a move request for a protected page to the GSR. Later, I noticed that most project pages, including the community portal of this wiki, are created in the main namespace, which seems unusual. I haven't found any active Village Pumps worth discussing in the project, so I'm bringing the matter here. —Yahya (talk • contribs.) 14:57, 30 December 2023 (UTC)

Thanks @Yahya for bringing this up here. Judging by the project's name in the logo, I think Wikisłowôrz is meant to be the localized project namespace name. The localized name was apparently never configured, which means it defaults to Wiktionary. Instead of moving the pages manually to the actual project namespace, I think it would be better to localize the project namespace's name to Wikisłowôrz, since that's what they actually use. Such localization would need to happen via filling a Phabricator ticket (and it can likely be implemented even without explicit community consensus, since they clearly use the localized version, it just never was formalized). Would you mind creating such a ticket in Phabricator please?
With the above in mind, closing this as Not done in favor of localizing the project namespace's name via Phabricator. Thanks for your understanding. Best, Martin Urbanec (talk) 15:28, 30 December 2023 (UTC)
I will create a ticket in Phabricator. Thanks Martin. —Yahya (talk • contribs.) 15:31, 30 December 2023 (UTC)
phab:T354114. —Yahya (talk • contribs.) 16:09, 30 December 2023 (UTC)
Thanks. I uploaded a patch for the task and made a note to deploy it next week (when the deployment freeze gets released). Martin Urbanec (talk) 17:05, 30 December 2023 (UTC)
Retrieved from "https://meta.wikimedia.org/w/index.php?title=Steward_requests/Miscellaneous/2023-12&oldid=26010151"