Steward requests/Miscellaneous

From Meta, a Wikimedia project coordination wiki
Shortcut:
SRM
This page is for Wikimedia wikis having no active administrators. Requests can be made here for specific administrative actions (such as page deletion) to be performed by a steward or global sysop. In other cases:
  • 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.
  • For global lock/block requests, file a request at Steward requests/Global.
  • For non-controversial deletion requests such as empty page, simple spam or vandalism, and non-controversial or emergency requests to block vandals, spammers or other malicious users, you may use global sysop requests instead.
  • If a consensus is considered required to act, similar principles apply as expressed at Steward requests/Permissions/Minimum voting requirements, and can be used for guidance to how and what should be done at small and medium communities to gain a consensus.

To add a new request, create a new section header at the bottom of the "Manual requests" 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


Bot-reported requests

See Global sysops/Speedy delete requests.

Manual requests

150 spam ?

Status:    In progress

All 150 contributions/articles on Studio 54 Network (here in "simple english" for example) appear to be spam ? --Arroser (talk) 12:25, 25 December 2020 (UTC)[reply]

@Arroser: Simple Wikipedia has local sysops, GS or Stewards can't help you. simple:Wikipedia:Administrators' noticeboard--𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 19:27, 25 December 2020 (UTC)[reply]
@WikiBayer: : Simple english was only an example, to have links on the article, on the others WP. The real problem is not only this language, but the 150 articles i think. --Arroser (talk) 19:30, 25 December 2020 (UTC)[reply]
Could you please link articles that are at global sysop-enabled wikis then? THanks! Martin Urbanec (talk) 19:31, 25 December 2020 (UTC)[reply]
OK Wikidata d:Q39841 Article created by Luigi Salvatore Vadacchino. Article are in ak:Radio_Studio_54_Network bm:Radio_Studio_54_Network ca:Radio_Studio_54_Network and more.𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 19:37, 25 December 2020 (UTC)[reply]
I think we should delete these pages. The content is 1 line + Links. This is not Useful for the projects. Please more opinions. --𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 19:01, 26 December 2020 (UTC)[reply]
@WikiBayer I agree Martin Urbanec (talk) 11:02, 29 January 2021 (UTC)[reply]
.:@WikiBayer I agree as well. EstrellaSuecia (talk) 17:06, 5 March 2021 (UTC)[reply]

If we are talking Radio Studio 54 Network (Q39841) then really shouldn't they be raised with the individual wikis. It is not up to this place to determine the notability nor whether pages that have been considered a reasonable addition for 8+ years after they were created. That has not been our role previously, and without some broader discussion through an RFC I don't think that we should act. Different from asking stewards or GS to act as administrators at these wikis where a legitimate conversation has taken place.  — billinghurst sDrewth 00:01, 6 March 2021 (UTC)[reply]

billinghurst the problem i'm seeing is that this is a massive crosswiki borderline hoax :/ Praxidicae (talk) 00:20, 6 March 2021 (UTC)[reply]
@Praxidicae: The item is visible at so many major wikis so who are we at this wiki to make that determination with the scope that we have been granted by the communities in our rights allocation. The processes for deletion of out of scope material is set to belong to local wikis. If the major wikis went about their investigations and came to their determinations, then these determinations flowed out to the wikis, then we have the scope to act. Tell/show me where it is in scope for this forum to be the instigator for such actions. Yes, it means more work, yes it is a PITA, but once we start that slippery slope of granting ourselves the power, then … No thanks, let us act within scope.  — billinghurst sDrewth 00:38, 6 March 2021 (UTC)[reply]
Sorry I wasn't advocating for doing anything, it was just a comment in general. Praxidicae (talk) 00:50, 6 March 2021 (UTC)[reply]
@billinghurst Quote "The item is visible at so many major wikis ... The processes for deletion of out of scope material"
I don't see that as "Out of Scope". One line and the web links is not useful content. Pages with useful content should not be deleted by GS, but pages like in the akWP can, in my opinion, be deleted using Reason "Crosswiki Spam/no useful content". --𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 13:21, 7 March 2021 (UTC)[reply]
I am making zero judgment on the articles. I am talking about the community specified roles of global sysops and stewards.

Out of scope for global sysops and stewards to speedy delete 8 year old articles. Out of scope for Steward requests/Miscellaneous to determine local wikis deletion processes. If you were doing works added today, maybe. Works added in 2012 should go through due process at the wikis. These wikis, they own their issues, we don't. Don't start making this role to be more than we have been elected to do.  — billinghurst sDrewth 14:09, 7 March 2021 (UTC)[reply]

Speedy deletions on suwiki

Status:    In progress

Automatic Visual editor citation on Dagbani Wikipedia

Status:    In progress
Tracked in Phabricator:
Task T261316

On the Dagbani Wikipedia, VE doesn't have the option to add citations automatically. More like the situation we had here. I've looked at the documentation but can't figure out how to configure citoid. We would appreciate some help with this task. --—M@sssly 15:54, 6 September 2021 (UTC)[reply]

Edit Interface of fa.wikibooks.org

Status:    In progress

I raised the issue on the VP and no one opposed it: fa:b:Special:Permalink/113740#تغییرات_رابط_کاربر

Please make the following changes to the to interface of fa.wikibooks.org:

First, create fa:b:MediaWiki:Common.js/CollapseElements.js with the following content

//<source lang="javascript">
// Faster Collapsible Containers
// Originally written by: [[User:Darklama]] from the English Wikibooks

// images to use for hide/show states
var collapse_action_hide = '//upload.wikimedia.org/wikipedia/commons/f/f1/MediaWiki_Vector_skin_action_arrow.svg';
var collapse_action_show = '//upload.wikimedia.org/wikipedia/commons/8/8e/MediaWiki_Vector_skin_left_arrow.svg';
 
// toggle state of collapsible boxes
function collapsible_boxes()
{
	$('div.collapsible').each( function() {
		var $that = $(this), css_width = $that.css('width'), attr_width = $that.attr('width');
		var which = $that.hasClass('selected') ? collapse_action_show : collapse_action_hide;

		if ( (!css_width || css_width == 'auto') && (!attr_width || attr_width == 'auto') ) {
			$that.css('width', $that.width() );
		}

		$(this).children('.title').each( function() {
			$(this).prepend('<span class="action"><a><img src="'+which+'" /></a></span>').click( function() {
				var which = $that.toggleClass('selected').hasClass('selected')
					? collapse_action_show : collapse_action_hide;
				$(this).find('span.action img').attr('src', which);
				if ( which == collapse_action_show ) {
					$(this).siblings(':not(.title)').stop(true, true).fadeOut();
				} else {
					$(this).siblings(':not(.title)').stop(true, true).fadeIn();
				}
			}).click();
		});
	});

	$( "table.collapsible" ).each( function() {
		var $table = $(this), rows = this.rows, cell = rows.item(0).cells.item(0);
		var which = $table.hasClass('selected') ? collapse_action_show : collapse_action_hide;
		var css_width = $table.css('width'), attr_width = $table.attr('width');

		if ( (!css_width || css_width == 'auto') && (!attr_width || attr_width == 'auto') ) {
			$table.css('width', $table.width() );
		}

		$(cell).prepend('<span class="action"><a><img src="'+which+'" /></a></span>');
		$(rows.item(0)).click( function() {
			var which = $table.toggleClass('selected').hasClass('selected')
				? collapse_action_show : collapse_action_hide;
			$(cell).find('span.action img').attr('src', which);
			if ( which == collapse_action_show ) {
				$(rows).next().stop(true, true).fadeOut();
			} else {
				$(rows).next().stop(true, true).fadeIn();
			}
		}).click();
	});
}

$(document).ready( collapsible_boxes );

//</source>

Then import the the page by adding the following to fa:b:مدیاویکی:Common.js:

	importScript('MediaWiki:Common.js/CollapseElements.js');

Finally add the following to fa:b:مدیاویکی:Common.css:

/* Add arrows to toggle-blocks for collapsible elements */
.mw-collapsible-arrowtoggle.mw-collapsible-toggle-expanded {
 padding-right: 20px !important;/* Add arrows to toggle-blocks for collapsible elements */
.mw-collapsible-arrowtoggle.mw-collapsible-toggle-expanded {
 padding-right: 20px !important;
 background-image: url('//upload.wikimedia.org/wikipedia/commons/f/f1/MediaWiki_Vector_skin_action_arrow.svg');
 background-repeat: no-repeat;
 background-position: center right;
}
.mw-collapsible-arrowtoggle.mw-collapsible-toggle-collapsed {
 padding-right: 20px !important;
 background-image: url('//upload.wikimedia.org/wikipedia/commons/8/8e/MediaWiki_Vector_skin_left_arrow.svg');
 background-repeat: no-repeat;
 background-position: center right;
}

/* Collapsible Containers */
.collapsible { margin:0px; padding:0px; }
.collapsible .title, .collapsible tr:first-child th, .collapsible tr:first-child td { cursor:pointer; padding-left:16px; color:#4D4D4D; }
.collapsible.selected .title, .collapsible.selected tr:first-child th, .collapsible.selected tr:first-child td { color:#0645AD; }
.collapsible span.action { display:block; float:right; white-space:nowrap; text-align:right; height:16px; margin:auto 5px auto 0px; padding:0px; }
.collapsible span.action img { height:16px; width:16px; margin:0px; padding:0px; }

.navbox .collapseButton {          /* 'show'/'hide' buttons created dynamically */
    display:none;
}
 background-image: url('//upload.wikimedia.org/wikipedia/commons/f/f1/MediaWiki_Vector_skin_action_arrow.svg');
 background-repeat: no-repeat;
 background-position: center right;
}
.mw-collapsible-arrowtoggle.mw-collapsible-toggle-collapsed {
 padding-right: 20px !important;
 background-image: url('//upload.wikimedia.org/wikipedia/commons/8/8e/MediaWiki_Vector_skin_left_arrow.svg');
 background-repeat: no-repeat;
 background-position: center right;
}

/* Collapsible Containers */
.collapsible { margin:0px; padding:0px; }
.collapsible .title, .collapsible tr:first-child th, .collapsible tr:first-child td { cursor:pointer; padding-left:16px; color:#4D4D4D; }
.collapsible.selected .title, .collapsible.selected tr:first-child th, .collapsible.selected tr:first-child td { color:#0645AD; }
.collapsible span.action { display:block; float:right; white-space:nowrap; text-align:right; height:16px; margin:auto 5px auto 0px; padding:0px; }
.collapsible span.action img { height:16px; width:16px; margin:0px; padding:0px; }

.navbox .collapseButton {          /* 'show'/'hide' buttons created dynamically */
    display:none;
}

Thanks, 4nn1l2 (talk) 06:49, 7 September 2021 (UTC)[reply]

Mon Wiktionary and Mon Wikipedia for help with defense

Status:    In progress

Anonymous IP account holder has been harassing Mon Wiktionary to this day since 15 June 2021, now, on August 27, 2021, Mon Wikipedia is being harassed again. We request that you permanently block this User:96.4.165.61 IP account from Mon Wiktionary and Mon Wikipedia. Admins from Mon Wiktionary and Mon Wikipedia are not yet proficient in using Mon Wiktionary and Mon Wikipedia, which is a weakness for Mon Wiktionary and Mon Wikipedia defense. I would like to request that you turn off editing with an IP account for Mon Wiktionary and Mon Wikipedia protection. I want to do a lot of work for Mon Wiktionary and Mon Wikipedia defense, but since I am not an administrator, I have no authority to do anything for Mon Wiktionary and Mon Wikipedia defense, if possible, I should be given some authority to defend Mon Wiktionary and Mon Wikipedia, as a Mon people, I would like to take on the responsibilities of Mon Wiktionary and Mon Wikipedia. See Wiktionary harassment evidence at the link.

  1. Mon Wiktionary evidence of harassment link
  2. Mon Wikipedia evidence of harassment link

We are very saddened by the harassment of an anonymous person, I do not want this anonymous person to bother me anymore on Mon Wiktionary and Mon Wikipedia, thanks.--咽頭べさ (talk) 12:03, 8 September 2021 (UTC)[reply]

96.4.165.61 has no contributions in Mon Wikipedia. Ruslik (talk) 20:57, 10 September 2021 (UTC)[reply]


How and where could cross wiki disruptive behavior and CU request be filed

Status:    In progress
Hello, I have recently came across a number of questionable contribution made by the IP address range 117.136.54.*.
The IP address is in itself dubious, since it belongs to China Mobile Tianjin, which mean it is inside China, and should be unable to access WMF-operated site
The IP address range have conducted a number of dubious edit deep inside multiple Wiki sites, including most recently:
  1. On 2021-09-10 created a request on Meta Wikimedia for a new Estonian language project, using a signature of User:BlueWhale, despite User:BlueWhale have never made any edits on Meta and the only edit ever made by such user were on Chinese Wikipedia in year 2005 on the Chinese Wikipedia Article of Blue Whale, and have see zero activity anywhere else, including on any Estonian projects, over the past 16 years. Also note that since @BlueWhale65: have created a number of language project creation request in recent months, the IP user might be trying to impersonate that user by making use of such signature. User:Liuxinyu970226 subsequently corrected a typo in this request.
  2. Also on 2021-09-10 the IP user on meta commented on project request "Wikisource Literary Chinese", agreeing with comment made by User:Liuxinyu970226 against me, urging me to "apologize" over my comment on possible viability of a Classical Chinese Wikisource project. The comment itself is unfriendly but not disruptive in nature, but such comment make me aware of possible relation between User:Liuxinyu970226 and edits made by the IP address range 117.136.54.*.
  3. On 2021-09-08 on Chinese Wikisource, the IP user impersonated me, adding inflammatory statements inside my comment against another user User:Liuxinyu970226. User:Liuxinyu970226 immediately reacted in 11 minutes, using the inflammatory statement added by the IP address range to issue Level 4im warning against me, but in 6 more minutes User:Liuxinyu970226 reverted that IP's edit recognizing the text was inserted by IP spammers, yet still maintain the Level 4im warning against me and changed the target to another comment I made, which now read "It's not productive to say whether the RFC can be passed or not mean who is winning or losing".
  4. On 2021-08-18 the IP address range on Commons again agreeing with a request made by User:Liuxinyu970226, on a potential copyright violation of a file uploaded by me.
  5. On 2021-07-06 the IP address range tried to edit an RFC for Russian Wikibooks, trying to modify comments signed by others, in order to add @Gzdavidwong: into the list of people being accused of breaking wiki rules there. User:Gzdavidwong have never edited in Russian Wikibooks, but is moderately active on Chinese Wikipedia and other Chinese Wikiprojects on topics related to Hong Kong, Macau, and Guangdong.
  6. Also on 2021-07-06, the user on meta attempted altering Simplified Chinese translation of 2008 Wikimedia Foundation Board election result, trying to eliminate the fact that @Wing: won the board election in 2008 who is now a sysop on Chinese Wikipedia.
  7. On 2021-07-05, the IP user on Chinese Wikisource pretended to be a sysop, removed a message by User:Gzdavidwong (The same user later accused by the IP user as participating in Russian Wikibooks conflict). The original message was trying to criticize User:Jusjih's decision and tried to warn User:Liuxinyu970226
  8. On 2021-03-02, the IP user on English Wikipedia made a comment specifically to follow up with User:Liuxinyu970226's comment on "Deletion requests for Australian road signs on Commons" in the English Wikipedia.
  9. On 2021-02-11 the IP user tried to modify somebody's unsigned comment on Commons, trying to add "Kyoto University" into party claimed to be against the status of existence of freedom of panorama in Indonesia. The IP user themselves never joined the discussion but User:Liuxinyu970226 is an active participant in the discussion.
  10. On 2021-02-10 the IP user made an comment to cite comment made by User:Liuxinyu970226 and another user there. Note that, User:Liuxinyu970226 have also responded to another request made by a similar IP address 117.136.1.99, indicating it might actually involve other IP addresses too.
  11. On 2020-04-23 on wikidata the user tried to revert a change against another user, with the change original being made by User:Liuxinyu970226, seemingly intended to be avoid being seen as repeatedly editing the same topic.
There are many more questionable edits being involved and cannot be listed out extensively.

The number of edits made by IP users in this IP range is problematic, and there are suspiciously close relationship between this IP range and User:Liuxinyu970226 that made the situation suspicious. But I am not familiar with how to resolve the situation. I would want to first perform a check user request, but since the suspicious editing behavior happened across multiple wikis, some have their own CU process and some others doesn't have their own CU process, I am not sure where should I begin with.
And then, regardless of CU result, the disruptive editing behavior exhibited by this IP range should probably be banned. And depends on CU result, maybe some other users should also be blocked from editing. But I am not certain about where to begin with with such process/
And since these IP ranges are assigned by Chinese state-owned telecommunication network operator, if their ability to access wikiprojects directly without proxy-like tools is under the order of those who also control China's website-censorship system to enable such IP accessing wikiprojects directly, then such authority can easily reassign another groups of IP to their personnel in order to overcome such blockages.
This pattern of disruptive behavior coming out of IP address accessing foreign website directly from IP address assigned to Mainland China is in line with Twitter's report finding of misinformation campaign, [1], noting some specifically unblocked IP address from Mainland China are able to access their service directly, and such accounts are mostly responsible for spam, coordinated activity, fake accounts, attributed activity, and ban evasion.
In such situation, banning only one or a few IP ranges wouldn't be able to help resolve the situation, as there are plenty of IP address being assigned to Chinese telecommunication operators, all of them state-owned, to allow them to assign those IP addresses to their subordinates freely. What further action can I request to prevent such situation from continues occurring?

--C933103 (talk) 08:43, 11 September 2021 (UTC)[reply]

For the first one, I nominated for deletion, originally I looked so simply that someone created a mis-titled RFL and moved to follow other RFLs, no idea who are the rest, I'd love to warn them. Liuxinyu970226 (talk) 09:41, 11 September 2021 (UTC)[reply]
The 6th one seems like fixing a wrong translation, but then also reverted by @WhitePhosphorus:, I don't know what happened here, as I entirely didn't watch it before, hence didn't know anything there. Asking the 8th case is also a nonsense since they're asking a question without any pro-me behaviors, but rather an unexpected question they met. --Liuxinyu970226 (talk) 09:46, 11 September 2021 (UTC)[reply]
NB: 117.136.55.130 stated at Wikidata that they are not Chinese, will this raise you from any doubts above? Note that under Wikidata P802 DR: I said "Template:Vd Clearly-than-god no consensus to keep such old-school schema. Replacement is now available." then after 19 days: "Keep Keep nghiên cứu sinh (doctoral student) is different by sinh viên (student) in Vietnamese." This is what I taught the 117.136.54.109 to say? I'm amazed with their Vietnamese-related comments. I "also taught them to create a number of match articles of 2019 Summer Universiade"? --Liuxinyu970226 (talk) 10:39, 11 September 2021 (UTC)[reply]
The 6th case does not appear to be "fixing a wrong translation". The translation of "The Election Committee announced the result [...], with Ting Chen winning the one seat available [...]" is removed without any reasons given, and "帐户" (account) is replaced with "户口" which is only used in household registration in zh-hans (however, in zh-yue accounts do be called "戶口", so perhaps this IP user has some knowledge of zh-yue). --WhitePhosphorus (talk) 11:58, 11 September 2021 (UTC)[reply]
Indeed, but regareless, I didn't saw it, so I was also surprised the details of it. Liuxinyu970226 (talk) 13:09, 11 September 2021 (UTC)[reply]
@Ruslik0: If no other stewards oppose, then I wonder if non-admin closure is okay here or not, since I still think all the problems above are locally handleable, rather than a stewardship action is needed. --Liuxinyu970226 (talk) 13:22, 12 September 2021 (UTC)[reply]
You mean you want to close this request that involves you yourself? --MF-W 20:03, 13 September 2021 (UTC)[reply]
I find your summary very credible. For Meta, I have filed a CU request at WM:RFCU. --MF-W 20:03, 13 September 2021 (UTC)[reply]
It's not credible for me because the C933103 randomly points me as "an employee of Chinese telecommunication operators", that's not right, it's possible to confirm them by calling +86-10086, +86-10010 and +86-10001, non of them know me. Liuxinyu970226 (talk) 23:15, 13 September 2021 (UTC)[reply]

OAuth permissions

Preferably permission requests should be submitted using the form from Special:OAuthConsumerRegistration.

After submitting this form, you will receive a token that your application will use to identify itself to MediaWiki. An OAuth administrator will need to approve your application before it can be authorized by other users. It is possible to request approval using {{oauthapprequest}}, please create a sub-section to this part.

A few recommendations and remarks:

  • Try to use as few grants as possible. Avoid grants that are not actually needed now.
  • Versions are of the form "major.minor.release" (the last two being optional) and increase as grant changes are needed.
  • Please provide a public RSA key (in PEM format) if possible; otherwise a (less secure) secret token will have to be used.
  • Use the JSON restrictions field to limit access of this consumer to IP addresses in those CIDR ranges.
  • You can use a project ID to restrict the consumer to a single project on this site (use "*" for all projects).
  • The email address provided must match that of your account (which must have been confirmed).

See also