|
I first registered this account - my first - April 20, 2007. Since then, I've gotten involved pretty deeply in AfD work. I see it as a chance to triage articles that are flawed, but may yet have potential. If you need access to a Wikipedia article that has been deleted, ask me. If it's not a copyright violation, libel, or personal information, and has not been deleted as a suspected biographies of living persons violation, I will userfy the article for you. Note that using the text to recreate any deleted article may automatically qualify them for speedy deletion, and copies of previously deleted content that are being used solely for long-term archival purposes may be subject to deletion because Wikipedia is not a free web host. We have a list of alternative sites which may be used to host your content. I maintain a sock account AVPW primarily for use on public networks. In the event of a compromised account, I specifically request any administrator to honor a request from AVPW to block this account, and absolve you in advance of any repercussions. To do list:
Add'l links
AB = Administrative Backlogs[edit]Administrative backlog[edit]AIV= Administrator intervention against vandalism Administrator intervention against vandalism
Reports[edit]
User-reported[edit]
CSD= Candidates for speedy deletion ; PROD= Proposed deletions
The following articles have been proposed for deletion for around 7 days: Deletion backlog {{CSD backlogs}} 7 backlognav + 2 + 5 single cat
Wikipedia files with a different name on Wikimedia Commons – No backlog currently Wikipedia files with the same name on Wikimedia Commons – 10 items Non-free files with orphaned versions more than 7 days old – 1 item Requested RD1 redactions – 19 items Expired proposed deletions of unsourced BLPs – No backlog currently UAA= Usernames for administrator attention ; RFPP= Requests for page protection Usernames for administrator attention
User-reported[edit]
Requests for page protection
Current requests for increase in protection level[edit]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.
Indefinite semi-protection: Persistent sockpuppetry – Persistent block evasion. '''[[User:CanonNi]]''' (talk • contribs) 04:19, 16 August 2024 (UTC) Reason: High level of IP unconstructive edits. DareshMohan (talk) 06:58, 16 August 2024 (UTC) Indefinite semi-protection: Important bio aricle. Lahsim Niasoh (talk) 08:30, 16 August 2024 (UTC)
Temporary semi-protection: Persistent vandalism – Ip adress vandalising the articles. Monhiroe (talk) 08:41, 16 August 2024 (UTC)
Temporary semi-protection: Persistent vandalism. Wikipedialuva (talk) 10:27, 16 August 2024 (UTC)
Reason: Protection required to prevent repeated addition of a non RS, non BLP compliant attack page. Axad12 (talk) 14:46, 16 August 2024 (UTC) Semi-protection: Consistent vandalism from IPs and new users due to the online "Ironland" movement. RyanAl6 (talk) 19:34, 16 August 2024 (UTC) Temporary create protection: Repeatedly recreated. Jdcomix (talk) 19:38, 16 August 2024 (UTC) Semi-protection: ip user persistently attempting to make a change without discussing. i believe protection might lead them to the talk page. cogsan (nag me) (stalk me) 19:57, 16 August 2024 (UTC)
Temporary pending changes: Persistent vandalism. Some1 (talk) 22:59, 16 August 2024 (UTC) Reason: High level of vandalism from IPs or SPA, attempting to promote a non-notable Youtuber called Koifish. ⁂CountHacker (talk) 23:52, 16 August 2024 (UTC) Temporary semi-protection: Persistent vandalism. Jdcomix (talk) 00:46, 17 August 2024 (UTC) Reason: Continuous IP and user vandalism of removing content - the page being viewed by many users recently due to a current event. JoshuaJ28 (talk) 01:08, 17 August 2024 (UTC) Semi-protection: Persistent vandalism – Blocked IP hopper can't stop themselves. Nswix (talk) 02:01, 17 August 2024 (UTC)
Temporary semi-protection: Persistent disruptive editing – After a COI editor wasn't permitted to add promotion to this article, they've written a blog post that is sending their users to Wikipedia. Please semiprotect to give this some time to blow over. MrOllie (talk) 03:45, 17 August 2024 (UTC) Reason: The page has more than 1000 views per day on average. Some IP and non-confirmed users keep changing the images without valid reason. It needs high level of protection so that only autoconfirmed users can edit the page (similar to Head of state page which have pending changes protection) JoshuaJ28 (talk) 04:45, 17 August 2024 (UTC) Temporary semi-protection: Disruptive editing / Unsourced content in the last few days. Kind Tennis Fan (talk) 05:24, 17 August 2024 (UTC) Indefinite semi-protection: High level of vandalism by IP addresses involving the name Wheatley2 (talk) 06:36, 17 August 2024 (UTC) Temporary semi-protection: Persistent vandalism – IP adding personal information and posting objectionable content. Thewikizoomer (talk) 06:59, 17 August 2024 (UTC)
Temporary semi-protection: Persistent vandalism – Persistent removal of logo images for multiple Paramount TV channels in Australia by IP users, including on the articles for 10 Bold Drama, 10 Peach Comedy and Nickelodeon. Yours sincerely, Bas (or TechGeek105) (talk to me) 07:35, 17 August 2024 (UTC) Reason: Persistent disruptive editing, both with IPs and socks, nearly 2 dozen edits/reverts over 6 days. Alivardi (talk) 09:58, 17 August 2024 (UTC) Reason: IP Address and @Xizx12 vandalized the disambiguation page, and other edits are irrelevant in disambiguation page. Royiswariii (talk) 10:25, 17 August 2024 (UTC) Temporary semi-protection: Persistent vandalism – Long term vandal who keeps changing IPs and vandalising the page every few days for months now. Many of their previous IPs have been blocked but they keep changing IPs. Bennv123 (talk) 11:04, 17 August 2024 (UTC) Reason: Persistent vandalism by Shurbanm (talk · contribs). I applied for intervention against vandalism, nothing. Beshogur (talk) 12:03, 17 August 2024 (UTC) Reason: Persistent addition of unsourced date information, from newly created accounts this month of August 2024. Hotwiki (talk) 12:10, 17 August 2024 (UTC)
Temporary semi-protection: Persistent vandalism by multiple IPs. PadFoot (talk) 12:28, 17 August 2024 (UTC) Reason: Constant vandalism Replayerr (talk) 14:09, 17 August 2024 (UTC) Reason: High levels of IP vandalism Replayerr (talk) 14:27, 17 August 2024 (UTC) Semi-protection: Persistent vandalism. Ratnahastin (talk) 14:58, 17 August 2024 (UTC) Indefinite extended confirmed protection:Per WP:CT/A-I.Pachu Kannan (talk) 15:05, 17 August 2024 (UTC) Indefinite extended confirmed protection: Arbitration enforcement – WP:CT/KURD. Skitash (talk) 15:25, 17 August 2024 (UTC) Indefinite extended confirmed protection: Arbitration enforcement – WP:CT/KURD. Skitash (talk) 15:29, 17 August 2024 (UTC) Reason: Request indefinite autoconfirmed or semi-protection. Dlaska, directly affiliated with LabPlot, wrote up a series of comically terrible promotional edits which obviously violated numerous guidelines and policies. When MrOllie undid these, the editor in question and/or their affiliates began using IPs to edit war their way into forcing through the (again completely unacceptable) changes, cast aspersions on MrOllie as "biased" and a "non-contributor" who should be "blocked", and sealion about the merits of their edits. When this strategy didn't work, one of the contributors to LabPlot wrote on the official blog this absolutely unhinged screed demonstrating no idea of or care for how Wikipedia is supposed to work, actively encouraging their followers to brigade, and even linking to a tweet which compared MrOllie by name to the Gestapo. Since then, more IP edits have been made trying to push these asinine changes. It's clear that there's a concerted, bad-faith effort by the LabPlot team to use sock- and meatpuppets to push through ridiculous, promotional changes to the detriment of the project and that they have every intention of pushing them through whenever they can in the hopes that nobody is looking. TheTechnician27 (Talk page) 16:04, 17 August 2024 (UTC) Temporary semi-protection: Persistent addition of unsourced or poorly sourced content – There is an IP user (with dynamic IP) keeps adding unsourced content (which probably breaks other wikipedia guidelines too) and he is not interested in discussing, so I thought making the page semi protected will help. Sports2021 (talk) 16:21, 17 August 2024 (UTC). (talk) 16:21, 17 August 2024 (UTC) Indefinite semi-protection: Sockpuppetry. — DaxServer (t·m·e·c) 17:15, 17 August 2024 (UTC) Reason: Persistent disruptive editing. 2A0E:1D47:9085:D200:1C4B:C74A:20B1:D8C1 (talk) 19:08, 17 August 2024 (UTC) Semi-protection: Persistent vandalism – Requesting protection. Mostly ip vandalism. Knitsey (talk) 19:13, 17 August 2024 (UTC) Temporary semi-protection: IP edit warring. Dell Latitude E6400 (talk) 20:11, 17 August 2024 (UTC) Temporary semi-protection: Persistent vandalism. Ravensfire (talk) 21:35, 17 August 2024 (UTC) Reason: Every time in recent months this page has been unprotected, it has been swiftly been by a party who is conducting a campaign of online harassment against the subject. That campaign is still continuing and is under a police investigation. Therefore ongoing protection would be appropriate in the meantime. EC84 (talk) 22:04, 17 August 2024 (UTC) Reason: Every time in recent months this page has been unprotected, it has been swiftly been vandalised by a party who is conducting a campaign of online harassment against the subject. That campaign is still continuing and is under a police investigation. Therefore ongoing protection would be appropriate in the meantime. EC84 (talk) 22:05, 17 August 2024 (UTC) Reason: Persistent disruptive editing by IP. Sheriff | ☎ 911 | 23:11, 17 August 2024 (UTC) Temporary semi-protection: I'm testing TW. GimmeKittens (talk) 01:02, 18 August 2024 (UTC) Reason: Persistent IP vandalism ‹hamster717🐉› (discuss anything!🐹✈️ • my contribs🌌🌠) 01:10, 18 August 2024 (UTC)
Reason: Disruptive edits by IPs again and again, IPs are treating the article and article's talk as WP:FORUM. M S Hassan (talk | contributions) 03:42, 18 August 2024 (UTC) Reason: Persistent disruptive editing by IP users. PJ Santos (talk) 03:43, 18 August 2024 (UTC) Semi-protection: BLP policy violations – Severe BLP violations. Article has been protected 4 times already and I think its time for this article to be protected for quite some time or indefinitely. 🛧Midori No Sora♪🛪 ( ☁＝☁＝✈) 04:53, 18 August 2024 (UTC) Current requests for reduction in protection level[edit]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.
Current requests for edits to a protected page[edit]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.
"Israeli military activities in the Gaza Strip remained unchanged following adoption of the resolution" needs a marker: citation needed. AmbroseVenture (talk) 18:42, 17 August 2024 (UTC) "On 28 March, the IDF shot and killed two unarmed men in central Gaza, before burying them in sand with bulldozers.[397]" needs to be altered, the source gives two contradicting stories which CNN (the source) didn't clear up. In the article AJ argues without evidence the two videos they present are from the same people, the IDF tells those were two separate incidents. This has to be cleared up to remain factual. AmbroseVenture (talk) 18:44, 17 August 2024 (UTC) Please add the following request to the page: 2A0E:1D47:9085:D200:1C4B:C74A:20B1:D8C1 (talk) 19:08, 17 August 2024 (UTC) Handled requests[edit]Protected edit requests
RFA= Requests for adminship RFP= Requests for permissions
Autopatrolled[edit]
For a third time, I'm applying for autopatrolled rights; my first request was denied in April 2023, and my second request was denied in June 2024. The reason for the first decline was that my previous articles were tagged for "notability." After that decline, I worked on bringing articles over from the Russian Wikipedia and had relatively few problems when other editors were reviewing them (I don't bring over everything from those respective pages, so I added a tag for expanding from Russian to let others know that information is still there). The reason for the second decline was that I moved one of my BLP articles back into the mainspace without changing the sourcing, and it was eventually deleted (that was a mistake on my part). Now, roughly two months later, I have had little to no problems with the other articles I have brought over. I respectfully request that I be granted the autopatrolled permission this time around, as I believe it will help lighten the NPP workload to some extent. Thanks in advance for your consideration. Losipov (talk) 20:10, 2 August 2024 (UTC)
Reviewer Aszx5000 has messaged me twice that I should be autopatrolled. I don't care for my sake, since the process works fine for me, but I don't want to be a burden on the reviewers. Please either grant or deny this status based on whatever you think is best for the community. Thanks! Jordanroderick (talk) 23:38, 8 August 2024 (UTC)
Would like to cut down on the backlog of pages that need to be reviewed while I create pages, especially as of recent where I've been working on creating pages for military battles, and Bahmani rulers. I definitely believe the pages I've created shows I am familiar with the guidelines of page notability, and especially quality. I've practiced with this being a new page patroller myself. Noorullah (talk) 00:36, 11 August 2024 (UTC)
I have created 25 new pages and would like to request the autopatrolled right. I have been a user since 2007, but have increased my writing on Wikipedia in the last 3 years. I create articles in generally non-controversial areas such as crystallography, symmetry and philately. GreatStellatedDodecahedron (talk) 13:19, 13 August 2024 (UTC) There are no outstanding requests for the confirmed flag.
Page mover[edit]
Reason for requesting page mover rights: I want to have my page mover rights extended, as I contribute to RM/TR. Was given 3mo trial and it will end on August 20. ToadetteEdit! 08:30, 29 July 2024 (UTC)
I'm an active AfC reviewer, and I spend a lot of time patrolling new pages. I often draftify articles that are not sourced or need additional sources (over 250 articles so far). Having this right would be super useful and help reduce the number of R2 tags for admins in the backlog. I also have experience in WP:RM, and I'd like to request page mover rights for non-controversial tasks. Thank you, Waqar💬 16:39, 12 August 2024 (UTC)
Pending changes reviewer[edit]
I have been monitoring recent changes on pages for a while now AlexBobCharles (talk) 08:36, 2 August 2024 (UTC)
I’ve been editing for a little while now, I’ve requested page protection and reverted edits which are not appropriate on various pages. I am pretty devoted to editing on Wikipedia and I have an extensive Watchlist so I think this permission would be useful. Adriazeri (talk) 22:55, 4 August 2024 (UTC)
I've been monitoring the pages in Wikipedia for a long time. I try my best to review new changes, revert any vandalism and provide authenticity. This permission will help me review the pages more fluently. MSouvik01 (talk) 21:14, 9 August 2024 (UTC)
Did all the requirements and patrolled the recent changes page for a rotating number of days. My account also meets all the requirements.
I've been creating and monitoring articles in Wikipedia for a long time and its time to a new step in this great community. TheFrenchKing (talk) 21:05, 12 August 2024 (UTC)
Rollback[edit]
I have been patrolling recent changes and combating vandalism for a little over a month. I've been primarily using Twinkle and I would like to request rollback privileges to use other tools such as Huggle. I understand the importance of leaving users a notice whenever their edits are reverted. Jiffles1 (talk) 22:30, 13 August 2024 (UTC)
I had this as admin, I would still find it useful. — Naomi Amethyst 03:11, 16 August 2024 (UTC)
I have used Twinkle to revert vandalism mostly from the recent changes page for a while now and warn users afterwards. Twinkle is not sufficient for me on longer articles because of my sluggish internet connection. Reverts I make with Twinkle may take up to ten seconds, even with ethernet connected to my router. Rollback permissions would be greatly appreciated to make edits faster and save time. I can be trusted with rollback permissions as I have been actively reverting vandalism with a few breaks for school since July 2023, consistantly warning editors with the templates that Twinkle offers. I understand what is and what is not vandalism, and believe that I have what it takes to be trusted with the rollback tool. Thank you, ItsCheck (talk) 03:10, 17 August 2024 (UTC)
Hi, I am familiar with helpful tools such as SWViewer and Twinkle and use them frequently, as well as the relevant guidelines for fighting vandalism. You can see from my contribution history that I always notify the users whose edits I am reverting. Greetings, MrBenjo (talk) 20:12, 17 August 2024 (UTC) There are no outstanding requests for template editor. Footer[edit]Policies and links
Committed identity: 5e0a9af339f30221a08fa86264cf1a81e3637ef17bd7ba87260c63b0fea3cdb0b55f545f061dd97184aa4061626c8c41b7237f4b18ccfdd096bff83e92ce9fc5 is a SHA-512 commitment to this user's real-life identity.
I copied this source code from someone's user page I liked. I did not save the name. Thank you, whomever you are. |
