Wikipedia:Requests for page protection/Increase

This is an old revision of this page, as edited by LikeLakers2 (talk | contribs) at 16:21, 22 February 2022 (→‎War of 2022). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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. ItcouldbepossibleTalk 05:32, 22 February 2022 (UTC)[reply]

  Checking to see if protection is necessary. --Deepfriedokra (talk) 11:27, 22 February 2022 (UTC)[reply]
  Not done --Deepfriedokra (talk) 11:30, 22 February 2022 (UTC)[reply]
  Note: Looks to have stopped. Please reapply if it starts up again. --Deepfriedokra (talk) 11:30, 22 February 2022 (UTC)[reply]
  User(s) blocked. --Deepfriedokra (talk) 11:32, 22 February 2022 (UTC)[reply]
  Note: Thanks, Zzuuzz --Deepfriedokra (talk) 11:32, 22 February 2022 (UTC)[reply]

Temporary semi-protection: Persistent vandalism. ItcouldbepossibleTalk 05:32, 22 February 2022 (UTC)[reply]

  User(s) blocked. --Deepfriedokra (talk) 11:33, 22 February 2022 (UTC)[reply]
  Note: Such a busy little don't-bee. --Deepfriedokra (talk) 11:33, 22 February 2022 (UTC)[reply]

Temporary semi-protection: Persistent vandalism. ItcouldbepossibleTalk 05:32, 22 February 2022 (UTC)[reply]

  User(s) blocked. Anarchyte (talk) 11:47, 22 February 2022 (UTC)[reply]

Reason: Escalating level of IP vandalism. Three different IP addresses (most likely the same person, but I'm not sure), keep adding hoax cast list entries, which also happened on the main Kamen Rider Saber page. Blazewing16 (talk) 05:40, 22 February 2022 (UTC)[reply]

@Blazewing16: Please review Special:Contributions/114.79.38.0/23. Do you know if these edits are all bad? How can someone like me with no knowledge of the topic confirm that it's junk? The IPs should be blocked if it is. Johnuniq (talk) 06:58, 22 February 2022 (UTC)[reply]
@Johnuniq: I concede that the IP address's other edits may or may not be good. However, the Kamen Rider Saber-related ones aren't even added properly. If they were, they would match the other entries. I also concede that the Saber character page is not terribly good by any means. I've been trying to fix it ever since the show premiered in 2020. I know full well who the established characters are, and it is everyone currently listed there before the IP addresses in question got involved. But the IP addresses like the one you mentioned keep adding characters who never once appeared in the show and doing it improperly. This has happened three times already, not to mention the primary Kamen Rider Saber page like I said, which received a protection template three days ago for the same reason. I've messaged the IP addresses, but unless somebody steps in, I refuse to believe that they won't start an edit war just to maintain their changes. Blazewing16 (talk) 08:22, 22 February 2022 (UTC)[reply]

Reason: There is potential for vandalism as currently there is no protection given to this article at all, also people are potentially able to use this article to write their own personal beliefs rather than simply enhance the article so I request it’s protection level is permanently increased as currently there is no protection at all. 2A02:C7F:56E5:C700:6D06:6871:51A4:D39C (talk) 10:22, 22 February 2022 (UTC)[reply]

  Note: Before checking, I'll say the potential is also there for all users to help build the encyclopedia. That is a fundamental principle of Wikipedia. --Deepfriedokra (talk) 11:43, 22 February 2022 (UTC)[reply]
  Note: And now, I can eat my words. The potential has been realized! --Deepfriedokra (talk) 11:48, 22 February 2022 (UTC)[reply]
  Semi-protected (for bot archive) Anarchyte (talk) 11:49, 22 February 2022 (UTC)[reply]
  Note: It was ca 1977. Some visiting singers at Clearwater Wesleyan Church announced the Second Coming would be 1986. I believe this announcement was connected to a boook sale. --Deepfriedokra (talk) 11:52, 22 February 2022 (UTC)[reply]

Reason: creation protection please see the reasons at Talk:Ayan Nayak#Speedy deletion rationale they are believed to be recreated/redirected of a non notable actor from potential WP:UPE by introducing self sponsered refs, false image uploads like at c:User talk:२ तकर पेप्सी and c:Commons:Deletion requests/File:Signature of actor Ayan.png discussions says that they are only here for promotion and inter-wiki spam. They are also involved in forum shopping per [1]. Thanks 2402:3A80:1A42:3221:ED5F:7D15:2CAD:74D2 (talk) 10:59, 22 February 2022 (UTC)[reply]

  Checking to see if protection is necessary. --Deepfriedokra (talk) 11:54, 22 February 2022 (UTC)[reply]
  Fully protected for a period of 1 year, after which the page will be automatically unprotected. Left article in place but gave 1 year of full to prevent promo/disruption/etc. It seems like we may have begun working on this simultaneously, Deepfriedokra: did you come to a different conclusion, or are we in agreement? Anarchyte (talk) 11:57, 22 February 2022 (UTC)[reply]
@Anarchyte: Trying to decide if I'll just delete the thing. No mention of this person in a film that the page redirects to? Can't decide what rationale to use. Maybe WP:G11. --Deepfriedokra (talk) 11:58, 22 February 2022 (UTC)[reply]
He's listed under the Cast section cited to some tabloid article. I'm not sure here; if he is indeed playing a significant role in the show (as the article creator insists), then I think leaving the redirect is fine, but if he's a minor character then I wouldn't be opposed to G11. Googling his name isn't great, but then again the show is in a language I can't speak, so I may be missing something. Anarchyte (talk) 12:03, 22 February 2022 (UTC)[reply]
  Note: @Anarchyte: Looking at the talk page, CSD would be challenged. As there is a cite, I'll leave it be. --Deepfriedokra (talk) 12:07, 22 February 2022 (UTC)[reply]
@Anarchyte and Deepfriedokra: thanks for the help. But don't you think Ayan Nayak should be deleted instead based on the discussion and new evidence and also, sockpuppety evidences per last filling Wikipedia:Sockpuppet_investigations/AnonymousIndiaz/Archive#02_September_2021 at cited atTalk:Ayan Nayak#Speedy deletion rationale.Thank you. 2402:3A80:1A46:6454:71A2:8CBB:2547:FCD7 (talk) 12:08, 22 February 2022 (UTC)[reply]
Guys just saved the talk page in case it got deleted and preserve evidence (https://web.archive.org/web/20220222121001/https://en.wikipedia.org/wiki/Talk:Ayan_Nayak) 2402:3A80:1A46:6454:71A2:8CBB:2547:FCD7 (talk) 12:11, 22 February 2022 (UTC)[reply]
I have read that SPI, though I don't see how that would affect the existence of this redirect as it's going to be quite hard to add promotional material with the page fully protected for the next year. Paid editing isn't banned, just heavily discouraged. It's obvious that Nayak isn't notable, but it looks like the film he stars in is, which may be enough to warrant a redirect (I say "may" because the source citing his involvement isn't great). Anarchyte (talk) 12:15, 22 February 2022 (UTC)[reply]

:  Note: A CSD would be challenged and reversed. Try WP:RfD. If the WP:SPI determines it to be vandalsim or promotion, then they can proceed from there. --Deepfriedokra (talk) 12:14, 22 February 2022 (UTC)[reply]

  Note: This is the page for requesting protection. Which was done. Deletion requires fuller discussion. Like WP:RfD --Deepfriedokra (talk) 12:14, 22 February 2022 (UTC)[reply]

Temporary semi-protection: Persistent vandalism – Frequent disruptive edits with nonsense and empty edit requests. IceWelder [] 11:55, 22 February 2022 (UTC)[reply]

  Declined – Not enough recent disruptive activity to justify protection. We don't usually protect talk pages except in cases of heavy vandalism - particularly where the article itself is protected, since the talk page is then the only way for new users to participate. Just delete the empty or nonsense requests when they occur. MelanieN (talk) 14:11, 22 February 2022 (UTC)[reply]

Reason: Page needs to be re-protected because of IP vandalism. Riley1012 (talk) 13:20, 22 February 2022 (UTC)[reply]

  Declined – Not enough recent disruptive activity to justify protection. MelanieN (talk) 14:23, 22 February 2022 (UTC)[reply]

Semi-protection: Persistent vandalism. soibangla (talk) 14:45, 22 February 2022 (UTC)[reply]

  Semi-protected for a period of 3 days, after which the page will be automatically unprotected.--Ymblanter (talk) 15:03, 22 February 2022 (UTC)[reply]

Semi-protection: Persistent disruptive editing – Please see Talk:Client_state#An_utter_pile_of_drivel_and_bad_writing_by_multiple_editors. Drmies (talk) 15:16, 22 February 2022 (UTC)[reply]

  Semi-protected --Deepfriedokra (talk) 16:14, 22 February 2022 (UTC)[reply]

Temporary semi-protection: BLP Policy Violations. IP who claims to be the subject is repeatedly changing the birthdate with no prior discussion ― Blaze WolfTalkBlaze Wolf#6545 15:27, 22 February 2022 (UTC)[reply]

It's quite possible that is the subject. The IP is attempting to change the day of the month, not the year, which seems pretty innocuous, considering that the current birthday is not sourced as far as I can see. OhNoitsJamie Talk 15:32, 22 February 2022 (UTC)[reply]

Reason: Highly sensitive & dangerous situation, should not be open to public (I tried to edit myself to be less dramatic and don't know how to change article name, but changed 'War of 2022' to '2022 Russo-Ukrainian conflict' elsewhere). 2A02:C7E:1855:2B00:50E5:C162:CB2E:5972 (talk) 15:53, 22 February 2022 (UTC)[reply]

  Note: Seems as though the linked page has been deleted in exchange for 2021–2022 Russo-Ukrainian crisis (edit | talk | history | links | watch | logs), which itself has been semi-protected until 10 August 2022. LikeLakers2 (talk) 16:21, 22 February 2022 (UTC)[reply]

Temporary semi-protection: Persistent vandalism. tgeorgescu (talk) 16:15, 22 February 2022 (UTC)[reply]

  Semi-protected --Deepfriedokra (talk) 16:18, 22 February 2022 (UTC)[reply]