Jump to content

Wikipedia:Requests for page protection/Increase

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Filmssssssssssss (talk | contribs) at 23:40, 6 June 2024 (Rafah Governorate: Requesting semi-protection of Rafah Governorate.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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

Temporary semi-protection: Persistent vandalism. Nardog (talk) 09:57, 6 June 2024 (UTC)[reply]

Question: @Nardog: I may be missing some context here but what makes these edits vandalism? - Aoidh (talk) 17:30, 6 June 2024 (UTC)[reply]
@Aoidh: I may be missing something too, but it looks more like edit warring including a 3RR violation. In addition, there are bitey warnings and edit summaries that completely fail to explain anything. Even if something is wrong with the edits, WP:3RRNO has not been followed because it's not obvious vandalism and no exemption has been claimed. Daniel Quinlan (talk) 20:42, 6 June 2024 (UTC)[reply]
@Daniel Quinlan: That's basically where I'm at, if there's vandalism there's no explanation of how it is vandalism anywhere I can find. This looks like a content dispute where 3RR has been violated on both sides, and while the IP hasn't received any sort of edit warring notice, Nardog has participated at ANEW enough to be aware of the edit warring policy. I'm leaning towards blocking Nardog for 24 hours and semi-protecting the page for that same time period absent a reason why that's not ideal. - Aoidh (talk) 21:56, 6 June 2024 (UTC)[reply]
@Aoidh: I think we're on the same page, no objections. Daniel Quinlan (talk) 22:10, 6 June 2024 (UTC)[reply]
Done. Since the IP currently has no reason to revert I'll hold off on semi-protecting the page until there's a reason to do so, but I'll keep an eye on it. Thanks. - Aoidh (talk) 22:12, 6 June 2024 (UTC)[reply]
Looks like a content dispute to me, but perhaps I do not understand what is wrong with the anonymous user's suggested IPA pronunciation. Malinaccier (talk) 20:05, 6 June 2024 (UTC)[reply]
Not done. Closing request for the bot (see above discussion). Daniel Quinlan (talk) 22:25, 6 June 2024 (UTC)[reply]

Temporary semi-protection: Persistent vandalism – Lots of disruptive IP changes. Apparently this is an internet thing at the moment. Nemov (talk) 17:54, 6 June 2024 (UTC)[reply]

Declined – Not enough recent disruptive activity to justify protection. While the article is getting heavily edited (surprise: it's a new show in the Star Wars franchise), I don't see disruption overwhelming the editors currently. Daniel Case (talk) 19:28, 6 June 2024 (UTC)[reply]

Reason: This person has recently been declared missing in Greece. He is a British television presenter and the page keeps getting vandalised. It is an active missing persons case which is attracting media attention in the UK. Would it meet the eligibility to be protected? Svampesky (talk) 19:37, 6 June 2024 (UTC)[reply]

Declined – Not enough recent disruptive activity to justify protection. IP users adding unsourced or poorly-sourced info on a breaking news event is not, IMO, the same thing as vandalism (Of course, other admins may differ). Daniel Case (talk) 19:38, 6 June 2024 (UTC)[reply]
Okay. Thanks for letting me know. I'll keep an eye on the page because it is facing a little bit of vandalism, per Special:Diff/1227607970. What's the threshold of vandalism on a page for protection to be re-requested? Svampesky (talk) 19:44, 6 June 2024 (UTC)[reply]
Comment: It may be classed as the insertion of unsourced content (or disruptive editing) rather than specifically vandalism, but in the last 24 hours there have been many of these unsourced edits in the article by IPs, which in my view violate WP:BLP guidelines. Perhaps, therefore, admins such as Daniel Case may be able to reconsider if temporary pending changes (or another form of temporary protection) would be beneficial to deal with these ongoing unsourced edits and BLP violations. Regards, Kind Tennis Fan (talk) 22:22, 6 June 2024 (UTC)[reply]
If the level of disruption due to unsourced edits and vandalism increases, someone can submit a new request and we'll reconsider at that time. Things seem to have calmed down a bit on the article although that may just be due to the time of day. Daniel Quinlan (talk) 23:11, 6 June 2024 (UTC)[reply]

Reason: High level of vandalism by unidentified user Teddybrutus (talk) 20:05, 6 June 2024 (UTC)[reply]

Declined – Content dispute. Please use the article's talk page or other forms of dispute resolution. Malinaccier (talk) 20:59, 6 June 2024 (UTC)[reply]

Temporary semi-protection: News broke that he's likely retiring, but Pavelski himself stated that it's not official yet, meaning that we don't note him as retired. A multitude of non-EC editors, however, seem to disagree. The Kip (contribs) 20:58, 6 June 2024 (UTC)[reply]

Semi-protected for a period of 2 days, after which the page will be automatically unprotected. Daniel Quinlan (talk) 21:56, 6 June 2024 (UTC)[reply]

Temporary semi-protection: Persistent vandalism – Bio has become target of vandalism in 24 hrs. Legit editors are having to whac-a-mole the problem. Pyxis Solitary (yak yak). Ol' homo. 23:10, 6 June 2024 (UTC)[reply]

Semi-protected for a period of 2 days, after which the page will be automatically unprotected. Daniel Quinlan (talk) 23:13, 6 June 2024 (UTC)[reply]

Semi-protection: Persistent vandalism – WP:ARBPIA. Filmssssssssssss (talk) 23:40, 6 June 2024 (UTC)[reply]