desk


Requests for adminship and bureaucratship update
No current discussions. Recent RfAs, recent RfBs: (successful, unsuccessful)
Admin statistics
Action Count
Edits 21366
Edits+Deleted 25360
Pages deleted 15561
Revisions deleted 6
Pages restored 118
Pages protected 417
Pages unprotected 21
Protections modified 16
Users blocked 1248
Users reblocked 27
Users unblocked 18
User rights modified 13
Users created 1


Purge the cache of this page


commenting template

Result Shorthand Longhand
Checking: :{{AIV|chk}} :{{AIV|check}}
wait :{{AIV|wt|Z}} :{{AIV|wait|Z}}
Warned user. :{{AIV|w}} :{{AIV|warn}}
Insufficient recent activity to warrant a block. :{{AIV|i}} :{{AIV|ins}}
No vandalism since final warning. Re-report if this user resumes vandalising. :{{AIV|f}} :{{AIV|nfw}}
Stale warning. Last warning was issued Y ago. :{{AIV|ow|Y}} :{{AIV|oldwarn|Y}}
Will actively monitor user. :{{AIV|m}} :{{AIV|monitor}}
Question: :{{AIV|q}} :{{AIV|ques}}
This noticeboard is for obvious vandals and spammers only. Consider taking this report to Administrators' noticeboard/Incidents. :{{AIV|a}} :{{AIV|ani}}
This noticeboard is for obvious vandals and spammers only. Consider taking this report to Usernames for administrator attention. :{{AIV|u}} :{{AIV|uaa}}
This noticeboard is for obvious vandals and spammers only. Consider taking this report to Requests for page protection. :{{AIV|r}} :{{AIV|rpp}}
This noticeboard is for obvious vandals and spammers only. Consider taking this report to Sockpuppet investigations. :{{AIV|sp}} :{{AIV|ssp}}
Note: :{{AIV|n}} :{{AIV|note}}
Note: IP addresses are generally not blocked indefinitely. Please see the blocking policy for more information. :{{AIV|in}} :{{AIV|indef}}
Appears to be a shared IP address, used by multiple users. :{{AIV|s}} :{{AIV|shared}}
User has been inappropriately warned. 4im warnings are appropriate for severe vandalism and defamation only. :{{AIV|4im}} :{{AIV|onlywarn}}
Content dispute. Consider dispute resolution. :{{AIV|c}} :{{AIV|cont}}
User has been incorrectly or insufficiently warned. Re-report if the user resumes vandalising after being warned sufficiently. :{{AIV|ns}} :{{AIV|new}}
Blocks are preventative, not intended to be used as punishment. :{{AIV|np}} :{{AIV|notpunish}}
Edits are not vandalism. Please ensure recent edits constitute vandalism before re-reporting. :{{AIV|nv}} :{{AIV|notvandal}}
Page deleted. :{{AIV|d}} :{{AIV|del}}
Stale report. User has not edited in X. :{{AIV|e|X}} :{{AIV|stale|X}}
Report was good at the time, but is now stale. (X since last edit) Re-report if this user resumes vandalising. :{{AIV|sn|X}} :{{AIV|nowstale|X}}
merge :{{AIV|me}} :{{AIV|merge}}


Reports

User-reported

Candidates for speedy deletion Entries
User requested -1
Empty articles 0
Nonsense pages -3
Spam pages -2
Notability not asserted 5

The following articles have been proposed for deletion for at least 5 days:
( source / chronological order )

Usernames for administrator attention

commenting template

Result Shorthand Longhand
Wait until the user edits. :{{UAA|wt}} :{{UAA|wait}}
Being discussed with the user. :{{UAA|d}} :{{UAA|disc}}
drfcn :{{UAA|dr}} :{{UAA|drfcn}}
aiv :{{UAA|v}} :{{UAA|aiv}}
ani :{{UAA|a}} :{{UAA|ani}}
rpp :{{UAA|r}} :{{UAA|rpp}}
ssp :{{UAA|sp}} :{{UAA|ssp}}
talk :{{UAA|uw}} :{{UAA|talk}}
Not a blatant violation of the username policy. Please discuss this with the user first, and consider opening a community discussion at Requests for comment/User names if they disagree with your concerns. :{{UAA|rc}} :{{UAA|rfcn}}
notb :{{UAA|b}} :{{UAA|notb}}
Question: :{{UAA|q}} :{{UAA|question}}
Note: :{{UAA|n}} :{{UAA|note}}
Stale: This account has not been used in the last 2–3 weeks. :{{UAA|e}} :{{UAA|stale}}
merge :{{UAA|me}} :{{UAA|merge}}



User-reported

Requests for page protection

commenting template

Result Code Normalized code
Semi-protected {{RFPP|s}} {{RFPP|semi}}
Fully protected {{RFPP|p}} {{RFPP|full}}
Move protected {{RFPP|m}} {{RFPP|move}}
Creation protected {{RFPP|t}} {{RFPP|salt}}
Done {{RFPP|do}} {{RFPP|done}}
Declined {{RFPP|d}} {{RFPP|deny}}
Declined – Not enough recent disruptive activity to justify protection. {{RFPP|nea}} {{RFPP|nact}}
DeclinedPages are not protected preemptively. {{RFPP|np}} {{RFPP|npre}}
{{RFPP|fa}} {{RFPP|mpfa}}
User(s) blocked. {{RFPP|b}} {{RFPP|bloc}}
Unprotected {{RFPP|u}} {{RFPP|unpr}}
Not unprotected {{RFPP|nu}} {{RFPP|noun}}
Already unprotected. {{RFPP|au}} {{RFPP|isun}}
Already protected. {{RFPP|ap}} {{RFPP|ispr}}
Already done. {{RFPP|ad}} {{RFPP|isdo}}
Question: {{RFPP|q}} {{RFPP|ques}}
Note: {{RFPP|n}} {{RFPP|note}}


Current requests for increase in protection level

Request protection of a page, or increasing the protection level

Place requests for new or upgrading pending changes, semi-protection, full protection, move protection, create protection, template editor protection, or upload protection at the BOTTOM of this section. Check the archive of fulfilled and denied requests or, failing that, the page history if you cannot find your request. Only recently answered requests are still listed here.


Reason: This article has faced ongoing disruptions by IP users for several months. They repeatedly damage the infobox template and add duplicate parameters. Since there are no significant daily updates needed for this person's life, using edit requests would be a more efficient solution for everyone involved. Sheriff | ☎ 911 | 13:54, 30 September 2024 (UTC)

Permanent extended-confirmed protection Contentious topic, fits well under WP:CT/HORN. Back and forth edit warring stretching back to multiple months. Previous temporary extended-confirmed protections have expired and edit warring has resumed since then. Ecrusized (talk) 14:40, 30 September 2024 (UTC)

  • Automated comment: A request for protection/unprotection for one or more pages in this request was recently made, and was denied at some point within the last 8 days.—cyberbot ITalk to my owner:Online 14:45, 30 September 2024 (UTC)
Ecrusized, YOU started this edit war, and you are not discussing with ANYONE to resolve it. I don't know how else i can tell you to come up with conensus with me, @Replayerr, or anyone else, I have went on your talk page to try to discuss this with you, Please answer!!! Zabezt (talk) 18:30, 30 September 2024 (UTC)

Permanent extended-confirmed protection Contentious topic, fits well under WP:CT/HORN. Back and forth edit warring stretching back to multiple months. Previous temporary extended-confirmed protections have expired and edit warring has resumed since then. Ecrusized (talk) 14:40, 30 September 2024 (UTC)

  • Automated comment: A request for protection/unprotection for one or more pages in this request was recently made, and was denied at some point within the last 8 days.—cyberbot ITalk to my owner:Online 14:45, 30 September 2024 (UTC)
Ecrusized, YOU started this edit war, and you are not discussing with ANYONE to resolve it. I don't know how else i can tell you to come up with conensus with me, @Replayerr, or anyone else, I have went on your talk page to try to discuss this with you, Please answer!!! Zabezt (talk) 18:30, 30 September 2024 (UTC)

Reason: High level Ip vandalism and many unsourced edits. Sush150 (talk) 16:23, 30 September 2024 (UTC)

Indefinite extended confirmed protection: Per WP:CT/A-I. Pachu Kannan (talk) 16:29, 30 September 2024 (UTC)

Temporary semi-protection: Persistent addition of unsourced or poorly sourced content – IP editors repeatedly adding unsourced names of competitors to articles. Show broadcasts in about a week so the list will be known by then, but it's pure guesswork and speculation without any sources supporting. Ravensfire (talk) 17:09, 30 September 2024 (UTC)

  • Adding Bigg Boss (Tamil TV series) for the same problems, often from the editors. Ravensfire (talk) 21:56, 30 September 2024 (UTC)

Temporary extended confirmed protection: Persistent vandalism – User:Mosalman786 (semi-confirmed user) has been adding spam links to external sites. Look like an account used only for link-spamming. Vestrian24Bio (TALK) 17:31, 30 September 2024 (UTC)

Semi-protection: Persistent vandalism. Filmssssssssssss (talk) 17:54, 30 September 2024 (UTC)

Semi-protection: Persistent vandalism – Previous protection applied 29 June for 3 months. The day after it expired (today), "Nicolle A. Morea" began adding her "marriage" back. Please apply at least another 3 months, if not longer; apparently the vandal has a long attention span. Schazjmd (talk) 20:28, 30 September 2024 (UTC)

  • Automated comment: A request for protection/unprotection for one or more pages in this request was recently made, and was denied at some point within the last 8 days.—cyberbot ITalk to my owner:Online 20:34, 30 September 2024 (UTC)

Extended confirmed protection: Persistent vandalism – Vandalism continues after page protection lifted.   Aloha27  talk  20:38, 30 September 2024 (UTC)

Reason: WP:PIA-related article with recent contentious IP edit Vyvagaba (talk) 20:59, 30 September 2024 (UTC)

Extended confirmed protection: Arbitration enforcement – Contentious topic etc. AntiDionysius (talk) 21:00, 30 September 2024 (UTC)

Current requests for reduction in protection level

Request unprotection of a page, or reducing the protection level

Before posting, first discuss with the protecting admin at their talk page. Post below only if you receive no reply.

  • To find out the username of the admin who protected the page click on "history" at the top of the page, then click on "View logs for this page" which is under the title of the page. The protecting admin is the username in blue before the words "protected", "changed protection level" or "pending changes". If there are a number of entries on the log page, you might find it easier to select "Protection log" or "Pending changes log" from the dropdown menu in the blue box.
  • Requests to downgrade full protection to template protection on templates and modules can be directed straight here; you do not need to ask the protecting admin first.
  • Requests for removing create protection on redlinked articles are generally assisted by having a draft version of the intended article prepared beforehand.
  • If you want to make spelling corrections or add uncontroversial information to a protected page please add {{Edit fully-protected}} to the article's talk page, along with an explanation of what you want to add to the page. If the talk page is protected please use the section below.
Check the archives if you cannot find your request. Only recently answered requests are still listed here.

Semi-protection: A few months have passed, and this article could benefit from allowing newer users to improve it. Disruption from semi-confirmed users is low-risk at this point. DarmaniLink (talk) 18:00, 30 September 2024 (UTC)

Not unprotected. As an Arbitration Enforcement action, this cannot be unprotected via a request here. See WP:AE for information on how to appeal. Daniel Quinlan (talk) 18:06, 30 September 2024 (UTC)

Reason: The page was protected due to valid concerns on sockpuppetry. However, Articles for Creation by its very nature is designed for "any editor" to request articles (and by extension, redirects). I think there should be a warning on watching for sock behavior, but that's beyond the scope of this decrease request. @NinjaRobotPirate: added the page protection just a few hours ago as of writing this. LR.127 (talk) 18:16, 30 September 2024 (UTC)

Not unprotected. The protection is short-term, expiring tomorrow. Short term semiprotection is appropriate to prevent disruption. We occasionally protect article talk pages for the same reason, which are also intended for "any editor". ~Anachronist (talk) 18:30, 30 September 2024 (UTC)

Reason: Because it needs updating as the evidence now shows this was a directed government plan and President Trump and his supporters did NOT intend and insurrection but were led on by government operatives to enter the capitol building. Its all on video and government records as is the General Milley's testimony that the President requested National Guard help well in advance of 6 Jan. 2605:59C8:4300:1308:2076:C89B:A86F:2B43 (talk) 20:17, 30 September 2024 (UTC)

Current requests for edits to a protected page

Request a specific edit to a protected page
Please request an edit directly on the protected page's talk page before posting here

Ideally, requests should be made on the article talk page rather than here.

  • Unless the talk page itself is protected, you may instead add the appropriate template among {{Edit protected}}, {{Edit template-protected}}, {{Edit extended-protected}}, or {{Edit semi-protected}} to the article's talk page if you would like to make a change rather than requesting it here. Doing so will automatically place the page in the appropriate category for the request to be reviewed.
  • Where requests are made due to the editor having a conflict of interest (COI; see Wikipedia:Suggestions for COI compliance), the {{Edit COI}} template should be used.
  • Requests to move move-protected pages should be made at Wikipedia:Requested moves, not here.
  • If the discussion page and the article are both protected preventing you from making an edit request, this page is the right place to make that request. Please see the top of this page for instructions on how to post requests.
  • This page is not for continuing or starting discussions regarding content should both an article and its discussion page be protected. Please make a request only if you have a specific edit you wish to make.


Handled requests

A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.


WP:RFPERM (rollback)

Rollback

I have been working to revert vandalism for some time now, mostly patrolling Recent changes. I have used Twinkle and RedWarn to revert vandalism and warn vandals. Rollback rights would make it easier for me to revert obvious vandalism. Thanks. Charliehdb (talk) 10:57, 28 September 2024 (UTC)

I see that you are failing to consistently warn editors when you revert their edits (e.g. 1, 2, 3). Why? It's important to leave a notification for every revert you make. Are you aware that we have tools such as Twinkle or Ultraviolet that make this extremely easy? -Fastily 08:27, 30 September 2024 (UTC)
@Fastily: Thanks for pointing it out. I assure you that I will warn all vandals from now on. I hope you give me Rollback rights. Thanks. Charliehdb (talk) 12:40, 30 September 2024 (UTC)

I have been reverting edits and warning users by patrolling recent changes for almost two months now. I have been using Twinkle to revert edits but manually warned users. I have consistently warned users most of the time after reverting their edits. I have been patrolling recent changes since 8 August 2024. I think getting Rollback rights would make it easier to revert edits or vandalism. Thank you. PEPSI697 (💬📝) 05:49, 30 September 2024 (UTC)

I see that you are failing to consistently warn editors when you revert their edits (e.g. 1, 2, 3). Why? It's important to leave a notification for every revert you make. Are you aware that we have tools such as Twinkle or Ultraviolet that make this extremely easy? -Fastily 08:27, 30 September 2024 (UTC)
@Fastily: Thank you for the response, I promise to consistently warn users after reverting edits. Please also check the tags that I use Twinkle to revert edits as well. Thank you. PEPSI697 (💬📝) 13:00, 30 September 2024 (UTC)

Reason for requesting rollback rights: I have achieved 200 mainspace edits and I am ready to be on Wikipedia's Anti-Vandal task force! I can use tools like AntiVandal, and of course continue to use Twinkle and Ultraviolet. I love patrolling Recent Changes and cant wait to join this exciting opportunity! Cooldudeseven7 (Discuss over a cup of tea?) 14:48, 30 September 2024 (UTC)

 Automated comment This user has had 1 request for rollback declined in the past 90 days ([2]). MusikBot talk 14:50, 30 September 2024 (UTC)

There are no outstanding requests for account creator.



30 September 2024