Wikipedia:Requests for page protection
| 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
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.
Reason: WP:GS/AA ~2026-46970-14 (talk) 14:29, 29 August 2026 (UTC)
Question: Do you mean WP:GS/ACAS? I don't see much relevance to AA. Daniel Case (talk) 22:35, 29 August 2026 (UTC)
Create protection: Repeatedly recreated – Generic page name. –LaundryPizza03 (dc̄) 17:05, 29 August 2026 (UTC)
Declined for the same reason as Draft:Draft 2 above. Daniel Case (talk) 22:35, 29 August 2026 (UTC)
Temporary semi-protection: Persistent disruptive editing – Persistent LLM-generated edits, despite explaining NOLLM. See the page's filter logs. ‑‑gurkubondinn 18:51, 29 August 2026 (UTC)
- Declined – Warn the user appropriately then report them to AIV or ANI if they continue. One user's actions do not warrant protecting a page. I have already given them a level 3 warning for attempt. Daniel Case (talk) 22:54, 29 August 2026 (UTC)
Temporary semi-protection: Persistent Disruptive Editing. MathMan4 (talk) 23:31, 29 August 2026 (UTC)
Full protection: Content dispute/edit warring. Zackmann (Talk to me/What I been doing) 23:41, 29 August 2026 (UTC)
- Declined – Content dispute. Please use the article's talk page or other forms of dispute resolution. This page was WP:BLARed in December 2021. Today, a TA reverted it. While that's longer than the usual, BLAR does not specify a time limit on objection-by-reversion. If you believe the page is still not indepently notable, the next step is AfD, not edit-warring. The Bushranger One ping only 00:11, 30 August 2026 (UTC)
Temporary semi-protection: Persistent disruptive editing. MathMan4 (talk) 01:08, 30 August 2026 (UTC)
Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Callanecc (talk • contribs • logs) 02:20, 30 August 2026 (UTC)
Reason: Page is related to Israeli/Palestinian conflict, with October 7 attacks as centre of story of film article. There is a strong possibility of page vandalism and non-constructive additions from new/unregistered. Teatreez (talk) 01:33, 30 August 2026 (UTC)
- Extended confirmed protected indefinitely. Callanecc (talk • contribs • logs) 02:20, 30 August 2026 (UTC)
Current requests for reduction in protection level
Reason: It has been 6 years since it was indefinitely protected and I think it should be unprotected because the protection level hasn't been increased in 6 years so it may be time to give unautoconfirmed users a chance again. Gumoochie (talk) 00:09, 30 August 2026 (UTC)
- That's not how protection works. - The Bushranger One ping only 01:06, 30 August 2026 (UTC)
Current requests for edits to a protected page
The infobox of article states that over 1,154 Israeli security personnel died in the war, which is incorrect. The cited source clearly states that figure also includes soldiers killed by Hezbollah attacks, fighting in Lebanon, the West Bank and other fronts, as well as those who died due to accidents or even suicide, which is what their remembrance day (Yom Hazikaron) commemorates every year. The infobox is supposed to include only those who were killed in the October 7 attacks and fighting in Gaza ever since. I'd like to ask someone to please replace the number 1,154 for 864 using the following source (per WP:CALC, it's the sum of 331 soldiers and 58 police officers killed in Israel on October 7 plus 473 soldiers and 2 policemen killed in Gaza during the war): [1] Therefore, the total number of Israelis killed in the war (both civilians and security personnel) at the end of infobox should say 1,751+ (including dead hostages) instead of 2,041+
If that is too complicated, at least a footnote should be added to the 1,154 number saying the figure includes those killed in other related fronts of the war. Thank you very much. Davidhiestand (talk) 22:43, 15 August 2026 (UTC)
References
- ↑ "Authorities name 968 soldiers, 70 police officers killed in Gaza war". Times of Israel. 6 August 2026.
Update the “Model versions” table to reflect current ChatGPT model availability.
Change OpenAI o3 from “Legacy support” to “Discontinued”. OpenAI officially retired o3 from ChatGPT on August 26, 2026 following a 90-day sunset period.
GPT-5.3 and GPT-5.4 should also no longer be listed as “Active” if that status refers to current ChatGPT availability. These generations are no longer selectable in the current ChatGPT model picker and have been superseded by the GPT-5.5 and GPT-5.6 generations. The GPT-5.4 mini fallback information in OpenAI’s release notes dates from March 18, 2026 and appears to describe the configuration in use at that time rather than the current GPT-5.6 setup.
Current OpenAI documentation identifies GPT-5.6 Sol as the current reasoning model for eligible paid plans and GPT-5.6 Luna as the default model for Free and Go users. Please update the table accordingly, or clarify what “Active” means if it includes models no longer available in ChatGPT. Icetea36 (talk) 12:24, 28 August 2026 (UTC)
- I have added a note to Talk:ChatGPT notifying the participants there of this request. ~Anachronist (who / me) (talk) 15:01, 29 August 2026 (UTC)
- I updated the table for o3, GPT-5.3 and GPT-5.4. I didn't make changes about GPT-5.6 because the secondary sources I checked didn't mention which version of GPT-5.6 is available with which subscription and because that kind of information has a tendency to get outdated. Also, the table intentionally doesn't have rows for sub-versions like Luna or Sol, to limit its size. Alenoach (talk) 22:17, 29 August 2026 (UTC)
Handled requests
A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.
