Jump to content

Wikipedia:Requests for page protection

Page semi-protected
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 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



    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.


    Temporary semi-protection: Article was protected back in July due to an IP user consistently removing information with multiple sources. Now that article is no longer protected, the same user is deleting the information using a new IP address. NJZombie (talk) 04:59, 8 December 2024 (UTC)[reply]

    Reason: Continued disruptive IP editing. Useddenim (talk) 13:24, 8 December 2024 (UTC)[reply]

    Reason: Too much edit wars and reverts are taking place. People are randomly changing box office numbers without looking at the reliable source. Hence requesting for Extended confirmed protection.PRIYAMANI7 (talk) 13:28, 8 December 2024 (UTC)[reply]

    +1 Reason: High level of vandalism by users on this page changing the boxoffice figure without citing reliable source. I can not say if canvassing or socks are attempted here. Some of these users are Special:Contributions/Shivraj0007 Special:Contributions/Manavchoudhury21 Special:Contributions/N0riooo Special:Contributions/RD55555 Special:Contributions/Jashpin. Special protection will help on this page and please revert to this last reliable version. Adding one more Special:Contributions/Bharatiya1177 who uses source with reports from the film producers that is unreliable. This disruptive editing is out of control on this page. RangersRus (talk) 14:04, 8 December 2024 (UTC)[reply]

    Temporary extended protection: This page is getting canvassing attempts from external websites trying to form a consensus to place a currently unofficial flag in the infobox Abo Yemen 13:42, 8 December 2024 (UTC)[reply]

    @Abo Yemen: Assuming that it does not reveal private information about a specific Wikipedian, would you please post a link to where the canvassing is coming from? — Red-tailed hawk (nest) 21:21, 8 December 2024 (UTC)[reply]

    Reason: Persistent unsourced date changes. Waxworker (talk) 14:39, 8 December 2024 (UTC)[reply]

    Indefinite Semi-protection: Persistent sockpuppetry – Per WP:GSCASTE, recently blocked IP ranges from Wikipedia:Sockpuppet investigations/Truthfindervert are editing warring in order to restore their edits. - Ratnahastin (talk) 16:04, 8 December 2024 (UTC)[reply]

    off-course but wait a second I really think there is not any generic need to confine any conditional protection of Chhura and for the sack of god i don't know what this man talking about but holding up my simple adherence is for Mazhabi Sikh[1]showcasing my edit summary hey look still anything to say go ahead @User:Ratnahastin

    adhering source which convey mazha (Mazhabi Sih) Jati are recruited in army of Sikhs prior to dogra rajput

    whatsoever intentionally miss out my point and twisting it for unnecessary clotting on the other side the @Truthfundervert extracted the laddhar stanza [2]

    which furiously even consoled with my aspirational editing i think its unreasonable since i am using Vi telecom network so it common anyone can edit, even locative to same region
    Note: Anyone can mediate if did any kind misconception thank aloy 2402:8100:2B79:F9E5:447:627E:E057:DBC0 (talk) 17:25, 8 December 2024 (UTC)[reply]

    Reason: Pending not sufficient. High vandalism. Request for long semiprotection. Island92 (talk) 17:56, 8 December 2024 (UTC)[reply]

    Temporary semi-protection: Persistent disruptive editing – Persistent disruptive editing by unregistered users. Yuvaank (talk) 18:26, 8 December 2024 (UTC)[reply]

    Semi-protection: Persistent vandalism – Continued disruption by IPs and new accounts over the result in the infobox. Mellk (talk) 18:30, 8 December 2024 (UTC)[reply]

    Reason: eastenders 81.100.140.55 (talk) 19:04, 8 December 2024 (UTC)[reply]

    Declined – Meaningless request. Favonian (talk) 20:08, 8 December 2024 (UTC)[reply]

    Reason: Michigan fan vandalismChar3290 (talk) 20:32, 8 December 2024 (UTC)[reply]

    Indefinite extended-protection: Contentious topics: Should be extended-protected since this article is related to the arab-israeli conflict. 🗽Freedoxm🗽 (talk) 21:28, 8 December 2024 (UTC)[reply]

    Reason: Indefinite semi-protection. Unconstructive edits. 50.100.44.204 (talk) 21:57, 8 December 2024 (UTC)[reply]

    Reason: Repeated removal of sourced content by IP Yung Doohickey (talk) 21:59, 8 December 2024 (UTC)[reply]

    Yngdoohickey is inflating numbers in articles and POV pushing. Every source says 377 victims. Even in the article itself it says: "As of March 2008, the remains of 345 massacre victims have been identified and returned to Kosovo and 32 remain missing". He found an old source speculating on the numbers and wants to add it. There is memorial and commemoration every year for the victims and reports, every source says 377 victims, even Albanian sources [3] [4] [5] [6] [7]

    He wants to put the article into protection so his inflated number stays and that's wrong. --2607:FEA8:101E:CE00:7D91:2CAD:FEF4:5B00 (talk) 22:54, 8 December 2024 (UTC)[reply]

    Semi-protection: IP vandalism in the past, and should be protected like the main article, Brian Thompson (businessman). This is an active, ongoing, major news event. Firecat93 (talk) 22:22, 8 December 2024 (UTC)[reply]

    Indefinite extended confirmed protection: Persistent vandalism – Same flag problem with other Syria related articles. Regioncalifornia (talk) 22:30, 8 December 2024 (UTC)[reply]

    Reason: Intermittent but persistent long-term vandalism by an anonymous editor who uses various IP addresses. The only edits to this article over the past year have been vandalism, and reverts thereof. As the article is about an event that happened a decade ago, few to none further changes are expected. Requesting page protection for an indefinite amount of time. Dmoore5556 (talk) 23:13, 8 December 2024 (UTC)[reply]

    Semi-protection: Persistent sockpuppetry – Block evasion through IPs. Za-ari-masen (talk) 23:22, 8 December 2024 (UTC)[reply]

    Reason: Persistent vandalism. Entranced98 (talk) 23:30, 8 December 2024 (UTC)[reply]

    Indefinite create protection: Repeatedly recreated. Sergiogriffiths (talk) 23:43, 8 December 2024 (UTC)[reply]

    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.

    Reason:Article is in a poorly written state and barely gets meaningful contributions since it was last protected. No signs of disruptive editing for a long time either.Axedd (talk) 14:45, 6 December 2024 (UTC)[reply]

    @Axedd: Is the long-term abuser that caused the article to be ECP'd still active on other articles? —Jéské Couriano v^_^v threads critiques 16:46, 6 December 2024 (UTC)[reply]
    Last time this specific user was active was 4 years ago according to his case page. I believe another sock caused this page to locked over an year ago for edit warring, but they weren't solely interested in this particular page. Axedd (talk) 16:52, 6 December 2024 (UTC)[reply]

    Reason: The article was protected back in 2010, when protecting standards were far lower. I believe it's now ready to go unprotected, Cheers. 50.100.53.53 (talk) 04:02, 7 December 2024 (UTC)[reply]

    I'm willing to try unprotection after 14 years of indef protection, unless Courcelles objects. – Muboshgu (talk) 21:39, 8 December 2024 (UTC)[reply]

    Reason: The protection is no longer necessary because i believe that the metaverse is now less associated with crypto and the blockchain - especially after the rise of spatial computing. 67.209.128.24 (talk) 15:46, 8 December 2024 (UTC)[reply]

    Suggested action: Lower to WP:WHITELOCK/WP:PCPP to prevent disruptive editing from cryptospammers while still allowing for broader contribution from legitimate editors (especially IPs like me). Otherwise, if no cryptospam is expected, remove protection completely. 67.209.128.24 (talk) 15:51, 8 December 2024 (UTC)[reply]

    Reason: The information and contents are totally incorrect and without credibility which provide wrong information public. FactsFinderKhorasan (talk) 21:20, 8 December 2024 (UTC)[reply]

    Declined So go make an edit request at Talk:Afghanistan. – Muboshgu (talk) 21:40, 8 December 2024 (UTC)[reply]

    Semi-protection: Persistent disruptive editing – Immediate resumption from last protect. Geraldo Perez (talk) 22:35, 8 December 2024 (UTC)[reply]

    Indefinite create protection: Repeatedly recreated. Sergiogriffiths (talk) 23:41, 8 December 2024 (UTC)[reply]

    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.


    This, I think, is the first time I've made a suggestion. Hopefully, I'm doing this correctly.

    The lateral fricative voiced retroflex, as an example, has an IPA representation of ɖɭ˔ according to its Wikipedia page, but the IPA Pulmonic table and other tables use the Unicode representation in the table and any font I have found just doesn't handle that character,

    Would it be better to use the IPA representation which I think many fonts handle since the table has 'IPA' in its title and its link points to the Wikipedia page with both representations? The linked article each cell in the table states that the representation the IPA version and that the Unicode character is implied from that.

    I'd be happy to make a list of each table and cell where this occurs if that is necessary and you think these will be worthwhile changes. BLWBebopKid (talk) 19:51, 8 December 2024 (UTC)[reply]

    Handled requests

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