Wikipedia:Requests for page protection/Increase - Wikipedia


Article Images

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 full protection: Content dispute/edit warring. — Czello (music) 16:39, 6 October 2024 (UTC)[reply]

If we do that, since we usually go to full-protection for only a few days and MediaWiki does not currently allow us to layer full and semi-protections, the article would remain unprotected when the protection expires until we could reprotect it if necessary. Might 1RR be a better option? Daniel Case (talk) 04:40, 7 October 2024 (UTC)[reply]
1RR would be a decent solution as this is a CTOPs article — Czello (music) 07:09, 7 October 2024 (UTC)[reply]
  Done And logged at CTOPS Daniel Case (talk) 20:53, 7 October 2024 (UTC)[reply]

Temporary semi-protection: Persistent vandalism – persistent vandalism in AFD. Gauravs 51 (talk) 07:17, 7 October 2024 (UTC)[reply]

  Declined – Not enough recent disruptive activity to justify protection. Last was a couple of days ago. I am really loathe to protect AfDs (although I have done it) since it could be seen as tipping the process toward one side or the other. Daniel Case (talk) 21:41, 7 October 2024 (UTC)[reply]

Reason: Persistent addition of unsourced content by IP addresses has continued after a previous protection. SB678 (talk) 08:17, 7 October 2024 (UTC)[reply]

  Semi-protected for a period of three weeks, after which the page will be automatically unprotected. Daniel Case (talk) 21:47, 7 October 2024 (UTC)[reply]

Reason: Repeated edits, mostly by unregistered users, changing his nationality from Russian to Ukrainian without any discussion. [1] [2] [3] [4]

That dispute itself is covered in the article and no serious scholar considers him Ukrainian in any meaningful way. --Երևանցի talk 08:57, 7 October 2024 (UTC)[reply]

  Semi-protected indefinitely. Daniel Case (talk) 21:57, 7 October 2024 (UTC)[reply]

Temporary semi-protection: Persistent vandalism. jlwoodwa (talk) 10:38, 7 October 2024 (UTC)[reply]

Reason: Persistent disruptive minor edits by various IP socks of blocked user User:Harry the house, going back months - most recently 146.199.140.43. Jean-de-Nivelle (talk) 11:47, 7 October 2024 (UTC)[reply]

  User(s) blocked: 146.199.140.43 (talk · contribs) blocked by PhilKnight. Favonian (talk) 17:17, 7 October 2024 (UTC)[reply]

Reason: High level of IP vandalism. M S Hassan 📬✍🏻 12:45, 7 October 2024 (UTC)[reply]

Reason: Disruptive addition of unsourced content. HorrorLover555 (talk) 13:40, 7 October 2024 (UTC)[reply]

Semi-protection: Vandalism, likely related to the war. Filmssssssssssss (talk) 14:07, 7 October 2024 (UTC)[reply]

Reason: High level of IP vandalism Svito3 (talk) 14:25, 7 October 2024 (UTC)[reply]

Reason: Semi-protection - We have a series of IPs who're claiming SSR is still alive and being hidden by his management - a far cry from what was the case even last year but still not something supported by the sources. —Jéské Couriano v^_^v threads critiques 16:04, 7 October 2024 (UTC)[reply]

Reason: I think it would be a good idea to protect this article so that users without an account cannot edit them, since for about a month there has been a user with an IP from Macedonia (the last one he used was 77.29.162.92) who is constantly being blocked because he keeps vandalizing football team articles (Málaga CF, Real Oviedo, Granada CF, Athletic Bilbao, FK Partizan, FK Voždovac, etc.) AlejandroR1990 (talk) 16:49, 7 October 2024 (UTC)[reply]

Reason: High level of vandalism and disruption Kaustubh42 (talk) 17:29, 7 October 2024 (UTC)[reply]

Reason: Arbitration enforcement: WP:CT/AI. Multiple non-EC editors have edited a contentious topic area on this page. GeorgeMemulous (talk) 17:32, 7 October 2024 (UTC)[reply]

Temporary semi-protection: Inappropriate use of user talk page while blocked. •Cyberwolf•talk? 17:49, 7 October 2024 (UTC)[reply]

  User(s) re-blocked with talk page editing disallowed by Pickersgill-Cunliffe. Favonian (talk) 18:02, 7 October 2024 (UTC)[reply]

Temporary semi-protection: Persistent vandalism. SirMemeGod  18:14, 7 October 2024 (UTC)[reply]

  Already protected by administrator Elli. Favonian (talk) 18:56, 7 October 2024 (UTC)[reply]

Semi-protection: Persistent sockpuppetry – An editor is using multiple IP addresses to edit the page, falsely claiming that two episodes that were left unaired in the US aired. The Grand Delusion(Send a message) 18:46, 7 October 2024 (UTC)[reply]

Semi-protection: Reason: High level of vandalism by sockpuppet. Jassu712 (talk) 19:15, 7 October 2024 (UTC)[reply]

Semi-protection: Reason: High level of vandalism bh sockpuppet IP Address and account. Jassu712 (talk) 19:17, 7 October 2024 (UTC)[reply]

Extended-confirmed-protection: Reason: High level of IP vandalism by sockpuppet account and one user was blocked for edit war but he still using sockpuppet account and IP address. Jassu712 (talk) 19:23, 7 October 2024 (UTC)[reply]

  • Automated comment: A request for protection/unprotection for one or more pages in this request was recently made, and was denied at some point within the last 8 days.—cyberbot ITalk to my owner:Online 19:23, 7 October 2024 (UTC)[reply]
  • Comment::it was due to the user who requested get blocked and he was the one who still using sockpuppet that's why i am requesting for protection

Reason: High level of IP vandalism. Kansas Bear (talk) 19:52, 7 October 2024 (UTC)[reply]

Semi-protection: Persistent vandalism – Pending changes doesn't seem to be working. Filmssssssssssss (talk) 20:01, 7 October 2024 (UTC)[reply]

Temporary semi-protection: Persistent disruptive editing – Disruptive editing on a newly released popular film, mostly by IPs (specifically from the 103.38.17.0/24 range which has already been blocked once for this [likely connected to the Wikipedia:Sockpuppet investigations/Symon Sadik). These edits disrupt the lead/ib despite Talk page consensus to the contrary. Gotitbro (talk) 20:14, 7 October 2024 (UTC)[reply]

Temporary semi-protection: Persistent vandalism – Persistent edit-warring from Colorado IP range Special:Contributions/2601:283:4600:7050:0:0:0:0/64, blocked once last April. Disruption also from France IPs. Binksternet (talk) 20:25, 7 October 2024 (UTC)[reply]

Temporary protection: Persistent vandalism. Wysprgr2005 (talk) 20:43, 7 October 2024 (UTC)[reply]

  Semi-protected for a period of 6 months, after which the page will be automatically unprotected. DrKay (talk) 21:17, 7 October 2024 (UTC)[reply]
  Already protected by administrator DrKay. for six months. Daniel Case (talk) 21:39, 7 October 2024 (UTC)[reply]

Reason: Favored target of an LTA (Sevgilerde) using too wide of an IP range to block. All IP edits over the past 12 months have been disruptive. Sable232 (talk) 21:34, 7 October 2024 (UTC)[reply]

Semi-protection: Persistent vandalism. SNUGGUMS (talk / edits) 21:36, 7 October 2024 (UTC)[reply]

Semi-protection: Persistent disruptive editing – Persistent IP spam. SNUGGUMS (talk / edits) 21:40, 7 October 2024 (UTC)[reply]

Semi-protection: Persistent disruptive editing. SNUGGUMS (talk / edits) 21:44, 7 October 2024 (UTC)[reply]

Reason: disruptive editing Skyerise (talk) 21:45, 7 October 2024 (UTC)[reply]

Indefinite semi-protection: persistent vandalism; immediately resumed after unprotection 2603:8080:D03:89D4:76E7:6E76:D599:24BE (talk) 21:55, 7 October 2024 (UTC)[reply]

Reason: persistent vandalism 2603:8080:D03:89D4:76E7:6E76:D599:24BE (talk) 21:56, 7 October 2024 (UTC)[reply]

Indefinte semi-protection: Ipersistent vandalism 2603:8080:D03:89D4:76E7:6E76:D599:24BE (talk) 21:57, 7 October 2024 (UTC)[reply]

Indefinite semi -protection: persistent disruptive editing in the past 3 weeks. pc not working. at least 25 previous protections. That's enough 2603:8080:D03:89D4:76E7:6E76:D599:24BE (talk) 21:59, 7 October 2024 (UTC)[reply]