Requests for page protection

This page is for requesting that a page, file or template be fully protected, create protected (salted), extended confirmed protected, semi-protected, added to pending changes, move-protected, template protected, upload protected (file-specific), or unprotected. Please read the protection policy for details. 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 only to prevent IP and new user vandalism and move protection is used to stop page-move wars. Extended confirmed protection is used where semi-protection has proved insufficient.

After a page has been protected, the protection is listed in the page history and logs with a short description indicating why it was protected, and the article is listed on Special:Protectedpages. Further discussion should take place on the Talk page of the article. In the case of full protection due to edit warring, admins do not revert to specific versions of the page, except to get rid of obvious vandalism.

Instructions

If you would like to request to have a page protected, have a page's existing protection level lowered or raised, or would like to submit an edit request for a protected page, please follow these steps:

  1. If you are requesting unprotection, the correct protocol is to ask the protecting administrator first for unprotection (the admin's user account name can be found in the page's edit history). If for any reason he or she is unresponsive, unwilling, or unable to lower protection then you may list your request on this page.
  2. Add a level-3 header (i.e. === [[Example title]] ===) with the exact title of the page you would like (un)protected. If the page is not in the article namespace, include the namespace prefix (e.g. Template:Example template or User:Example user). Place your request at the bottom of either the protection or unprotection list, depending on the nature of your request. Please make sure you have spelled the name of the article properly; a common error stems from mistaken requests for the protection of redirects, particularly capitalised ones.
  3. Place the pagelinks template below the header, in the form of * {{pagelinks|Example title}} (note the asterisk).
  4. If you are requesting protection, write the type of request (full protection, semi-protection, pending changes, move protection) and a brief reason for your request below your header.
  5. Please do not add arbitrary requests for a protection expiry time to your request, or request indefinite protection arbitrarily.
    • If there is a reason for a page to be protected for a certain amount of time, such as protecting a user talk page until the user is unblocked, please make this clear.
    • If you are requesting indefinite semi-protection or pending changes, be aware that it is only applied to articles with endemic and endless vandalism problems that multiple increasing periods of temporary semi-protection or pending changes have failed to stop.
    • Note that different expiry times can be set for edit- and for move-protections— thus, an article can, for example, be semi-edit-protected for a week and also fully-move-protected indefinitely.
  6. Sign your request with four tildes ~~~~ and click Publish changes.
  • Note: editors should not consider requesting page protection as a method for continuing an argument from elsewhere nor as a venue for starting a new discussion regarding article content. If a request contains excessive argument, appears to be intended to resolve a content dispute, includes personal attacks or uncivil comments, or has any other unrelated discussion, it will be removed from this page and no action will be taken.
Examples
For single page requests
=== [[Example Article Name]] ===
* {{pagelinks|Example Article Name}}
'''Semi-protection:''' High level of IP vandalism. ~~~~
=== [[Template:Example Template Name]] ===
* {{pagelinks|Template:Example Template Name}}
'''Reduction in protection level:''' From full protection to template editor protection. ~~~~
For multiple page requests with the same criteria
=== Short descriptive header ===
* {{pagelinks|Bharatpedia:Example Page Name 1}}
* {{pagelinks|Bharatpedia:Example Page Name 2}}
'''Temporary semi-protection:''' High level of IP vandalism. ~~~~


Current requests for increase in protection level[edit source]

Place requests for new or upgrading semi-protection, full protection, move protection, create protection at the BOTTOM of this section. Check the rolling 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.

Sai Tamhankar[edit source]

Semi-protection: Hello Admin, Page Created by me Sai Tamhankar it is Created Organically By Verifying All Available Sources.Can we Make this Page Semi Protected ? Kindly Share Your Reviews.(-Pixerark (talk) 10:49, 14 May 2021 (IST))Reply

Declined – Not enough recent disruptive activity to justify protection. -- WikiDwarf (talk) 11:42, 14 May 2021 (IST)Reply

Siddhaguru[edit source]

Semi-protection: User with possible conflict of interest repeatedly removing sourced contents and using IP address for removing my edits so please protect the page. Khan786 (talk) 09:26, 9 September 2021 (IST)Reply

Closing this request as stale. The reported disruption is from September 2021 and has not recurred, so no protection is needed now. 🍁Bharatwiki Socrates🍁(📩) 13:18, 9 November 2026 (IST)Reply

Vijay Raaz[edit source]

Repeated IP edits are changing the article's image. The unofficial image has been added again despite previous removal, so protection is requested to prevent further disruptive image changes. Editorial Oversight(Talk with me) 01:49, 22 September 2026 (IST)Reply

They seem to have stopped for now. If they return and start vandalising the page again, the IP address can be blocked.
When the vandalism is coming from only one or two users or IPs, please report them for blocking rather than requesting page protection. If they continue returning through multiple different accounts or IPs, then page protection can be requested. Protection should generally be treated as a last resort. WikiDwarf (talk) 09:02, 22 September 2026 (IST)Reply
Closing this request as declined for now, per the reply above. If the image changes resume, please report the IP addresses for blocking. 🍁Bharatwiki Socrates🍁(📩) 13:18, 9 November 2026 (IST)Reply

Narendra Modi[edit source]

Vandalism processing Editorial Oversight(Talk with me) 18:25, 26 September 2026 (IST)Reply

The user has been blocked for vandalism. If there are only one or two users involved, please request that they be blocked instead, as page protection should generally be used when there is repeated vandalism within a short period. WikiDwarf (talk) 18:30, 26 September 2026 (IST)Reply

Semi-protection: Frequent vandalism. Duration: Indefinite. Dokania😎(📩) 21:10, 6 November 2026 (IST)Reply

Protected page from non autoconfirmed users for 6 months due to persistent vandalism. 🍁Bharatwiki Socrates🍁(📩) 06:39, 7 November 2026 (IST)Reply
Already semi-protected until 7 May 2027, so no new action is needed on this request. 🍁Bharatwiki Socrates🍁(📩) 13:17, 9 November 2026 (IST)Reply

Isha Malviya[edit source]

I would like to request temporary semi-protection for Isha Malviya due to repeated disruptive edits involving the addition of multiple AI-generated images.

Please review the page's edit history and assess whether the repeated additions of AI-generated images warrant protection under Wikipedia's protection policy. If the disruption is ongoing, semi-protection may help prevent further inappropriate edits by unregistered and new users.Editorial Oversight(Talk with me) 20:59, 29 October 2026 (IST)Reply

Declined for now. I have reviewed the page history: there have been only two edits, both from the same IPv6 range, swapping the infobox image back and forth, and both have already been reverted. Semi-protectiHarishrooon is generally a last resort for repeated disruption coming from multiple users. If the disruption returns from the same range, the range itself can be blocked instead; and if it later comes from several different IPs or accounts, please re-request and the page can be protected then. 🍁Bharatwiki Socrates🍁(📩) 11:07, 30 October 2026 (IST)Reply
Update (1 November): The disruption returned after that decline, now from more than one IP range, and a reverted change was restored by a second IP. I have semi-protected the page for one week and restored the lastclean version. 🍁Bharatwiki Socrates🍁(📩) 04:22, 1 November 2026 (IST)Reply

Semi-protection request: After the protection expires, the IP editor returns and adds the same AI-generated images again. Longer-term page protection and an IP block are needed to prevent further disruption. Duration: 3 months. Editorial Oversight(Talk with me) 18:12, 8 November 2026 (IST)Reply

It's not AI-generated though it may be AI-modified. Thus, I don't find any reason to block the editor or protect the page. Also does anyone know why there's no reply button in this page? Dokania😎(📩) 18:15, 8 November 2026 (IST)Reply
Try to find the original image. Share link. Also, this is not the first time this has happened on Isha's page; it has happened multiple times. So it is clear that this is a long-term abuse and blocking the IP is necessary.Editorial Oversight(Talk with me) 20:19, 8 November 2026 (IST)Reply
How's changing an image abuse? Even his image is newer than your image so it's fit to be there. He may be unaware of the policies but why you yourself have engaged in editing war? Dokania😎(📩) 20:36, 8 November 2026 (IST)Reply
The image is extremely vulgar and inappropriate for an encyclopaedic article. This does not appear to be a constructive attempt to improve the article; rather, the editor seems intent on repeatedly inserting an image based on personal preference. The repeated replacement of the image despite objections raises concerns about disruptive editing. Please compare the image with the original source and assess whether it is appropriate under image policies. I believe further protection may be necessary if this behaviour continues.Editorial Oversight(Talk with me) 21:41, 8 November 2026 (IST)Reply
The image isn't vulgar as private parts are covered but I am not sure if they are modified or not. Image is newer than your image so I think it makes sense to put it there. If the user had disruptive intentions he might have tried other disruptive words or images but he's only insisting on this image as he deems it fit. He's not indulged in any other disruptive editing. Dokania😎(📩) 21:52, 8 November 2026 (IST)Reply
If the article were about the Kama Sutra, I would have no objection to such an image. However, this is an article about Isha Malviya, a public figure, and repeatedly adding an inappropriate image can damage the quality and presentation of her article. More importantly, the image appears to have been created in violation of Wikipedia's copyright policies. check no source and licensing. Wikipedia may remove the image after reviewing the copyright issue. Until its copyright status is established, my reverts were justified to prevent potentially copyrighted material from remaining in the article.Editorial Oversight(Talk with me) 22:01, 8 November 2026 (IST)Reply
The inage is clearly covering private parts, so that shouldn't be an issue. About copyright, tbis isn't Wikipedia. I think Bharatpedia allows more liberty in adding images regardless of copyright issues? Anyways, what's the copyright status of your image? Is it freely licensed? Dokania😎(📩) 23:04, 8 November 2026 (IST)Reply
Perhaps such images are considered acceptable in your own site, but that is not my main concern anymore. Regarding copyright, the image was uploaded to Bharatpedia through Wikimedia Commons, where image uploads are subject to the platform's permissions and licensing requirements. Only the actual photographer or copyright owner can legitimately claim ownership of an image and release it under an appropriate licence. I have also reviewed this editor's contribution history and found other instances where copyrighted photographs appear to have been uploaded while being claimed as the editor's own work. This raises serious concerns about possible copyright violations and misrepresentation of ownership. I will report the evidence through the appropriate process, and the matter will be investigated. Appropriate action may follow.Editorial Oversight(Talk with me) 23:17, 8 November 2026 (IST)Reply
You should avoid personal attacks like Perhaps such images are considered acceptable in your own site, otherwise you will invite a block as warnings are already issued in the past too. The image asserted by you belongs to Instagram, uploaded by user:Harishroo and holds the same copyright status as the current image.Dokania😎(📩) 23:32, 8 November 2026 (IST)Reply
Semi-protected for one month due to the repeated disruptive image additions. 🍁Bharatwiki Socrates🍁(📩) 13:16, 9 November 2026 (IST)Reply
How's it disruptive? Is a change of image not allowed? Dokania😎(📩) 14:23, 9 November 2026 (IST)Reply
Excellent! Wikimedia also removed all of his AI-generated images from the site.Editorial Oversight(Talk with me) 14:33, 9 November 2026 (IST)Reply
Well, anyone can get the current image endorsed by you removed in the same way. I do not think such strict copyright laws are required in India, and Bharatpedia should maintain its own repository for images and files rather than depending on Wikimedia. Dokania😎(📩) 14:59, 9 November 2026 (IST)Reply
That's actually a good technical suggestion. Bharatpedia could consider developing its own independent media repository instead of relying entirely on Wikimedia Commons. It would give contributors more flexibility in uploading and managing freely licensed images and other media. However, proper copyright and licensing checks would still be necessary. I think this idea deserves a separate technical proposal and community discussion.Editorial Oversight(Talk with me) 15:05, 9 November 2026 (IST)Reply
You can raise it if you want. Dokania😎(📩) 15:17, 9 November 2026 (IST)Reply

Saran district[edit source]

Semi-protection: Persistent disruptive editing. Dokania😎(📩) 17:49, 11 November 2026 (IST)Reply

  • Support – Full support for extended-confirmed protection. The disruptive editing has been ongoing for a long time with autoconfirmed users are involved in the disputes. Semi-protection may not be sufficient.Editorial Oversight(Talk with me) 18:17, 11 November 2026 (IST)Reply
  • Not done: This appears to be primarily a content dispute between users and should be resolved through discussion on the relevant talk page. Protection is not a solution to a content dispute. It should be considered only where there is clear evidence of persistent disruption by multiple contributors, rather than being used to resolve disagreements between editors. I would suggest issuing appropriate warnings for edit warring, if warranted, rather than imposing page protection. WikiDwarf (talk) 18:34, 11 November 2026 (IST)Reply
  • Agree with WikiDwarf, no protection is needed here. This looks like a content dispute, not disruptive editing. Dr.Aviraj is adding content he believes belongs in the article; the disagreement is over whether that content is correct and sourced, and that is settled by discussion on the article's talk page, not by locking the page. The user is not vandalising the page. For the record, I had applied extended-confirmed protection one minute after the close above, from a board read taken before the close appeared, and I have now removed it, as the protection log of Saran district shows. 🍁Bharatwiki Socrates🍁(📩) 18:53, 11 November 2026 (IST)Reply
There's hardly anything for dispute here. He had already accepted he fabricating the sources in User talk:Dr.Aviraj#Do not revert edits or create hoax pages but no action was taken against him by @user:WikiDwarf even after non-stop personal attacks on me. In the end, I just gave up as quoted In any case, I am no longer interested in this debate, as it is being treated lightly even after he has accepted having done so. You may handle it as you deem fit.

Smit Machchhar[edit source]

Semi-protection: Multiple IP addresses are continuously vandalising this page. Please review the recent edits and protection. Duration: 1 month. Editorial Oversight(Talk with me) 19:39, 12 November 2026 (IST)Reply

Semi-protected for a period of 2 weeks, after which the page will be automatically unprotected. WikiDwarf (talk) 20:50, 12 November 2026 (IST)Reply

Sunny Leone[edit source]

Semi-protection: Since 9 November, two different IP addresses, 103.165.68.74 and 202.133.79.113, have repeatedly added the same false and unsourced information to the Sunny Leone article. Both IP editors have been warned, but they continue making the same edits despite the warnings. Please review the contributions of both IP addresses, investigate the repeated behaviour and take appropriate administrative action. Duration: 1 week. ButterflyCat (talk) 15:28, 15 November 2026 (IST)Reply

 Done as requested. 🍁Bharatwiki Socrates🍁(📩) 15:34, 15 November 2026 (IST)Reply

Current requests for reduction in protection level[edit source]

Current requests for edits to a protected page[edit source]