Steward requests/Miscellaneous

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
Requests and proposals Steward requests (Miscellaneous) Archives
This page is for requesting that a specific administrative action (such as page deletion) be performed by a steward or global sysop on a Wikimedia wiki having no active administrators. (If the wiki does have active administrators, file the request with one of them.) If the wiki has an active editor community, any potentially controversial action (deletion of actual content, edit to a protected page, renaming of a protected page, etc.) should receive consensus from the wiki community before being requested here, and a link should be provided to that consensus in the request.

To add a new request, create a new section header at the bottom of the page (but above the See also section) using the format below:

=== Very brief description of request here ===
{{Status|In progress}}
Give details about your request here. --~~~~

It is helpful if you can provide a link to the wiki (or the specific page on the wiki) in question, either in the header or in the body of your request.

When reporting cross-wiki vandalism, the following template calls can be used to link to a user's contributions across all Wikimedia content wikis (these are for logged in users and non-logged-in users, respectively):

* {{sultool|Username}}

* {{luxotool|IP.address}}

Template {{LockHide}} can also be used in appropriate cases.

To request approval of OAuth consumers please use {{oauthapprequest}} (see the documentation before using).

Old requests are archived by the date of their last comment.

Cross-wiki requests
Meta-Wiki requests


Manual requests[edit]

Please see a list of pages nominated for speedy deletion via {{Delete}} and/or the local equivalent. You can also filter by wikis whose admins are less than X or have not delete since Y.

Myeuurn, Baka Líte, Gioniiiiii[edit]

Status:    In progress

I am reporting a case of long term abuse and cross-wiki vandalism. Users Myeuurn's and Baka Líte's accounts have been globally blocked ("Long-term abuse") like 4 of the proxy IP ranges they have been using to log in and edit (66.160.0.0/16, 64.71.128.0/18, 72.52.64.0/18 and 74.82.0.0/18) while Gioniiiiii has been blocked for sockpuppetry in it.wikipedia less than one hour after the account was created. I would like stewards to control whether the sockmaster of these sockpuppets is an Italian user named Ninonino. My suspect is that this user chose to use proxies and socks to edit lately in order not to be recognised nor detected, if he had thought his edits were right then he would have used his real account to do them instead of hiding himself behind open proxies and undeclared socks, besides normal IPs from Northern Italy. There is also another likely sock, Fulgencio Kokomeci, but he made just 6 edits and was not blocked. Probably there is no need for a checkuser request, because the evidences connecting Ninonino to the other accounts and IPs are too manifest. I am providing some differences between revision which link the socks, the proxy IPs, the normal IPs and Ninonino to each others:

  1. Myeuurn is 66.160.188.86
  2. Myeuurn is 151.34.69.186
  3. 151.34.19.233 is 66.160.178.43
  4. Baka Líte is 72.52.87.71
  5. 151.36.36.227 is 74.82.17.89
  6. 151.82.52.48 is Ninonino
  7. 151.68.133.185 is 195.206.3.188
  8. 195.206.3.188 is Ninonino
  9. 195.206.3.188 is Ninonino
  10. 195.206.3.188 is Ninonino
  11. Gioniiiiii is Ninonino and 195.206.3.188

As you could see, the user is obsessed with final accents in Italian names, specially for Berté/è, he usually edits the same pages in different wikis rollbacking whoever reverts him, that is edit-warring. Examples 1 and 2 are just there to show the identicalness of edits made by one of the socks and a proxy IP plus a normal IP. In example 3 he rollbacks a Portuguese admin. Examples 4 and 5 are there to show another pair of proxies he has used in the past for the same edits. Example 6 shows that Ninonino himself made identical edits to one of those normal IPs. Example 7 is the most interesting: on the 23rd of January he wrote a message with static IP 195.206.3.188 at 09:12; 6 minutes later he deleted that message; at 09:49 he came back and rewrote the same comment with a dynamic IP: this means he did not want his message to be connected with IP 195.206.3.188, which is the main IP used by Ninonino to log in and edit (see next point). Exemples 8, 9 and 10 are the ultimate evidence, since IP 195.206.3.188 himself signs "Ninonino" and even declares "I'm Ninonino" while Ninonino himself declares "195.206.3.188 and Ninonino is always me". In example 11 you can see that the 3 users refer to the ISTAT (the Italian institution of statistics) as to the only correct source for final accents in Italian names. The Italian comune he is most obsessed with is Portobuffolé: Ninonino a pair of years ago made a personal cross-wiki war against the correction of the accent, which was finally corrected in every wiki but in Lombard wiki which is his home wiki, but even today he keeps trying writing the uncorrect spelling in other wikis, as you can see here. If it walks like a duck... That is not all, because through his socks and anonymous IPs he did also some unequivocally inappropriate or even disruptive edits: removing section title - removing content - deforming content - further deforming - disrupting a wikiling. These were just some examples. Well, in the light of all this I suppose you will agree with me about the likelihood of this connection and that it is the case to at least give it a try and investigate. As I said probably there is no need for a checkuser request but, in case, it would provide for sure the overwhelming evidence. I just hope you will not ignore this case, I have given you all the information you may need about the very very likely identity of the original "Long-term abuser". Gheorghiosan (talk) 15:30, 11 July 2018 (UTC)

@Gheorghiosan: Thank you for your detailed report - I've read it and I believe you are asking the following:
  1. I would like stewards to control whether the sockmaster of these sockpuppets is an Italian user named Ninonino
  2. You would like confirmation/investigation that the IPs/Users you have listed are the same person
  3. You would like action to prevent this abuse (global block/locks)
As you may be aware, we cannot publicly link an IP address to a user's account - we can however have a look at these IPs/Users and see if they warrant any global block/global locks.
To help us better understand your request, could you summarise what you would like us to do in one sentence? Again, thank you for taking the time to report this to us, and I do apologise we have not responded sooner. Your efforts are very appreciated - TNT 💖 07:06, 19 July 2018 (UTC)
@There'sNoTime: Thank you for reading my report. I'll try summarising my request. The 3 points you've underlined are what I'm asking stewards: to verify that the sockmaster is Ninonino, to verify that Fulgencio Kokomeci is another sockpuppet (and to verify whether there're others hidden behind those proxy or normal IPs), to take measures against the users involved in this case of sockpuppetry. In one sentence, I'd like a steward to verify the information I've provided through the differences between revisions and, once verified, to establish if a connection among all these identities (blocked sockpuppets, non-blocked suspicious users, blocked proxy IPs, non-blocked Italian IPs, Ninonino) is probable (on my humble opinion, it's more than evident); in case stewards establish it, I hope that measures will be taken, since both using open proxies and abusing sockpuppets is forbidden, and the fact that such actions have been going on for so long makes this a serious case. I don't know if it's possible for checkusers to use their tools for Ninonino himself, because he's not been logging in after last december, exactly when the proxies and sockpuppets started being used, but example 7, together with examples 8, 9 and 10, are quite exhaustive and they should be an overwhelming evidence. About the IPs, I know that they can't be publicly connected to users, but I'm not asking stewards to do that, I've just given them a lead to start investigating. If you need further information, don't hesitate to ask me. Gheorghiosan (talk) 15:45, 19 July 2018 (UTC)
@Gheorghiosan: Thank you for the clarification - I had read this and started to take a look, but it appears this will require a lot of investigation. The stewards are limited as to how far we can help, but it appears at the very least we'll be able to put in place some global blocks and locks. Please bear with us on this one - TNT 💖 06:55, 20 July 2018 (UTC)
@There'sNoTime: Sure, I'll bear this one with you. The important thing is, and I think we agree, that the LTA's sockpuppets are detected and blocked together with the sockmaster's main account, whoever it is (even if he was someone else than Ninonino, but this is very unlikely). Gheorghiosan (talk) 11:11, 20 July 2018 (UTC)
@There'sNoTime: any news here? --Alaa :)..! 11:13, 3 August 2018 (UTC)
I don't think so... Perhaps he's on holidays. Couldn't you solve this request in his place, please? Probably it won't be even necessary a real CU check, it's just about accepting the evidences brought here which link all these identities to each others and to Ninonino, I've provided stewards every information they may need, I think! Gheorghiosan (talk) 11:19, 6 August 2018 (UTC)

Need help stopping vandalism in Lithuanian Wiktionary[edit]

Status:    Done

The Lithuanian Wiktionary is currently experiencing some repeated vandalism from an anonymous user. They are spamming useless articles and undoing my reverts. See here: [1] (Admittedly, today there have been fewer offending edits, so maybe the anonymous user will just disappear without stirring up too much trouble)

The Lithuanian Wiktionary currently does not have any active users other than myself and there is only one semi-active admin [2] who is rarely seen.

As an ordinary user, I cannot take any measures to stop further vandalism, other than keep reverting those edits. I believe we should delete the spam articles and post a warning on the anonymous user's page or temporarily block them. --Rokas00 (talk) 19:58, 31 July 2018 (UTC)

You can post a warning yourself. As to deletion, please, mark all articles that need deletion with an appropriate template or at least create a list of them. Ruslik (talk) 20:31, 1 August 2018 (UTC)
@Rokas00: so? --Alaa :)..! 11:16, 3 August 2018 (UTC)
I marked those articles with a deletion template but the user in question simply keeps removing it. As for posting the warning myself, I can definitely do it, but what's the point? One, the user keeps changing their IP address - they have edited from seven different IPs over the past few days. If you check this list here [3], you can see edits from different IPs in articles named something like "Tukas ir dagilė", "Tuko pelės ir dagilės pelės" or something similar. All of this is garbage, it doesn't mean anything in Lithuanian.
Second, if a warning could help, no such warning would be needed in the first place because a reasonable person wouldn't be vandalizing WIktionary like that anyway. However, if an official warning is a must, I can post one. Rokas00 (talk) 19:51, 3 August 2018 (UTC)
Edit: I see it was actually me who came up with the idea of issuing a warning to the user. Well, now I do think a warning won't help here. Blocking the anonymous user seems a more reasonable measure in this case. Of course, that's just my opinion, you probably know better about the preferred way of handling such issues. Rokas00 (talk) 19:58, 3 August 2018 (UTC)
@Rokas00: Sveikas! Looking at the edits, I have to agree with you they are a little strange. However, I'm not quite sure what to do with the templates that IP user has created/overwritten. Also, some pages (like the one on families) look more like clueless/experimental edits rather than vandalism, while other pages are nonsensical. Since you are the only active user, you are also the best one to judge what happens to these templates. Therefore, I would suggest you apply for adminship on the wiki (wikt:lt:Vikižodynas:Kandidatavimas į administratorius) and shouldn't there be any objections within the next 2 weeks (which is unlikely to happen on a near-dead wiki) a steward will grant you admin rights for a limited time period upon request at SRP. --Vogone (talk) 21:48, 3 August 2018 (UTC)
@Vogone: Sveikas! Thanks for cleaning up and temporarily blocking the anonymous vandal. I hope that will be enough to stop the disruption and make them rethink what they're doing. About those templates they created - I will look into this and decide what should happen to those templates by my best knowledge (though admittedly, I don't feel entirely confident about the technical stuff in the templates). Still, judging by the fact numerous template changes happened at the same time as this other vandalism, I'm pretty sure the template changes are also part of it.
Thanks for the advice about requesting adminship rights. I also think that is a good idea given the fact the Lithuanian Wiktionary is lacking a more active admin supervision. Rokas00 (talk) 17:51, 4 August 2018 (UTC)

Bot activity in Turkish Wikinews[edit]

Status:    In progress

Over in the Turkish Wikinews, GrondinBot has created thousands of empty "daily" project pages and categories, and apparently will continue to do so forever into the future, despite the fact that the wiki has almost no editing community left and no admins, the bot was seemingly only explicitly approved to maintain interwiki links, and the users who were involved in the approval process (AFAICT) have not edited the wiki for about 5–8 years. See n:fr:User talk:Grondin#Daily pages, where I challenged the bot's operator on the necessity and validity of this bot work and was completely unsuccessful (the discussion includes more links to evidence — although to understand all of it, it would help if you read French as well as Turkish [I read neither]). I believe the work this bot does is no longer needed on that wiki and that the vast majority of pages it has created there should be deleted. Steward opinions on this? I posted a comment nearly identical to this one on the wiki's equivalent of the VP two weeks ago, and have gotten no response. - dcljr (talk) 20:46, 31 July 2018 (UTC)

You argument is basically that trwikinews is dead and should be closed. Ruslik (talk) 20:07, 8 August 2018 (UTC)
Um, no, my argument is that the wiki has no real editing community and no admins, but has a bot that will be filling the wiki up forever with useless, empty pages. The bot should be stopped and the worthless pages deleted, but the wiki can sit there inactive forever, as far as I'm concerned. Inactivity is not a valid reason for closure, anyway. - dcljr (talk) 05:30, 9 August 2018 (UTC)
Well, IMO, "no real editing community and no admins" are sufficient to close a wiki and bring them back to the incubator, but langcom won't buy my arguments, so... back to the discussion, if there is no community as you describe and there is no objection for few weeks (or a month), I guess bot can be blocked (to stop them). Deleting the debris will take more time than I want to, so if someone wants to do it, they should do it after getting temporary adminship. — regards, Revi 05:45, 9 August 2018 (UTC)

Ajapaik web (testing)[edit]

Status:    In progress

This is for developing Ajapaik in virtual machine. There is also "Ajapaik web localhost" by me where i failed to copypaste correct url to callback URL and that request can be deleted. --Zache (talk) 11:06, 7 August 2018 (UTC)

Per phab:T201166 I changed the callback url to staging.ajapaik.ee so it is now pointing to public web with https. Original request can be closed). --Zache (talk) 07:34, 8 August 2018 (UTC)

Global block for 46.72.0.0/16[edit]

Status:    In progress

Proxy server status confirmed by administrator. Contribs for this IP range is enough for indefinite cross-wiki block (46.72.24.21 caught on Italian Wikipedia as Tor exit node, and 46.72.0.0/16 caught on Russian Wikipedia as IP for block evasions and 46.72.0.0/16 caught on Japanese Wikipedia as Tor exit node). ZimmermannKKK (talk) 13:01, 9 August 2018 (UTC)

@ZimmermannKKK: SRG is a more appropriate venue for global block requests. PiRSquared17 (talk) 13:45, 9 August 2018 (UTC)
@PiRSquared17: not in use. Must be autoconfirmed, but I am not autoconfirmed. I'll purge this flag before of approval of another Steward. This is a question of life and death. ZimmermannKKK (talk) 19:59, 9 August 2018 (UTC)
@Vituzzu: action required! 46.72.24.21 17:20, 14 August 2018 (UTC)

Cross-wiki USB-C changes 2018-08-08[edit]

Status:    Not done

Cross-wiki rename without talking and sometimes against explicit consensus.

2018-08-08 a user from frwiki after a dispute in frwiki moved USB-C pages in several Wikipedias. The user also altered labels in Wikidata and edited articles in other Wikipedias. The user even went so far to request deletion of redirects from USB-C to the new title, potentially creating broken incoming external links. He knows https://www.google.com/search?q=%22USB-C%22+site%3Ausb.org : "USB Type-C™ and USB-C™ are trademarks of USB Implementers Forum." [4], i.e. that both are official names.

More important the common name is the relevant name for articles in several Wikipedias.

Reverts are starting

80.171.207.9 15:55, 9 August 2018 (UTC)

Note: etwiki talk "USB-IF ei taha, et seda tõlgitaks, ja soovitab kasutada USB Type-C või USB-C. Eestlastele suupärasem variant on siis vast USB-C." (The more comfortable option for Estonians is then USB-C.) - Also here the user moved against what was said on the talk page. Disrespect for language issues. 80.171.207.9 15:57, 9 August 2018 (UTC)

At the top of this page: "This page is for requesting that a specific administrative action (such as page deletion) be performed by a steward or global sysop on a Wikimedia wiki having no active administrators.". I can't see any specific request. Please specify one. — regards, Revi 16:21, 9 August 2018 (UTC)
These renames were only done in goal according to the USB-IF. You can see on the official documentation that it is written "USB-IF recommends "USB Type-C" be used [...]" about the USB Type-C name and ""USB-C" as viable terminology to minimize word count [...]" about the shorten name USB-C. --Niridya (talk) 16:26, 9 August 2018 (UTC)
If you want to revert all my edits, you can do. But this I wanted to do is not a cross-wiki vandalism like you (and you differents IPs) are writting in the different wikis. ;) --Niridya (talk) 16:26, 9 August 2018 (UTC)
@-revi and 80.171.207.9: And I think that sending "LOL" to a very kind administrator is not a proof of good faith. --Niridya (talk) 16:41, 9 August 2018 (UTC)
Of course not. But that is a local issue in plwiki, nothing for meta. 80.171.207.9 16:58, 9 August 2018 (UTC)

User:-revi, the specific request is to undo the removals of the name "USB-C" in Wikidata, to move pages in local Wikipedias back, to their previous names. etwiki clearly states "Eestlastele suupärasem variant on siis vast USB-C". 80.171.207.9 16:56, 9 August 2018 (UTC)

And which wiki doesn't have active admins? (etwiki is non-GS wiki, we are not doing anything there.) — regards, Revi 16:59, 9 August 2018 (UTC)
@-revi: Just to be sure : I did nothing bad ? (except answering to this IP) ;) --Niridya (talk) 17:02, 9 August 2018 (UTC)
I haven't made any assessment with regard to your action: the request (at its current form) sounds like an issue that stewards does not intervene. — regards, Revi 17:04, 9 August 2018 (UTC)

User:-revi, are all these Wikis non-GS?:

80.171.207.9 17:07, 9 August 2018 (UTC)

@-revi: These renames are (for me) non controversal title changes. If anyone don't agree, anyone can revert without need of admin right (except on enWP where I opened a rename request). --Niridya (talk) 17:21, 9 August 2018 (UTC)

Stewards does not decide which is the correct name for something, nor we will determine which party is right. Please discuss elsewhere (locally). Steward requests are just for requests. — regards, Revi 17:24, 9 August 2018 (UTC)

Thank you Revi (i will stop ping you at every message^^). --Niridya (talk) 17:26, 9 August 2018 (UTC)
@80.171.207.9: Also, for the record, all of those are non-GS except bewiki and mnwiki. But even those two wikis have multiple active admins. PiRSquared17 (talk) 17:29, 9 August 2018 (UTC)

Report concerning 49.163.196.154[edit]

Status:    Done

When block finished, this IP user create fake articles again. Thanks. --Garam (talk) 10:09, 11 August 2018 (UTC)

They're gone again, for a longer time. — regards, Revi 11:08, 11 August 2018 (UTC)

Sitenotice for ko.wikt[edit]

Status:    Done

A election for adminship begin in Korean Wiktionary. Please add in wikt:ko:Mediawiki:Sitenotice the following:

[[:사용자:Garam|Garam]]님의 [[:위키낱말사전:관리자 선거/Garam|관리자 선거]]가 2018년 8월 26일(KST)까지 진행됩니다.

Thanks. --Garam (talk) 03:28, 12 August 2018 (UTC)

Yes check.svg Done[5], good luck! --Vogone (talk) 14:32, 12 August 2018 (UTC)
Thank you. :) --Garam (talk) 14:33, 12 August 2018 (UTC)


Block Jasonnn~zhwiki on war.wiki[edit]

Status:    Done
Where exactly? Ruslik (talk) 20:44, 12 August 2018 (UTC)
This edit - "祝你全家出门被车撞死". Note that currently there are two sysops in the wiki, and one was active a few days ago. They might be able to handle this locally but not quite sure at the moment. Most of the page is ranting about zhwiki matters, and the user is also indefinitely blocked at enwiki. I'm just pointing out the edits and have no opinion on what should be done next. -★- PlyrStar93 Message me. 20:51, 12 August 2018 (UTC)
Office actions also can be taken if continued like this in anyway, especially making threats. SA 13 Bro (talk) 21:21, 12 August 2018 (UTC)

OAuth consumer approval for the Bulgarian community Phabricator[edit]

Status:    Done
Moved from Meta talk:OAuth administrators.

Hi! Could you please approve the consumer that I've proposed, which should allow our Bulgarian community users to register and login to our (new) Phabricator. Deploying a Phabricator for local use has been discussed several times in the past, but became quite important with the new way the JS/CSS code in the MediaWiki namespace is handled, as we finally settled upon a code review process with automatic deployment (probably via Jenkins). It will likely also be used for the further development of the AI sysop bot PSS 9 and other more complex bot projects, as well as for general coordination and communication in various fields, e.g. by the current (and possibly new) Bulgarian user groups, where the wiki itself may not be flexible enough. The Phabricator instance is hosted by the Computer Assisted Research and Teaching Lab (C.lab) of the University of Plovdiv, Bulgaria, which already hosts wikimedian resources like the BG community blog and mailing lists. The local announcement is here. Please let me know if there are any problems with the request. Thank you very much for considering it.
— Luchesar • T/C 17:15, 13 August 2018 (UTC)

Come to think of it, I should probably write a more user-centric description of the consumer, as this is likely what the users will see when trying to login, no? It seems there isn't a way to update it once proposed, so should I instead create a new proposal?
— Luchesar • T/C 17:54, 13 August 2018 (UTC)
I've created an updated proposal with more concise description. The link above has been updated. Feel free to delete or do whatever is appropriate with the old proposal. Thanks!
— Luchesar • T/C 21:26, 13 August 2018 (UTC)

No, only the name of the consumer is shown on the authorization form (which is not great but that's how it is). Anyway, approved. Re: deploying CSS/JS, maybe you are interested in phab:T187749. --Tgr (WMF) (talk) 09:42, 14 August 2018 (UTC)

Tgr (WMF), thank you! I really appreciate your work on the new way of handling site JS/CSS - and it's even greater that you've been also considering the use of external repos. Concerning the OAuth consumer, I'm afraid I hadn't checked the "use callback URI as prefix" option. So I had to create a yet newer version. This time I checked that it works (hadn't realized I could do it with my own account). Could you please approve it, while possibly disapproving the previous one? Sorry for the mess!
— Luchesar • T/C 18:21, 14 August 2018 (UTC)
@Iliev and Tgr (WMF): Butting in here, but I've just approved 1.2 and disabled 1.1 - TNT 💖 18:28, 14 August 2018 (UTC)

Pending speedy deletion requests on nahwiktionary[edit]

Status:    On hold

Please check wikt:nah:Neneuhcāyōtl:Para borrar en breve (edit: 28 subcats, 42 pages ATOW. 18:58, 13 August 2018 (UTC)). The only administator there has not been active in the last year (edits, logs). CC User:Marrovi as the author of most (all?) of those requests. Kind regards, Peter Bowman (talk) 18:53, 13 August 2018 (UTC)

X mark.svg Not done, the "only administrator" you mentioned as well seems to be the author of most of these articles. I suppose it's best to wait until he returns. In the meantime, a ping (@Frank C. Müller:) should suffice. Regards, --Vogone (talk) 00:45, 14 August 2018 (UTC)
He really is the only one right now, no need to quote. I agree with you, though - it looked to me like he had left the project, but now I see he's still active elsewhere. Would it make sense to put this request on hold for one week or two until he responds? Peter Bowman (talk) 12:43, 14 August 2018 (UTC)
If you prefer, sure. I used quotation marks just to make it clear that I referred to someone whom you had previously mentioned. I am sorry if this has been misunderstood. Kind regards, —Vogone (talk) 15:11, 14 August 2018 (UTC)

Delete spam[edit]

Status:    Done

Please delete this follow spambot contributions in GS wiki, Meagan51Y82178 and KrystynaCmb. Thanks --Igna Flag of Uruguay.svg (talk) 00:17, 14 August 2018 (UTC)

Yes check.svg Done --Vogone (talk) 00:35, 14 August 2018 (UTC)

Delete draft known Krav Maga IKMF[edit]

Status:    Not done

Please delete this draft on enwiki, because it has been proposed for deletion. Isn't in english, but in romanian. 109.98.165.185 09:01, 17 August 2018 (UTC)

X mark.svg Not done En.wiki has local admins that can delete the page. -- Tegel (Talk) 09:09, 17 August 2018 (UTC)

See also[edit]