Wikipedia:Requests for page protection
 | This page has a backlog that requires the attention of one or more administrators. Please change this notice to {{No admin backlog}} when the backlog is cleared. |
| Requests for page protection | ||||||||
|---|---|---|---|---|---|---|---|---|
|
This page is for requesting that a page, file or template be protected. Please read up on the protection policy. Full protection is used to stop edit warring between multiple users or to prevent vandalism to high-risk templates; semi-protection and pending changes are usually used only to prevent IP and new user vandalism (see the rough guide to semi-protection); and move protection is used to stop pagemove revert wars. Extended confirmed protection is used where semi-protection has proved insufficient (see the rough guide to extended confirmed protection) After a page has been protected, the protection is listed in the page history and logs with a short description indicating why it was protected, and the article is listed on Special:Protectedpages. Further discussion should take place on the Talk page of the article. In the case of full protection due to edit warring, admins do not revert to specific versions of the page, except to get rid of obvious vandalism. Note: Editors should not consider requesting page protection as a method for continuing an argument from elsewhere nor as a venue for starting a new discussion regarding article content. If a request contains excessive argument, appears to be intended to resolve a content dispute, includes personal attacks or uncivil comments, or has any other unrelated discussion, it will be removed from this page and no action will be taken.
| ||||||||
| 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 |
Current requests for increase in protection level
Request protection of a page, or increasing the protection level
|
Mikoyan-Gurevich MiG-15
Temporary full protection: Content dispute/edit warring – Several IPs (obviously the same person) have been replacing "would score" with "scored", making false claims that the former is grammatically incorrect. ZLEA T\C 00:52, 28 June 2022 (UTC)
- @ZLEA: I have a sneaking suspicion that it may be WP:BKFIP, but it's interesting that you would revert them before coming here requesting protection. Is the change imposed by them incorrect in any way? It is less awkward. Sdrqaz (talk) 13:09, 28 June 2022 (UTC)
- Sdrqaz You're not the first one to suspect an LTA. One of the IPs had also been performing similar edits. While the change itself is not incorrect, the IPs have a history of making unnecessary edits, usually related to tense, to articles on Soviet fighter aircraft. Given the IPs' edit summaries, such as "The past tense of score is "scored" - remember, it's not rocket science; it's English (although I understand that's a fine distinction for some).", display a lack of understanding of the English language, I view this as a case of persistent disruptive editing. Pinging BilCat, who also has experience with this set of IPs. - ZLEA T\C 14:33, 28 June 2022 (UTC)
Demons Protected by Angels
Indefinite semi-protection: Persistent sockpuppetry – This redirect[1] was requested by block-evading User:Rishabisajakepauler using IPs from Texas. This is an end-run around the inability of IPs to create articles. He has done it many times before; see Wikipedia_talk:WikiProject Articles for creation/Archive 50#Banned user gaming the system of redirects to create music articles. The request was made in this pair of edits. Also needing the same indefinite protection is the redirect Crazy Tings.[2] Binksternet (talk) 22:23, 28 June 2022 (UTC)
Note: Binksternet, I think you linked to the wrong page. El_C 11:28, 29 June 2022 (UTC)
- Only in the sense that the redirects went to their redirected pages. I added two non-redirecting links. Binksternet (talk) 14:40, 29 June 2022 (UTC)
Alfred Kinsey
Temporary extended confirmed protection: Persistent disruptive editing – WP:PROFRINGE edits by various IPs and newbie accounts. tgeorgescu (talk) 05:40, 29 June 2022 (UTC)
Dimasa Kingdom
Reason: High level of IP vandalism and possible WP:BE. Chaipau (talk) 12:17, 29 June 2022 (UTC)
Nelson Piquet
Semi-protection: Persistent vandalism – Vandalism continued immediately after previous protection expired. SSSB (talk) 12:43, 29 June 2022 (UTC)
FC Metz
Temporary semi-protection: Persistent vandalism – Persistent vandalism over several days from two IP's and at least two new accounts - recommend a semi protect for one week. MaxnaCarta (talk) 13:06, 29 June 2022 (UTC)
Kabhi Eid Kabhi Diwali (film)
Semi-protection: Persistent disruptive editing – IP vandalism. ManaliJain (talk) 13:12, 29 June 2022 (UTC)
Aurangabad
Temporary extended confirmed protection: Persistent disruptive editing – Few hours ago the official name of the city has been changed. IPs are changing the WP:COMMONNAME [3], [4] as well as in older revisions. Kindly protect it. Fylindfotberserk (talk) 13:41, 29 June 2022 (UTC)
Art Simone
Temporary semi-protection: Persistent vandalism – Vandalism. --Another Believer (Talk) 13:48, 29 June 2022 (UTC)
2022 monkeypox outbreak in the United Kingdom
Reason: Persistent IP vandalism. Hey man im josh (talk) 14:07, 29 June 2022 (UTC)
User(s) blocked. Rangeblocked 2601:40:3:0:0:0:0:0/51. OhNoitsJamie Talk 16:03, 29 June 2022 (UTC)
2022 monkeypox outbreak in Canada
Reason: Persistent IP vandalism. Hey man im josh (talk) 14:08, 29 June 2022 (UTC)
- User(s) blocked. Rangeblocked 2601:40:3:0:0:0:0:0/51. OhNoitsJamie Talk 16:03, 29 June 2022 (UTC)
Umran Malik
Reason: Continued disruption of either removing sources or changing text without sourcing on this BLP. Page has been protected twice previously. Lugnuts Fire Walk with Me 14:13, 29 June 2022 (UTC)
Tim Drake
Temporary semi-protection: Persistent vandalism – Unexplained removal of content by two IPs (same location). No use of edit summaries or talk page. Firefangledfeathers (talk / contribs) 14:52, 29 June 2022 (UTC)
- User(s) blocked. Partial-blocked on range, warned another IP. OhNoitsJamie Talk 15:59, 29 June 2022 (UTC)
Eoin Morgan
Temporary semi-protection: Persistent disruptive editing – subject retired from only international cricket, but there is a rise in edits calling him 'former'. Vandalism as well. Kpddg (talk) 15:05, 29 June 2022 (UTC)
Roger Redgate
Temporary semi-protection: BLP policy violations – Repeated insertion of unsourced material. Toddst1 (talk) 15:13, 29 June 2022 (UTC)
Sam Houser
Semi-protection: Persistent addition of unsourced or poorly sourced content. IceWelder [✉] 15:37, 29 June 2022 (UTC)
Declined – Warn the user appropriately then report them to AIV or ANI if they continue. - Gave IP final warning. OhNoitsJamie Talk 15:54, 29 June 2022 (UTC)
University of Glasgow
Temporary semi-protection: Persistent vandalism. Storchy (talk) 15:39, 29 June 2022 (UTC)
Graham Skidmore
Temporary semi-protection: Persistent vandalism – Pointless IP edits moving things around for no benefit and the sake of it. Joseph2302 (talk) 15:42, 29 June 2022 (UTC)
- Declined – Warn the user appropriately then report them to AIV or ANI if they continue. OhNoitsJamie Talk 16:06, 29 June 2022 (UTC)
Australia_(continent)
Reason: Keeps getting vandalized. Users keep changing the instances of the word "Australia" to "Morbius". ProblemOfficerss (talk) 16:08, 29 June 2022 (UTC)
Aurangabad
Reason: High level of consistent IP vandalism on this page. IPs are causing disruption. Request to have page protected with access to confirmed users only for atleast 2 weeks or a month. MehmoodS (talk) 16:18, 29 June 2022 (UTC)
1988
Temporary semi-protection: No reason for doubtful anon and unconfirmed IPs. Dolfi2000 (talk) 16:34, 29 June 2022 (UTC)
Donkey Squads (Korean War)
Semi-protection: Persistent disruptive editing – Six weeks of IP-hopping attempts to change "Koreans" to "North Korean defectors". No response to user talk page warnings or article talk page thread. Meters (talk) 16:41, 29 June 2022 (UTC)
Sudarshan News
Temporary semi-protection: Persistent vandalism. Aman Kumar Goel (Talk) 16:51, 29 June 2022 (UTC)
Kelly Piquet
Temporary semi-protection: Persistent Vandalism. Father Nelson Piquet caught in controversy which is leaking out to this article in the form of persistent vandalism and BLP violations. TylerBurden (talk) 17:05, 29 June 2022 (UTC)
Romanians
Temporary semi-protection: Some dude in Belgium got rejected by a Romanian girl recently [9] [10] [11]. Super Ψ Dro 17:06, 29 June 2022 (UTC)
Maharashtra Legislative Assembly
Temporary extended protection: Content Dispute/Edit Warring. Users changing data without WP:RS. Floor test in State legislature due on 11 July. Venkat TL (talk) 17:09, 29 June 2022 (UTC)
Hersheypark
Reason: High levels of IP vandalism 45BearsFan (talk) 17:29, 29 June 2022 (UTC)
- Declined – Not enough recent disruptive activity to justify protection. Please don't post to this board unless you understand the criteria for protection. OhNoitsJamie Talk 17:32, 29 June 2022 (UTC)
Osmanabad district
Temporary semi-protection: Persistent addition of unsourced or poorly sourced content. Dove's talk (talk) 17:39, 29 June 2022 (UTC)
- @OhNoitsJamie: Dove's talk (talk) 17:40, 29 June 2022 (UTC)
- IPs changing WP:COMMONNAME of the article [12] [13] [14] [15] [16] [17]. - Fylindfotberserk (talk) 17:47, 29 June 2022 (UTC)
Swami Karpatri
Reason: High level of IP vandalism. 2409:4041:D04:B6F9:D424:3D2C:9A42:3E5C (talk) 17:39, 29 June 2022 (UTC)
Osmanabad
Semi-protection: Persistent addition of unsourced or poorly sourced content. Dove's talk (talk) 17:42, 29 June 2022 (UTC)
Current requests for reduction in protection level
Request unprotection of a page, or reducing the protection level
|
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 |
Handled requests
A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.