Wikipedia:Requests for page protection/Increase: Difference between revisions
Airplaneman (talk | contribs) →Tiger 3: Semi-protected 1 month (using responseHelper) |
Airplaneman (talk | contribs) →Kaitlin Bennett: Declined. as per discussion above; pending changes seems adequate for now (using responseHelper) |
||
| Line 12: | Line 12: | ||
::::Thanks. [[User:Daniel Quinlan|Daniel Quinlan]] ([[User talk:Daniel Quinlan|talk]]) 01:21, 8 November 2023 (UTC) |
::::Thanks. [[User:Daniel Quinlan|Daniel Quinlan]] ([[User talk:Daniel Quinlan|talk]]) 01:21, 8 November 2023 (UTC) |
||
:::::I would say pending changes protection is doing fine, and semi is not needed at the moment. It might be needed if we get a couple of such edits every day. [[User:Ymblanter|Ymblanter]] ([[User talk:Ymblanter|talk]]) 07:56, 8 November 2023 (UTC) |
:::::I would say pending changes protection is doing fine, and semi is not needed at the moment. It might be needed if we get a couple of such edits every day. [[User:Ymblanter|Ymblanter]] ([[User talk:Ymblanter|talk]]) 07:56, 8 November 2023 (UTC) |
||
::::::I also think the pending changes is doing acceptably. One caveat: based on the article's long protection log and the kind of (BLP) vandalism that is happening, I would consider another long-term semiprotection. Given the above, I will decline this request with the decline template. [[User:Airplaneman|Airplaneman]] [[User talk:Airplaneman|(talk)]] [[Special:Contributions/Airplaneman|✈]] 20:15, 8 November 2023 (UTC) |
|||
:[[File:Pictogram voting oppose.svg|20px|link=|alt=]] '''Declined'''<!-- Template:RFPP#deny --> as per discussion above; pending changes seems adequate for now. [[User:Airplaneman|Airplaneman]] [[User talk:Airplaneman|(talk)]] [[Special:Contributions/Airplaneman|✈]] 20:15, 8 November 2023 (UTC) |
|||
=== [[Minnesota Wild]] === |
=== [[Minnesota Wild]] === |
||
Revision as of 20:15, 8 November 2023
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". Request protection of a page, or increasing the protection level
| |
Reason: Requesting indefinite ECP under WP:CT/BLP due to relentless BLP violations. (I applied PC protection, but subsequently made edits.) Daniel Quinlan (talk) 22:03, 7 November 2023 (UTC)
- Declined. Extended-confirmed protection is not necessary when only IPs have been targeting the page. The rate of disruption now is around what pending-changes can deal with, so escalation to semi-protection is not (in my opinion) necessary at the moment. Sdrqaz (talk) 23:22, 7 November 2023 (UTC)
- @Sdrqaz: You're right about ECP being unnecessary (looking again, the few problematic edits from non-IPs have been all over 500/30 or brand new). Nevertheless, I believe I erred in applying PC protection instead of semi-protection. All of the edits from IPs are serious BLP violations, seem to be coordinated, and semi-protection would be consistent with WP:PP and WP:CT/BLP. Daniel Quinlan (talk) 00:15, 8 November 2023 (UTC)
- If I had been in the same position as you, Daniel, I would have either pending-changes protected it or declined the protection request. There was a spate of disruption on 5 October, but the next disruptive edit was on 31 October, a 26-day gap. Since then, there's been two disruptive edits in a week – I get where you're coming from with BLPs being under CT, but policy also allows for pending-changes for BLP violations and the frequency isn't that high. I will deactivate the RfPP template to allow another administrator to review this, but I personally wouldn't semi-protect it. Sdrqaz (talk) 01:17, 8 November 2023 (UTC)
- Thanks. Daniel Quinlan (talk) 01:21, 8 November 2023 (UTC)
- I would say pending changes protection is doing fine, and semi is not needed at the moment. It might be needed if we get a couple of such edits every day. Ymblanter (talk) 07:56, 8 November 2023 (UTC)
- I also think the pending changes is doing acceptably. One caveat: based on the article's long protection log and the kind of (BLP) vandalism that is happening, I would consider another long-term semiprotection. Given the above, I will decline this request with the decline template. Airplaneman (talk) ✈ 20:15, 8 November 2023 (UTC)
- I would say pending changes protection is doing fine, and semi is not needed at the moment. It might be needed if we get a couple of such edits every day. Ymblanter (talk) 07:56, 8 November 2023 (UTC)
- Thanks. Daniel Quinlan (talk) 01:21, 8 November 2023 (UTC)
- If I had been in the same position as you, Daniel, I would have either pending-changes protected it or declined the protection request. There was a spate of disruption on 5 October, but the next disruptive edit was on 31 October, a 26-day gap. Since then, there's been two disruptive edits in a week – I get where you're coming from with BLPs being under CT, but policy also allows for pending-changes for BLP violations and the frequency isn't that high. I will deactivate the RfPP template to allow another administrator to review this, but I personally wouldn't semi-protect it. Sdrqaz (talk) 01:17, 8 November 2023 (UTC)
- @Sdrqaz: You're right about ECP being unnecessary (looking again, the few problematic edits from non-IPs have been all over 500/30 or brand new). Nevertheless, I believe I erred in applying PC protection instead of semi-protection. All of the edits from IPs are serious BLP violations, seem to be coordinated, and semi-protection would be consistent with WP:PP and WP:CT/BLP. Daniel Quinlan (talk) 00:15, 8 November 2023 (UTC)
Declined as per discussion above; pending changes seems adequate for now. Airplaneman (talk) ✈ 20:15, 8 November 2023 (UTC)
Reason: Semi-protection: Mobile editor repeatedly making unproductive edits. GoodDay (talk) 07:03, 8 November 2023 (UTC)
Semi-protected for a period of 6 months, after which the page will be automatically unprotected. Airplaneman (talk) ✈ 20:04, 8 November 2023 (UTC)
Temporary semi-protection: Persistent disruptive editing – Repeated recreation of article following Wikipedia:Articles for deletion/TrainPal (outcome of Redirect) by WP:SPA. Wikishovel (talk) 07:14, 8 November 2023 (UTC)
- Fully protected indefinitely. OhNoitsJamie Talk 19:48, 8 November 2023 (UTC)
Semi-protection: Persistent vandalism – vandalism. Joeykai (talk) 07:15, 8 November 2023 (UTC)
- Semi-protected for a period of 3 months, after which the page will be automatically unprotected. OhNoitsJamie Talk 19:49, 8 November 2023 (UTC)
Indefinite extended confirmed protection: Arbitration enforcement – WP:A/I/PIA. GnocchiFan (talk) 08:35, 8 November 2023 (UTC)
Reason: A lot of unregistered users are adding up wrong information and disrupting the article. MNWiki845 (talk) 08:50, 8 November 2023 (UTC)
Temporary semi-protection: Persistent vandalism – Disruptive and unsourced addition of content. C1K98V (💬 ✒️ 📂) 08:52, 8 November 2023 (UTC)
Reason: A lot of unregistered users are adding up incorrect information and destroying the article. MNWiki845 (talk) 08:53, 8 November 2023 (UTC)
- Semi-protected for a period of 1 month, after which the page will be automatically unprotected. Airplaneman (talk) ✈ 20:09, 8 November 2023 (UTC)
Temporary extended confirmed protection: Persistent disruptive editing – IPs keep on changing the WP:COMMONNAME and sourced census figures [1] [2] [3] [4] [5] [6] [7]. One of which is blocked as of now, so possibly sock/meat puppetry. Fylindfotberserk (talk) 09:40, 8 November 2023 (UTC)
Temporary semi-protection: Persistent sockpuppetry – Globally locked user. MCC214#ex umbra in solem 14:37, 8 November 2023 (UTC)
- Declined – Warn the user appropriately then report them to AIV or ANI if they continue. Please use AIV for issues with single users. OhNoitsJamie Talk 14:58, 8 November 2023 (UTC)
- Ohnoitsjamie, previous sock 202.131.73.200 add this before three days, also, this LTA very like edit in this page, such as 210.3.187.114, Quitespeak, 223.197.175.34, 210.0.147.79, 223.197.163.125, Quick7168, Kmart Silver Racer Miguel, Dbsjosndk, 14.0.128.0/17, so this page have been protected two times[8].--MCC214#ex umbra in solem 15:28, 8 November 2023 (UTC)
- I've added some changes to my LTA filters that should help with that. If those aren't effective, we can revisit protection. OhNoitsJamie Talk 15:32, 8 November 2023 (UTC)
Indefinite extended confirmed protection: WP:CTOP: WP:A/I/PIA. Wikishovel (talk) 14:51, 8 November 2023 (UTC)
Reason: IP vandalism’s and pages subject to the Armenia-Azerbaijan conflict are under extended-confirmed protection due to WP:GS/AA. TagaworShah (talk) 16:26, 8 November 2023 (UTC)
Temporary semi-protection: Persistent addition of unsourced or poorly sourced content – IP users are insisting upon an unsourced claim of whether the subject is a "moderate" member of his party. It may well be the case, but there are no reliable sources or discussion in the article for such. Stefen Towers among the rest! Gab • Gruntwerk 17:24, 8 November 2023 (UTC)
- Further, this moderate claim wasn't in the article prior to the recent flurry of edits due to the election. Stefen Towers among the rest! Gab • Gruntwerk 17:39, 8 November 2023 (UTC)
- Semi-protected for a period of 2 days, after which the page will be automatically unprotected. @StefenTower: Airplaneman (talk) ✈ 20:07, 8 November 2023 (UTC)
Semi-protection: vandalism and unsorced changes--Luke Stark 96 (talk) 18:30, 8 November 2023 (UTC)
Reason: Persistent disruptive edits by IPs and newly created accounts. Shadowwarrior8 (talk) 19:24, 8 November 2023 (UTC)
- Semi-protected for a period of 2 weeks, after which the page will be automatically unprotected. OhNoitsJamie Talk 19:56, 8 November 2023 (UTC)
Semi-protection: Persistent disruptive editing – IPs keep on adding crystal edits and unsourced hoaxes. Maybe protect until after after the end of the season (which is on the 26th)? Cause historically, pages blow up during the end of the season. Dieter Lloyd Wexler 19:36, 8 November 2023 (UTC)
Temporary semi-protection: Persistent vandalism – recent uptick in disruptive editing. 𝑭𝒊𝒍𝒎𝒔𝒔𝒔𝒔𝒔𝒔𝒔𝒔𝒔𝒔𝒔𝒔 (talk) 20:08, 8 November 2023 (UTC)