Jump to content

Wikipedia:Requests for page protection/Increase

From Wikipedia, the free encyclopedia

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.

Requests for page protection

You are currently viewing the subpage "Current requests for increase in protection level".
Return to Requests for page protection.

Request protection of a page, or increasing the protection level

Reason: Disruptive IP editing. HorrorLover555 (talk) 14:46, 18 November 2024 (UTC)[reply]

Declined – Not enough recent disruptive activity to justify protection. Not seeing it since the last protection expired. Daniel Case (talk) 20:28, 18 November 2024 (UTC)[reply]

Reason: The article has faced ongoing disruption and vandalism since September, which constitutes a WP:BLPVIO as it impacts the election results of living individuals. Extended protection, ideally six months would be ideal, as there is too much to handle. For more context, refer to Wikipedia talk:Requests for page protection#Upward of a thousand articles requiring protection. Sheriff | ☎ 911 | 20:55, 18 November 2024 (UTC)[reply]

@SheriffIsInTown: This falls into two separate contentious topics (Indian Subcontinent, concluded (sub)national elections). Have you considered maybe requesting at WP:Arbitration/Requests/Enforcement to maybe see if other actions besides protection could be taken? —Jéské Couriano v^_^v threads critiques 23:08, 18 November 2024 (UTC)[reply]
@Jéské Couriano I can’t think of any effective measures they could take against random IPs causing disruptions to multiple articles at irregular intervals every few days. Sheriff | ☎ 911 | 23:44, 18 November 2024 (UTC)[reply]

Indefinite semi-protection: Persistent vandalism even with pending changes2600:100C:B012:4577:60BE:B264:C465:8D5 (talk) 22:17, 18 November 2024 (UTC)[reply]

Declined – No changes to the current protection level are required at this point in time. Daniel Quinlan (talk) 23:06, 18 November 2024 (UTC)[reply]

Reason: Persistent disruptive editing. IPs are repeatedly replacing the website with a spam link. Johnj1995 (talk) 23:52, 18 November 2024 (UTC)[reply]

Indefinite semi-protection: Persistent disruptive editing – Per WP:GSCASTE - Repeated attempts at changing the subject's caste by logged out users. - Ratnahastin (talk) 01:04, 19 November 2024 (UTC)[reply]

Temporary semi-protection: Persistent disruptive editing – IP keeps removing large amounts of sourced content from the article. MaplesyrupSushi (talk) 01:24, 19 November 2024 (UTC)[reply]

Temporary semi-protection: Persistent vandalism – An IP keeps vandalizing the article. MaplesyrupSushi (talk) 01:27, 19 November 2024 (UTC)[reply]

Semi-protection: Persistent vandalism. Remsense ‥  02:07, 19 November 2024 (UTC)[reply]

Temporary semi-protection: Persistent vandalism — this protection needs to be done. 173.219.33.43 (talk) 02:21, 19 November 2024 (UTC)[reply]

Temporary semi-protection: Persistent disruptive editing – persistent addition of copyvio by two, now blocked, accounts. possible sockpuppets. Cowboygilbert - (talk) ♥ 02:29, 19 November 2024 (UTC)[reply]

Indefinite semi-protection: Multiple cases of IP vandalism and non-EP vandalism in the past year. Firecat93 (talk) 02:30, 19 November 2024 (UTC)[reply]

Semi-protection: Persistent disruptive editing. TornadoLGS (talk) 02:45, 19 November 2024 (UTC)[reply]

Semi-protected for a period of 3 days, after which the page will be automatically unprotected. Dr vulpes (Talk) 03:54, 19 November 2024 (UTC)[reply]

Reason: Over half of recent edits have been IP vandalism. I would like to request long-term semi-protection. Wildfireupdateman (talk) 03:11, 19 November 2024 (UTC)[reply]

Temporary semi-protection: Repeated IP vandalism. Red Phoenician (talk) 03:53, 19 November 2024 (UTC)[reply]