Wikipedia:Requests for page protection
This page has an administrative backlog that requires the attention of willing administrators. Please replace this notice with {{no admin backlog}} when the backlog is cleared. |
Welcome—request protection of a page, file, or template here. | ||
---|---|---|
Before requesting, read 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 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, it is listed in the page history and logs with a short rationale, and the article is listed on Special:Protectedpages. In the case of full protection due to edit warring, admins should not revert to specific versions of the page, except to get rid of obvious vandalism.
Request protection of a page, or increasing the protection level
Request unprotection of a page, or reducing the protection level
Request a specific edit to a protected page
Please request an edit directly on the protected page's talk page before posting here |
2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
Current requests for increase in protection level
Place requests for new or upgrading of article protection, upload protection, or create 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: Dear Wikipedia Administrators, I am writing to request protection for the Wikipedia page [Kundalpur Jain Temple (Bade Baba)] due to persistent vandalism and misinformation being added by certain individuals. The temple is a highly significant religious site for followers of the Digambar sect of Jainism, yet the page has repeatedly been altered with incorrect information, likely motivated by sectarian bias.
Nature of the Issue
1.Misinformation on Managing Body: The temple is managed by Shri Digambar Jain Atishay Kshetra Kundalpur Public Trust, but vandals have changed this to Shri Shwetambar Jain Atishay Kshetra Kundalpur Public Trust, which is factually incorrect.
2.Religious and Cultural Sensitivity: The temple holds immense importance for the Digambar Jain community. The repeated alterations appear to stem from hate or jealousy, which disrespects the faith and beliefs of millions.
Evidence of Vandalism
https://en.wikipedia.org/w/index.php?title=Bade_Baba_Temple&diff=1270028436&oldid=1268410418
16:28, 9 January 2025 User12231
15:40, 17 January 2025 Uts v Jain
Request for Protection
Given the sensitivity of the topic and the repeated vandalism, I kindly request:
1. Semi-protection: Restrict edits to registered and confirmed users.
2. Long-term protection: Given the likelihood of continued attempts at misinformation, I request protection for an extended period.
This will help ensure that the article maintains its accuracy and neutrality, in line with Wikipedia’s guidelines. Protecting this page would not only prevent further disruption but also respect the sentiments of the Jain community, particularly the Digambar sect.
Thank you for your attention to this matter. Please let me know if further details or evidence are needed.
Sincerely,
Anonymous 92.99.127.127 (talk) 12:43, 18 January 2025 (UTC)
- Forgiving the format and length here, you do realize that you will be unable to edit the article if it gets semi-protected? Daniel Case (talk) 07:01, 19 January 2025 (UTC)
Temporary semi-protection: Persistent sockpuppetry – https://en.wikipedia.org/wiki/Wikipedia:Sockpuppet_investigations/Oriental_Aristocrat. - Ratnahastin (talk) 12:56, 18 January 2025 (UTC)
- Note to admin: the OP has to explain why they are redirecting an article edited by multiple editors. Also, I see it was created by some editor (Mfarazbaig) when they weren't under any block or ban sanction. 39.34.145.168 (talk) 13:05, 18 January 2025 (UTC)
- Semi-protected for a period of three months, after which the page will be automatically unprotected. How many editors worked on the article, and who created and whether they were blocked at the time, has no bearing on whether an article is redirectified or not. Daniel Case (talk) 07:04, 19 January 2025 (UTC)
- @Daniel Case: So you are saying the article is not notable? The redirection is done entirely based on some non-existent policy and that's okay. 39.34.146.22 (talk) 07:13, 19 January 2025 (UTC)
- See WP:INVOLVE. Daniel Case (talk) 07:16, 19 January 2025 (UTC)
- That's an essay. Please state a policy to justify your action. 39.34.146.22 (talk) 07:28, 19 January 2025 (UTC)
- See WP:INVOLVE. Daniel Case (talk) 07:16, 19 January 2025 (UTC)
- @Daniel Case: So you are saying the article is not notable? The redirection is done entirely based on some non-existent policy and that's okay. 39.34.146.22 (talk) 07:13, 19 January 2025 (UTC)
- Semi-protected for a period of three months, after which the page will be automatically unprotected. How many editors worked on the article, and who created and whether they were blocked at the time, has no bearing on whether an article is redirectified or not. Daniel Case (talk) 07:04, 19 January 2025 (UTC)
Temporary semi-protection: Persistent disruptive editing. Shadow4dark (talk) 12:58, 18 January 2025 (UTC)
- Semi-protected for a period of six months, after which the page will be automatically unprotected. Daniel Case (talk) 07:06, 19 January 2025 (UTC)
Semi-protection: Persistent vandalism – unsourced and disruptive edits by IPs and new accounts. Sid95Q (talk) 14:29, 18 January 2025 (UTC)
- Semi-protected indefinitely. Daniel Case (talk) 07:09, 19 January 2025 (UTC)
Temporary semi-protection: Persistent vandalism. --Min☠︎rax«¦talk¦» 15:57, 18 January 2025 (UTC)
- Semi-protected for a period of one week, after which the page will be automatically unprotected. Daniel Case (talk) 07:11, 19 January 2025 (UTC)
Reason: Editors keep updating in Vance's infobox, that Jon Husted is Vance's successor as US Senator. Husted is still Ohio lieutenant governor. GoodDay (talk) 15:58, 18 January 2025 (UTC)
- Declined – Not enough recent disruptive activity to justify protection. The article's already at ECP anyway. The only place we can go from here, really, is 1RR. Do you think that's necessary? Daniel Case (talk) 07:13, 19 January 2025 (UTC)
Temporary semi-protection: Persistent disruptive editing – Persistent disruptive editing from multiple IPs. Annh07 (talk) 16:33, 18 January 2025 (UTC)
- Semi-protected for a period of 10 days, after which the page will be automatically unprotected. Daniel Case (talk) 07:18, 19 January 2025 (UTC)
Temporary semi-protection: Persistent disruptive editing – An IP has been persistently trying to add a non-notable building to the infobox without any discussion. This has been ongoing for several months. See examples here:
- [3]. Ixudi (talk) 17:35, 18 January 2025 (UTC)
- Semi-protected indefinitely. Will log at CTOPS. Daniel Case (talk) 07:21, 19 January 2025 (UTC)
Temporary semi-protection: Persistent vandalism – IP hopper vandalism. Jalen Barks (Woof) 17:35, 18 January 2025 (UTC)
- Semi-protected for a period of six months, after which the page will be automatically unprotected. Will log at CTOPS. Daniel Case (talk) 07:25, 19 January 2025 (UTC)
Reason: High level of IP vandalism, request of more extended or permanent protection Aldebaran69 (talk) 17:58, 18 January 2025 (UTC)
- Semi-protected for a period of one year, after which the page will be automatically unprotected. Will log at CTOPS per BLPGROUP. Daniel Case (talk) 07:29, 19 January 2025 (UTC)
Temporary semi-protection: Persistent vandalism – Multiple IP users vandalizing page today. Wburrow (talk) 18:20, 18 January 2025 (UTC)
- Semi-protected for a period of three days, after which the page will be automatically unprotected. Daniel Case (talk) 07:33, 19 January 2025 (UTC)
Temporary extended confirmed protection: Persistent disruptive editing – Page becoming a time sink, IMO. Aloha27 talk 18:37, 18 January 2025 (UTC)
- User(s) blocked: Ramihasib (talk · contribs) blocked by Daniel Case. from the article indefinitely. Daniel Case (talk) 07:37, 19 January 2025 (UTC)
Indefinite full protection: Persistent Disruptive Editing. 54rt678 (talk) 19:49, 18 January 2025 (UTC)
- Declined We don't just do that. Daniel Case (talk) 07:38, 19 January 2025 (UTC)
Indefinite extended confirmed protection: Persistent vandalism – This page suffers from persistent vandalism or unconstructive edits. This is the second time I have personally seen this in RC patrols. This article should probably be considered for permanent protection. m a MANÍ1990(talk | contribs) 20:16, 18 January 2025 (UTC)
- Edits do not appear to be vandalism, but there seems to be persistent blanking and insertion of promotional content. TornadoLGS (talk) 21:00, 18 January 2025 (UTC)
Indefinite template protection: High-risk template – Now with 16,000 transclusions, used by {{Cite wikisource}} which itself is TE-protected. — hike395 (talk) 20:28, 18 January 2025 (UTC)
Temporary semi-protection: Persistent disruptive editing. Jetstreamer Talk 20:44, 18 January 2025 (UTC)
Reason: Repeated whitewashing/turning into a hagiography by IPs and new editors 81.2.123.64 (talk) 21:12, 18 January 2025 (UTC)
Temporary cascade protection: It is a protected photo of the day and it will be main in under 48 hours 54rt678 (talk) 21:33, 18 January 2025 (UTC)
Indefinite semi-protection: Persistent sockpuppetry – Long-term IP vandalism by Wikipedia:Long-term abuse/Demographics vandal. Short periods of protection, like the 3 days last month, have little protective effect. MichaelMaggs (talk) 21:45, 18 January 2025 (UTC)
- Semi-protected for a period of one month, after which the page will be automatically unprotected. Daniel Case (talk) 07:40, 19 January 2025 (UTC)
Temporary semi-protection: Persistent sockpuppetry – A LTA keeps reporting User:CFA over and over using multiple accounts for a false claim of edit warring on a deleted article. Isla🏳️⚧ 22:11, 18 January 2025 (UTC)
Indefinite extended protection: Arbitration Enforcement. WP:RUSUKR. 💽 🌙Eclipse 💽 🌹 ⚧ (CALL ME IF YOU GET LOST) 22:11, 18 January 2025 (UTC)
Indefinite semi-protection: Persistent sockpuppetry – It looks like the person behind this indefinitely blocked account is now evading that block and continuing to disrupt its talk page using IP addresses. — AP 499D25 (talk) 23:51, 18 January 2025 (UTC)
- Automated comment: One or more pages in this request appear to already be protected. Please confirm.—cyberbot ITalk to my owner:Online 06:01, 19 January 2025 (UTC)
- Dancing with the Stars (American TV series) season 28 (edit | talk | history | links | watch | logs)
Semi-protection: Persistent disruptive editing – Persistent disruptive editing by IP editor. Bgsu98 (Talk) 00:00, 19 January 2025 (UTC)
Reason: Indefinite semi-protection. unconstructive edits. 50.100.44.204 (talk) 00:27, 19 January 2025 (UTC)
Reason: Indefinite semi-protection. This page has a lengthy protection history, most recently for 2 years but previously for 1, and expired. I feel that this page should be indefinintly to prevent vandalism. Thank You. 50.100.44.204 (talk) 00:53, 19 January 2025 (UTC)
Reason: Edit warring from newly-extended confirmed users, with inappropriate and to some level dubious info about other people at a BLP that is currently one of the most-visited on WP. Users ignore warnings and discussion requests, one petulantly. Kingsif (talk) 00:59, 19 January 2025 (UTC)
- Semi-protected for a period of one month, after which the page will be automatically unprotected. Daniel Case (talk) 07:43, 19 January 2025 (UTC)
Temporary semi-protection: Persistent vandalism. Shadow4dark (talk) 01:05, 19 January 2025 (UTC)
Temporary semi-protection: Arbitration enforcement – WP:GS/SCW&ISIL. Leonidlednev (T, C, L) 01:37, 19 January 2025 (UTC)
Temporary semi-protection: Persistent Vandalism. IP vandalism. 💽 🌙Eclipse 💽 🌹 ⚧ (CALL ME IF YOU GET LOST) 02:26, 19 January 2025 (UTC)
- User(s) blocked. — rsjaffe 🗣️ 04:26, 19 January 2025 (UTC)
Temporary semi-protection: Persistent vandalism – Vandal started harassing me on my talkpage after I reverted their edits. 💽 🌙Eclipse 💽 🌹 ⚧ (CALL ME IF YOU GET LOST) 02:39, 19 January 2025 (UTC)
Reason: Persistent disruptive editing in the last days. Xexerss (talk) 02:41, 19 January 2025 (UTC)
Semi-protection: Persistent vandalism. Filmssssssssssss (talk) 02:44, 19 January 2025 (UTC)
Semi-protection: Persistent vandalism. Nswix (talk) 02:49, 19 January 2025 (UTC)
Reason: Highly disruptive vandal which uses these IP addresses 68.33.255.195 and 2601:147:4700:2000:b8d3:bbb5:f93:3e37 (same person). User has a history of this behaviour since last year, which led to a temporary block on another page and temp. protection of 2 others. I do not wish to edit war. The user has done this on at least 6 other pages which I have observed and/or contributed to. Warnings and attempts to discuss have been exhausted, therefore I am requesting temp. protection and an absolute ban on the user. Xaymacan (talk) 03:14, 19 January 2025 (UTC)
- Daniel Case the vandal which I complained to you about a couple weeks ago is back at it. This user 68.33.255.195 was blocked from the Jamaican cuisine page by another Admin. Last December you temporarily protected Rice and peas from the same user who uses these IP addresses 68.33.255.195 and 2601:147:4700:2000:b8d3:bbb5:f93:3e37. Below I saw where he/she has also requested protection of the same page, by falsely accusing me of what he/she has been doing. I've exhausted attempts to discuss the issue and warnings, but to no avail. I look forward to some effective intervention from you or another admin. Thanks. Xaymacan (talk) 05:14, 19 January 2025 (UTC)
- Declined – Content dispute. Please use the article's talk page or other forms of dispute resolution. — rsjaffe 🗣️ 05:31, 19 January 2025 (UTC)
- Rsjaffe I've been using the article's talk page and even the user's talk page to come to a consensus by discussing the issue, but the user has never responded until now. I even asked other editors to chime in. I appreciate that here is not the place to discuss it, but the user which has a history of vandalism has no intention of actually resolving the matter. The only thing that has worked in the past is temp. protection of the pages or temp. block of the said user's IP address (as was the case in early January). While it might seem like a content dispute which in essence it is, this user tends to follow the pages I contribute to and remove/change content. There is a clear pattern of stalking, vandalism and edit warring, which I have been enduring for the last few months. It is also done to other editors on certain pages, and the edit summaries that they write and claims below are false. This is creating a disruptive and hostile environment, all for the sake of writing and improving articles. I tend to request the protection to avoid engaging in edit warring. By the way, moments after you denied the request, the user returned to the page with random citations, including the book source I provided on the talk page to support the distinction which had been previously discussed by other editors. He/she has been wantonly adding sources (including my book source) which actually do not support the sentences where they had been placed. Xaymacan (talk) 06:30, 19 January 2025 (UTC)
- User(s) blocked: 68.33.255.195 (talk · contribs) blocked by Daniel Case. for 72 hours. Daniel Case (talk) 06:47, 19 January 2025 (UTC)
- Rsjaffe I've been using the article's talk page and even the user's talk page to come to a consensus by discussing the issue, but the user has never responded until now. I even asked other editors to chime in. I appreciate that here is not the place to discuss it, but the user which has a history of vandalism has no intention of actually resolving the matter. The only thing that has worked in the past is temp. protection of the pages or temp. block of the said user's IP address (as was the case in early January). While it might seem like a content dispute which in essence it is, this user tends to follow the pages I contribute to and remove/change content. There is a clear pattern of stalking, vandalism and edit warring, which I have been enduring for the last few months. It is also done to other editors on certain pages, and the edit summaries that they write and claims below are false. This is creating a disruptive and hostile environment, all for the sake of writing and improving articles. I tend to request the protection to avoid engaging in edit warring. By the way, moments after you denied the request, the user returned to the page with random citations, including the book source I provided on the talk page to support the distinction which had been previously discussed by other editors. He/she has been wantonly adding sources (including my book source) which actually do not support the sentences where they had been placed. Xaymacan (talk) 06:30, 19 January 2025 (UTC)
Semi-protection: Persistent vandalism. Salmoonlight (talk) 05:01, 19 January 2025 (UTC)
Semi-Protection: Disruptive editing of IP address and non-login account. Please, I request to protection this article. Panda Arun (talk) 05:11, 19 January 2025 (UTC)
Semi-protection: Persistent vandalism. Nswix (talk) 05:37, 19 January 2025 (UTC)
Reason: High level of IP editing that's been amplified since September, even spreading to the Simple English Wikipedia Surayeproject3 (talk) 06:57, 19 January 2025 (UTC)
Temporary semi-protection: Persistent vandalism. moderate to high level of vandalism throughout its history, according to redwarn. 🗽Freedoxm🗽(talk • contribs) 07:13, 19 January 2025 (UTC)
Current requests for reduction in protection level
Before posting, first discuss with the protecting admin on 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.
Current requests for edits 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.
Add “by June 30, 2024” to the sentence: The Lancet has estimated 70,000 deaths due to traumatic injuries.[8] Seahumidity (talk) 23:09, 12 January 2025 (UTC)
I would like to request that... (the status section for the front page should be labeled as “ceasefire” until the ceasefire ends. This is in accordance with the recently-reached agreement.) . LordOfWalruses (talk) 04:55, 17 January 2025 (UTC)
Handled requests
A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.