Jump to content

Wikipedia:Requests for page protection

Page semi-protected
From Wikipedia, the free encyclopedia
    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: Persistent vandalism – Ip's going back and fourth changing information. Magical Golden Whip (talk) 19:26, 11 December 2024 (UTC)[reply]

    Already protected by administrator EvergreenFir. Malcolmxl5 (talk) 00:51, 12 December 2024 (UTC)[reply]

    Reason: Persistent disruptive editing (spam links, vandalism etc.) mixed in with some good faith IP edits. Protection log shows that disruption has been ongoing for many years, perhaps a case for long-term pending changes? Entranced98 (talk) 19:41, 11 December 2024 (UTC)[reply]

    Perhaps indefinite pending changes? I would wait for others to reply first. Johnny Au (talk/contributions) 00:44, 12 December 2024 (UTC)[reply]
    Semi-protected for a period of one year, after which the page will be automatically unprotected. BusterD (talk) 01:20, 12 December 2024 (UTC)[reply]

    Temporary semi-protection: Persistent disruptive editing – While this is a bit extraordinary, there are many unregistered/IP users who appear to be complaining about the map in their own section on the talk page, rendering the talk page very long and the conversation scattered. If the page could be protected, and users directed to the map discussion on Commons, I think this would effectively improve the encyclopedia and the maintenance thereof. — Red-tailed hawk (nest) 19:44, 11 December 2024 (UTC)[reply]

    Reason: Suspected socks are running an edit war.––kemel49(connect)(contri) 20:41, 11 December 2024 (UTC)[reply]

    Reason: High level of ip vandalism in last few days [[1]], [[2]], [[3]] etc. Theonewithreason (talk) 20:55, 11 December 2024 (UTC)[reply]

    Reason: Hello. Given that this article has been the victim not only of sockpuppets but also a bone of contention who claim that one did this and the other that, avoiding good coexistence, teamwork and contributing to Wikipedia; I request through this message that the the block is only and exclusively for Extended confirmed users. With this we continue to avoid more problems, although I do not understand why you should delete editions with their sources just because it was done by a sockpuppet. Thank you. JeanMercier90 (talk) 22:13, 11 December 2024 (UTC)[reply]

    Temporary semi-protection: Persistent disruptive editing – Edit warring by IP hopper. CycloneYoris talk! 22:22, 11 December 2024 (UTC)[reply]

    Reason: Continued IP vandalism (2803.xx) since previous PP expired. Mac Dreamstate (talk) 22:46, 11 December 2024 (UTC)[reply]

    Reason: Persistent addition of unsourced content. Waxworker (talk) 23:01, 11 December 2024 (UTC)[reply]

    Temporary semi-protection: Persistent sockpuppetry – Sock immediately started editing the article after it was unprotected. mwwv converseedits 23:30, 11 December 2024 (UTC)[reply]

    Temporary semi-protection: Persistent sockpuppetry – LTA target, resumed within 2 hours. Leonidlednev (TCL) 23:52, 11 December 2024 (UTC)[reply]

    Temporary semi-protection: Persistent sockpuppetry – Disruptive LTA returns to article after 8 hours. mwwv converseedits 23:54, 11 December 2024 (UTC)[reply]

    Reason: Persistent IP vandalism. Disruptive IP users from the articles WCIU-TV and WGN-TV, who are persistently claiming hoax information about The CW returning to WCIU next year, are vandalizing this page as well by claiming this on the "Television Stations" section. 2603:6081:893D:13AC:1C19:72A9:CDC7:ADB (talk) 00:18, 12 December 2024 (UTC)[reply]

    Semi-protected for a period of 6 months, after which the page will be automatically unprotected. Steven Walling • talk 04:07, 12 December 2024 (UTC)[reply]

    Reason: User 'Http Iosue' is continually engaging in edit warring and reverting edits to remove any mention of the sexual assault allegations against former One True King member, Tectone, even after the page went under semi-protected mode. I would like to request assistance to deal with this user and undo the vandalism done to the One True King wikipage. Thank you.Mach9Wikia (talk) 00:28, 12 December 2024 (UTC)[reply]

    This does not appear to be a request for page protection. If this is a dispute over what should be in the article, discuss it on the article talk page; the talk page is unprotected. Note that we must be very careful when adding information about living persons; it is not our job to spread allegations about people's lives. Malcolmxl5 (talk) 01:26, 12 December 2024 (UTC)[reply]

    Reason: High level of vandalism. Paramandyr (talk) 01:19, 12 December 2024 (UTC)[reply]

    User(s) blocked: 76.36.109.69 (talk · contribs) blocked by Peaceray. — Red-tailed hawk (nest) 01:32, 12 December 2024 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – BLP with persistent disruption by IPs and vandalism-only accounts. jellyfish  03:23, 12 December 2024 (UTC)[reply]

    Semi-protected for a period of 3 months, after which the page will be automatically unprotected. Longer time or pending changes protection may be merited. Steven Walling • talk 04:04, 12 December 2024 (UTC)[reply]

    Reason: This page has been highly attacked by IP users as soon as its temporary protection level is removed. They continuously change the box office numbers of the films without adding any sources despite multiple warnings, undermining the credibility of information the page provides. I would like to suggest that the page be permanently semi-protected to minimize the vandalism is possible. If not, temporary protection for a longer period is needed. Sneshik (talk) 03:40, 12 December 2024 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. It's only been a day or so since protection expired and there has been only one unsourced edit, which was reverted. If it continues over the coming days, feel free to ping me directly or re-request. Steven Walling • talk 04:02, 12 December 2024 (UTC)[reply]

    Semi-protection: BLP policy violations. Persistent disruptive editing by IPs. LaffyTaffer (talk) 03:56, 12 December 2024 (UTC)[reply]

    Semi-protected for a period of 3 months, after which the page will be automatically unprotected. Steven Walling • talk 04:00, 12 December 2024 (UTC)[reply]

    Temporary semi-protection: Persistent sockpuppetry – Persistent disruption by MAB. ~SG5536B 04:50, 12 December 2024 (UTC)[reply]

    Semi-protection: Persistent sockpuppetry – Continued disruption by MAB even after the page was unprotected. ~SG5536B 04:54, 12 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 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.

    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]
    The case page is not a reliable indicator of if an LTA is active or not, especially if they're reveling in the attention. —Jéské Couriano v^_^v threads critiques 08:28, 9 December 2024 (UTC)[reply]
    Pinging @Yamaguchi先生 --Ahecht (TALK
    PAGE
    )
    20:18, 9 December 2024 (UTC)[reply]
    Thank you Axedd for being in touch and Jéské for the ping. Axedd, you are already able to edit this article in the currently protected state. For context, there have been over 18 different page protections applied over the years due to long term abuse, block evasion, and persistent disruption in general. In light of this, was there any specific reason that you're looking to see this page unprotected? Regards, Yamaguchi先生 (talk) 23:34, 9 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]
    Pinging @El C. --Ahecht (TALK
    PAGE
    )
    16:19, 9 December 2024 (UTC)[reply]

    Reason: I have submitted both to the talk page and to the administrator a well researched and sourced addition to this page pertaining to Ukrainian special forces fighting Russians in Syria and no one has answered me, therefore this page cannot be updated based on new information. (If anyone wants me to provide the information again please ask).

    Downgrading this page to semi protection will still leave this page protected and will allow the page to be updated more.

    I am actively monitoring this page and if someone consistently does vandalism to this page we can always revert it and ask to upgrade the protection again.

    Thanks. Historyguy1138 (talk) 21:49, 11 December 2024 (UTC)[reply]

    no Declined. Per WP:RUSUKR extended-confirmed protection is applied to articles in the topic area of the Russo-Ukrainian war. This falls within that area. — Red-tailed hawk (nest) 23:22, 11 December 2024 (UTC)[reply]

    Unprotection: Requesting a reduction to indef WP:ECP, per conversation on talk page of imposing administrator. Move protection can remain at indef sysop. — Red-tailed hawk (nest) 23:17, 11 December 2024 (UTC)[reply]

    Reason: The page was protected due to BLP, and is still protected for that reason despite Eric dying in 2014. 100.7.34.111 (talk) 00:15, 12 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]

    Pinging @Kwamikagami as they are likely to have some insight to these issues. For me personally, I'm not sure. I happen to have fonts installed that handle the extIPA symbols, but I'm in the stark minority there. Remsense ‥  01:46, 9 December 2024 (UTC)[reply]
    ExtIPA is IPA. It's just a specialized subset. For example, extIPA can be used in the 'Illustrations of the IPA' published in JIPA.
    The issue is one of font support. The letters in question date to 2015, though they weren't added to Unicode until 2021. There are websites that list fonts that support various characters. These are supported by the SIL fonts, which are the best free IPA fonts available. If you don't have a good font installed, you're not going to be able to view IPA correctly anyway. That's why we have the IPA notice in articles, that you may need to install an IPA font to view the article properly. — kwami (talk) 05:32, 9 December 2024 (UTC)[reply]

    I would like to request that the most recent change be reverted: [4] . User 'Http iosue' who made that edit has been banned for engaging in edit wars and vandalizing the wikipage. The One True King page became protected today, but he continued to revert until he got banned. Mach9Wikia (talk) 02:40, 12 December 2024 (UTC)[reply]

    Handled requests

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