User talk:NinjaRobotPirate

Did you know that F5 is the "generate drama" key? Try it! Every time you press it, more drama is auto-generated on Wikipedia.

Note: I rarely check my email, so if you send me something important, you should probably let me know.

Bored? Check out User:NinjaRobotPirate/Games for a list of video games that are probably notable. I listed most of the sources, so you don't even have to find them.

Administrators' newsletter – June 2025

News and updates for administrators from the past month (May 2025).

Administrator changes

Interface administrator changes

0xDeadbeef

CheckUser changes

L235

Oversight changes

L235

Guideline and policy news

An RfC is open to determine whether the English Wikipedia community should adopt a position on AI development by the WMF and its affiliates.

Technical news

A new feature called Multiblocks will be deployed on English Wikipedia on the week of June 2. See the relevant announcement on the administrators' noticeboard.
History merges performed using the mergehistory special page are now logged at both the source and destination, rather than just the source as previously, after this RFC and the resolution of T118132.

Arbitration

An arbitration case named Indian military history has been opened. Evidence submissions for this case close on 8 June.

Miscellaneous

Voting for the Universal Code of Conduct Coordinating Committee (U4C) election is open until 17 June 2025. Read the voting page on Meta-Wiki and cast your vote here!
An Articles for Creation backlog drive is happening in June 2025, with over 1,600 drafts awaiting review from the past two months. In addition to AfC participants, all administrators and new page patrollers can help review using the Yet Another AFC Helper Script, which can be enabled in the Gadgets settings. Sign up here to participate!
The Unreferenced articles backlog drive is happening in June 2025 to reduce the backlog of articles tagged with {{Unreferenced}}. You can help reduce the backlog by adding citations to these articles. Sign up to participate!

Sent by MediaWiki message delivery (talk) 17:17, 6 June 2025 (UTC)[reply]

Vietnam

Hi NinjaRobotPirate, it's been well over 4 years since you placed the Vietnam article under extended-confirmed protection due to sockpuppetry. Do you really think the current protection level is still necessary to this day? The Mexico article was also extended-confirmed protected in 2019 for the same reason, but had since been downgraded to semi-protection on December last year. Perhaps it's time to downgrade the protection level of this article to semi as a trial, considering the fact that it has gained just slightly less views than Mexico in the past year (see here)? If you still think extended-confirmed protection is needed specifically for this article, then why aren't the other Southeast Asian country articles seeing the blue lock? For example, Singapore has gained nearly twice as more daily views than Vietnam in the past year (see here), but is only fine with semi-protection. How come Laos completely lacks edit protection altogether? I'm still okay if the blue lock is still necessary here, given the fact the Vietnamese version of this article is also under its form of extended-confirmed protection. BriDash9000 (talk) 08:00, 8 June 2025 (UTC)[reply]

It looks like there have been some blanking sprees in Laos, too. It looks like other people are aware of it, so maybe they'll protect the article if it starts up again. Vietnam has been troublesome because blanking sprees happen in it when the protection expires. Thus, it's set to not expire. People can still request edits at Talk:Vietnam. It looks like activity is picking up somewhat on the talk page since the last time I looked, but it's still sparse, and I don't think it would be a good idea to unprotect the article while sock puppets are still active. The last edit to the talk page was reverted for block evasion. Admins who are curious why it's protected can look at my userpage on the private CheckUser Wiki. NinjaRobotPirate (talk) 14:05, 8 June 2025 (UTC)[reply]