Edge Rewrite
// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a451f3472fafc424

Jump to content

Wikipedia:Requests for page protection

From Wikipedia, the free encyclopedia
(Redirected from Wikipedia:RfPP)
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 remove obvious vandalism.


Request addition of protection to a page, or increasing the current protection level

Request removal of protection from a page, or reducing the current protection level

Request a specific edit be made to a protected page

Request the non-urgent protection of multiple pages that do not require immediate administrator attention


Current requests for increase in protection level

Request addition of protection to a page, or increasing the current protection level

Place requests for protection increases at the BOTTOM of this section. If you cannot find your request, check the archive of requests or the page history. Only recently answered requests are still listed here.

Indefinite semi-protection: Persistent disruptive editing – As has repeatedly been the case, the page is under attack by a group of temp accounts that change sourced information (specifically plug listings) without sources and without comment, and ignore all invitations to discuss. , , , , .

Since the page has been haunted by similar problems for years, I suggest indefinite semi-protection. Gawaon (talk) 07:24, 1 October 2026 (UTC)reply

Note that this may be related to the long-term SPI case of ImprovisedAlphorn7281, whose socks have repeatedly shown similar editing patterns on that page. Gawaon (talk) 07:35, 1 October 2026 (UTC)reply
IP address(es) partially blocked (from Mains electricity by country). for one year. The Bushranger One ping only 21:27, 3 October 2026 (UTC)reply

Reason: This page has been subject to disruption multiple times today. It was briefly hijacked, and two subsequent edits by another user have had to be suppressed.

Would semi-protection (or any edit protection at all) be appropriate for this page? – MrPersonHumanGuy (talk) 16:57, 2 October 2026 (UTC)reply

Declined – Not enough recent disruptive activity to justify protection. I can't see where this was happening ... there are no reverts. Daniel Case (talk) 02:12, 4 October 2026 (UTC)reply

Reason: Attempts have been frequently made to erase the band's history between 1990 and 2022, including one anonymous editor claiming to "the band itself is asking for these releases to be removed from here!", essentially admitting to a Conflict of Interest. I suspect other edits by anonymous users or brand new accounts may have similar motivations. Some sections of the article also contain biased language that may need to be written in the future to sound more neutral. Sparkysilverfish (talk) 21:35, 3 October 2026 (UTC)reply

Declined – Not enough recent disruptive activity to justify protection. The edits reverted today were made quite some time ago. Bothersome as this is, it appears that at present the community has this under control. Daniel Case (talk) 02:13, 4 October 2026 (UTC)reply

Reason: Extensive disruption from LTAs. ✦Inzessin✦ (talk) 00:19, 4 October 2026 (UTC)reply

Already protected by administrator Pickersgill-Cunliffe. For three days. Daniel Case (talk) 02:14, 4 October 2026 (UTC)reply

Semi-protection: Persistent vandalism. Chrisahn (talk) 01:38, 4 October 2026 (UTC)reply

Semi-protected for a period of six months, after which the page will be automatically unprotected. And ...
IP address(es) blocked by Daniel Case. for a year. I rarely do the belt-and-suspenders thing, but in this case while the sockmaster has generally used an IP we have repeatedly blocked at length in the past, yet has shown a willingness to use others, it's appropriate. Daniel Case (talk) 02:28, 4 October 2026 (UTC)reply

Indefinite semi-protection: Persistent vandalism: Vandalism returned immediately after protection expired MathMan4 (talk) 02:40, 4 October 2026 (UTC)reply

Temporary semi-protection: Multiple people are falsely claiming he is dead when there is no evidence to prove it; semi-protection would help die down the argument. MathMan4 (talk) 02:48, 4 October 2026 (UTC)reply

Temporary semi-protection: Persistent vandalism – Spate of vandalism renewed by temporary accounts on 3 October. Geoff | Who, me? 02:49, 4 October 2026 (UTC)reply

Indefinite extended confirmed protection: Almost every change over the past few months (aside from reverts and removing protection notice) has been disruptive, even before a semi-protection of one year ended. SNUGGUMS (talk / edits) 03:00, 4 October 2026 (UTC)reply

Current requests for reduction in protection level

Request removal of protection from a page, or reducing the current protection level

Indefinite pending changes: Persistent vandalism – Requesting reduction in protection to pending changes, page was inf semi-protected over 3 years ago. The page also desperately needs updates and allowing more people to submit edits may help solve this. Szxq (talk) 05:21, 25 September 2026 (UTC)reply

@Ferret: Szxq (talk) 05:25, 25 September 2026 (UTC)reply
I'd say no, but I'd leave it up to Ferret. Anyone can still make an edit request. The article consistently averages 1000 page views per day for all of 2026 so far. And it appears to be actively edited. The page history includes a high proportion of reverted edits prior to protection, and pending-change protection would not change that situation if the same activity resumes, edits would still need reversion, so such protection would simply become a burden on the community as if it was unprotected. ~Anachronist (who / me) (talk) 05:52, 3 October 2026 (UTC)reply

Current requests for edits to a protected page

Request a specific edit be made to a protected page


Change “Collapse of the June ceasefire (July)” to “Collapse of the June ceasefire (20 June - 31 July)” because the June ceasefire ended on 19 June, not 30 June. ~2026-47054-03 (talk) 00:02, 23 September 2026 (UTC)reply

Is a source for this already in the article? Daniel Case (talk) 02:34, 27 September 2026 (UTC)reply
Yes! VAIO 2026 (talk) 01:10, 4 October 2026 (UTC)reply

OpenAI has decided to pause its training on all versions ~2026-50272-23 (talk) 15:48, 27 September 2026 (UTC)reply

Source? —Jéské Couriano v^_^v Look out it's Jimothy! 16:36, 27 September 2026 (UTC)reply
--~2026-50272-23 (talk) 18:07, 27 September 2026 (UTC)reply

Handled requests

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