|
|
| Line 1: |
Line 1: |
| {{short description|English Bharatpedia project policy on blocking}}
| | Kedarnath Yatra 2026 Registration Process |
| {{redirect-multi|1|Bharatpedia:Blocked|help with being blocked|Help:I have been blocked|and|Bharatpedia:Appealing a block}}
| |
| {{Redirect|Bharatpedia:BP|the policy page on Bharatpedia bots|Bharatpedia:Bot policy}}
| |
| {{Redirect|Bharatpedia:TPA|the description on how to make a perfect article|Bharatpedia:The perfect article}}
| |
| {{policy|subcategory=enforcement|BP:BP|BP:BLOCK|BP:BLOCKPOL}}
| |
| {{nutshell|User accounts and IP addresses may be '''blocked''' from editing to protect Bharatpedia from disruption.}}
| |
| {{Enforcement policy list}}
| |
| '''Blocking''' is the method by which [[Bharatpedia:Administrators|administrators]] technically prevent users from editing Bharatpedia. Blocks may be applied to [[BP:Account|user accounts]], to [[BP:IP|IP addresses]], and to ranges of IP addresses, for either a definite or an indefinite time, to all or a subset of pages. Blocked users can continue to access Bharatpedia, but cannot edit any page they are blocked from (including, if appropriate, their own [[Bharatpedia:User pages|user pages]]). In most cases, a site-wide blocked user will only be able to edit their own [[Bharatpedia:User talk pages|user talk page]].
| |
|
| |
|
| Blocks are used to prevent damage or [[Bharatpedia:Disruptive editing|disruption to Bharatpedia]], not to punish users (see {{section link||Purpose and goals}}). Any user may report disruption and ask administrators to consider blocking a disruptive account or IP address (see {{section link||Requesting blocks}}).
| |
|
| |
|
| If editors believe a block has been improperly issued, they can request a review of that block at [[Bharatpedia:Administrators' noticeboard]]. Administrators can unblock a user when they feel the block is unwarranted or no longer appropriate.
| |
|
| |
|
| Blocking is different from [[Bharatpedia:Banning policy|banning]], which is a formal retraction of [[Bharatpedia:User access levels|editing privileges]] on all or part of Bharatpedia. Blocks disable a user's ability to edit pages; bans do not. However, bans may be enforced by blocks; users who are subject to a total ban, or who breach the terms of a partial ban, will most likely be site-wide blocked to enforce the ban.
| | Kedarnath is one of the Char Dham and twelve Jyotirlingas of Lord Shiva; Char Dham is known as a path to Moksh. Every Hindu must visit the Char Dham at least once in their lifetime. Each Dham reflects its own unique ancient traditions and has its own significance. The four dhams are Yamunotri Dham, Gangotri Dham, Kedarnath Dham, and Badrinath Dham. |
|
| |
|
| == Purpose and goals ==
| | Kedarnath registration is compulsory for all pilgrims since it is a government-mandatory registration process; not only that this registration ensure the pilgrim’s safety, crowd management, as well as a smooth travel experience. Without completing the registration, pilgrims will not be able to move ahead of the checkpoint. The registration can be done at the official portal of Uttarakhand Tourism. Also, keep in mind that this registration applies to every age category and gender. Vaayu Aviation believes in assisting the pilgrims with a smooth and guided government registration process, ensuring government guideline compliance. |
| Blocks serve to protect the project from harm, and reduce likely future problems. Blocks may escalate in duration if problems recur. They are meted out not as retribution but to protect the project and other users from disruption and inappropriate conduct, and to deter any future possible repetitions of inappropriate conduct. Blocking is one of the most powerful tools that are entrusted to administrators, who should be familiar with the circumstances prior to intervening and are required to be able to justify any block that they issue.
| |
|
| |
|
| In general, once a matter has become "cold" and the risk of present disruption has clearly ended, reopening it by blocking retrospectively is usually not appropriate. In this situation, if an ongoing or serious concern persists, several [[Bharatpedia:Dispute resolution|dispute resolution]] processes exist to allow discussion and possible sanction of a user.
| | Step-by-Step Kedarnath Dham Registration Process 2026 |
| | Below is the complete Kedarnath registration 2026 process guide- |
|
| |
|
| [[Bharatpedia:Appealing a block|Blocks can be appealed]] (see {{section link||Unblocking}}). Requests to be unblocked are also decided in light of prevention and deterrence. A user may be unblocked earlier if the user agrees to desist and appears to have learned from the matter, or if the situation was temporary and has now ended. Likewise, a user who has previously returned to inappropriate conduct after other unblocks may find their unblock request declined for deterrence reasons, to emphasize the importance of change and unacceptability of the conduct.
| | Step 1: Visit the official Uttarakhand tourism portal using the link mentioned below- https://registrationandtouristcare.uk.gov.in/ |
|
| |
|
| === <span id="NOTPUNITIVE"></span>Blocks should not be punitive ===
| | Step 2: Register/Login to the web portal, followed by entering the correct personal details of the pilgrim, including name, age, and gender. |
| {{See also|Bharatpedia:Sanctions against editors should not be punitive}}
| |
| {{policy shortcut|BP:BLOCKNOTPUNITIVE|BP:NOPUNISH}}
| |
|
| |
|
| Blocks should not be used:
| | Step 3: Choose your preferred Kedarnath 2026 darshan dates. Government authorities need it to check daily availability limits. |
| # to retaliate;
| |
| # to disparage;
| |
| # to punish; or
| |
| # if there is no current conduct issue of concern.
| |
|
| |
|
| === <span id="PREVENTATIVE"></span><span id="DETERRENT"></span>Blocks should be preventative ===
| | Step 4: Upload government-authorised ID proof and a photograph of the pilgrim. |
| {{policy shortcut|BP:BLOCKP|BP:BLOCKPREVENTATIVE|BP:BLOCKDETERRENT}}
| |
|
| |
|
| Blocks should be used to:
| | Step 5: Select your travelling mode (helicopter, foot, or pony). |
| # prevent imminent or continuing damage and disruption to Bharatpedia;
| |
| # deter the continuation of present, disruptive behavior; and
| |
| # encourage a more productive, congenial editing style within community norms.
| |
|
| |
|
| Deterrence is based upon the likelihood of repetition. For example, though it might have been justifiable to block an editor a short time ago, such a block may no longer be justifiable right now, particularly if the actions have since ceased or the conduct issues have been resolved.
| | Step 6: Submit and download your Yatra e-pass; it will have a QR Code, which will further be scanned at the Shrine’s checkpoint. Make sure to carry it for checkpoint verification. |
|
| |
|
| == Common rationales for blocks ==
| | You can register from any digital device (phone, desktop, or laptop). |
| {{policy shortcut|BP:WHYBLOCK}}
| |
| The following are some of the most common rationales for blocks.
| |
|
| |
|
| As a rule of thumb, when in doubt, do not block; instead, consult other administrators for advice. After placing a potentially controversial block, it is a good idea to make a note of the block at the [[BP:ANI|administrators' incidents noticeboard]] for peer review.
| | Kedarnath Registration Fees at |
| | Kedarnath registration 2026 is free of cost, i.e., there is no separate cost of registration. Pilgrim can register through the registrationandtouristcare.uk.gov.in official Uttarakhand portal. |
|
| |
|
| Administrators should take special care when dealing with new users. Beginning editors are often unfamiliar with Bharatpedia policy and convention, and so their behavior may initially appear to be disruptive. Responding to these new users with excessive force can discourage them from editing in the future. See [[Bharatpedia:Do not bite the newcomers]].
| | Documents Required for Kedarnath Registration |
| | The key documents required before registration are- |
|
| |
|
| === Protection ===
| | Government-issued photo ID (such as Aadhar/ PAN/ Voter ID). |
| A user may be blocked when necessary to protect the rights, property, or safety of the [[foundationsite:About|Bharatmedia Foundation]], its users, or the public. A block for protection may be necessary in response to:
| | Passport-size photograph of every individual |
| * persistent [[Bharatpedia:No personal attacks|personal attacks]];
| | Current phone number for One-time password verification. |
| * personal, professional, or [[Bharatpedia:No legal threats|legal]] threats (including outside the Bharatpedia site);
| | Why is Kedarnath Registration Important in 2026? |
| * actions placing users in danger;
| | Registrations help the authorities to monitor pilgrims and offer emergency assistance if needed. |
| * {{anchor|Pedophilia}}actions that may compromise the safety of children, in accordance with [[Bharatpedia:Child protection]];
| | Tracks the daily visitor limits to avoid overcrowding at the Dham. |
| * disclosures of others' [[Bharatpedia:Harassment#Posting of personal information|personal information]] (whether or not the information is accurate);
| | Pre-bookings of travel and stays in order to avoid last-minute hassle. |
| * persistent [[Bharatpedia:Copyright violations|copyright violations]];
| | Enable emergency support and health monitoring. |
| * persistent posts of unreferenced, poorly or incorrectly referenced, or potentially [[defamatory]] information about [[Bharatpedia:Biographies of living persons|living persons]]; or
| | Registration helps in balancing a smooth coordination among the local authorities of Uttarakhand to avoid any future conflicts. |
| * an account appearing to have been compromised (as an emergency measure), i.e. there is some reason to believe the account is being used by someone other than the person who registered the account.
| | If you have not registered for the Kedarnath yatra, then you will not be allowed to enter the Kedarnath temple. |
|
| |
|
| When blocking in response to personal information disclosures or actions that place users in danger, consider notifying the [[Bharatpedia:Arbitration Committee|Arbitration Committee]] by e-mail ({{No spam|arbcom-en|bharatmedia.org}}) about the disclosure or danger and contacting someone with [[Bharatpedia:Oversight|oversight permissions]] to [[Bharatpedia:Requests for oversight|request deletion]] of the material in question.
| | Important Guidelines for Kedarnath Pilgrims |
| | Pilgrims must carry their Yatra e-pass (in the form of a digital or hard copy). |
| | Pilgrims must visit the Kedarnath temple on their registered date only. |
| | In case of a missed slot, the pilgrims will not be allowed to transfer their registration. |
| | It is essential to carry a medical kit, as well as follow the weather and safety advisories regularly. |
| | Kedarnath temple has daily visitor limits; crossing the limit would create an imbalance and may even lead to penalties. |
| | Visiting Kedarnath Without Registration? |
| | You will be prohibited from entering the Kedarnath temple without pre-registration. Pilgrims who do not have a Yatra e-pass can not go beyond the Patna check post or the Sonprayag check post. The key aim of the Uttarakhand government behind mandating this registration is to ensure effective crowd management and pilgrims’ safety. Hence, this registration is made free so that every devotee can visit. |
|
| |
|
| === Disruption ===<!-- This section is linked from [[Bharatpedia:Disruption]] -->
| | Assisted Kedarnath Registration by Vaayu Aviation- Start Your Kedarnath Journey Today |
| {{Policy shortcut|BP:DBLOCK|BP:BLOCKDISRUPT|BP:DISRUPTBLOCK}}
| | Vaayu Aviation brings you hassle-free, convenient, and comfortable Kedarnath Yatra packages for all devotees planning their yatra in 2026. We at Vaayu Aviation believe in assisting the pilgrims with a smooth and guided registration process, ensuring government guideline compliance so that you do not feel stressed at the last moment. |
| A user may be blocked when their conduct severely disrupts the project; that is, when their conduct is inconsistent with a [[Bharatpedia:Civility|civil, collegial atmosphere]] and interferes with the process of editors working together harmoniously to create an encyclopedia. A block for disruption may be necessary in response to:
| |
| * [[Bharatpedia:Vandalism|vandalism]];
| |
| * [[Bharatpedia:Civility|gross incivility]];
| |
| * [[Bharatpedia:Harassment|harassment]];
| |
| * [[Bharatpedia:Spam|spamming]];
| |
| * deliberately tripping the [[Bharatpedia:Edit filter|edit filter]]
| |
| * breaching the [[Bharatpedia:Policies and guidelines|policies or guidelines]], especially [[Bharatpedia:Sock puppetry|sock puppetry]];
| |
| * attempts to coerce actions of editors through threats of actions outside the Bharatpedia processes, whether onsite or offsite.
| |
|
| |
|
| [[Bharatpedia:Edit warring|Edit warring]], especially breaches of the [[BP:3RR|three-revert rule]], often results in a block, either from the pages the user is disrupting or from the entire site.
| | FAQs |
| | Is Kedarnath registration necessary? |
| | Yes, according to the official Uttarakhand government guidelines presented, each pilgrim must register their Yatra at the official website. Please check the official website or refer to the ‘Step-by-Step Kedarnath Dham Registration Process’ section. |
|
| |
|
| ==== Disruption-only ====
| | Do I need to pay for the Kedarnath registration 2026? |
| {{Policy shortcut|BP:DISRUPTONLY}}
| | No, registration is completely free of cost. |
| {{See also|Bharatpedia:Username policy#Usernames violating the BLP policy}}
| |
| Some types of user accounts are considered disruptive and may be blocked without warning, usually indefinitely:
| |
| * Accounts used exclusively for disruptive purposes, such as [[Bharatpedia:Vandalism|vandalism]].
| |
| * {{anchor|COI}}Accounts that appear, based on their edit history, to exist for the sole or primary purpose of promoting a person, company, product, service, or organization. ''See [[Bharatpedia:Conflict of interest]] and [[Bharatpedia:Spam]].''
| |
| * Accounts with [[Bharatpedia:Username policy|inappropriate usernames]].
| |
| * Public accounts (where the password is publicly available or shared with a large group).
| |
| * [[Bharatpedia:Bots|Bots]] operating without [[Bharatpedia:Bots/Requests for approval|approval]] or outside their approval, or that appear to be malfunctioning.
| |
|
| |
|
| === Open or anonymous proxies ===
| | Is there a separate registration process for booking a helicopter to reach Kedarnath? |
| {{Main article|Bharatpedia:Open proxies}}
| | No, during registration, you will be asked about the travel mode; opt for the one that fits your needs. |
| [[Bharatpedia:Open proxies|Open or anonymous proxies]] may be blocked on sight.
| |
|
| |
|
| Non-static IP addresses or hosts that are otherwise not permanent proxies typically warrant blocking for a shorter period of time, as the IP address is likely to be reassigned, or the open proxy is likely to be closed. Many [[Tor (network)|Tor]] proxies, in particular, are "exit nodes" for only a short time; in general, these proxies should not be blocked indefinitely without consideration. See [[Bharatpedia:Blocking IP addresses]] for further details.
| | Can Vaayu Aviation complete the Kedarnath registration 2026 process on my behalf? |
| | Yes, we offer assisted registration services for each pilgrim. Our team will reach out to you to collect your necessary details and ensure an error-free registration completion. |
|
| |
|
| There is also a Bharatpedia project, the [[Bharatpedia:WikiProject on open proxies|WikiProject on open proxies]], which seeks to identify and block open proxy servers.
| | When will Kedarnath registration for 2026 open? |
| | The booking slots for the Kedarnath yatra will open in mid-March or April 2026. |
|
| |
|
| === Enforcing bans ===
| | Can the pilgrim change the registration dates after booking? |
| {{anchor|bans|Bans}}{{further|Bharatpedia:Banning policy}}
| | No, once the registration is done, it becomes non-transferable, since there is a daily pilgrim limit. Further registration will only be accepted if there are any available slots. |
| | |
| A Bharatpedia ban is a formal revocation of editing privileges on all or part of Bharatpedia. A ban may be temporary and of fixed duration, or indefinite and potentially permanent.
| |
| | |
| Blocks may be imposed as a technical measure to enforce a ban. Such blocks are based on the particulars of the ban. Bans that apply to all of Bharatpedia—that is, they are not partial—may be backed up by a sitewide block, which is usually set to apply for the period of the ban. Other bans may be enforced with a partial block.<ref name="er11Jan">Editing restrictions placed before 11 January 2020 should not be converted to partial blocks without consensus to do so. [[Bharatpedia:Requests for comment/Partial blocks#Should partial blocks be used to enforce editing restrictions?]]</ref>
| |
| | |
| === "Not here to build an encyclopedia" ===
| |
| This often-used blocking rationale is described at {{section link|Bharatpedia:Here to build an encyclopedia|Clearly not being here to build an encyclopedia}}.
| |
| | |
| == <span id="Evasion of blocks"></span>Evasion and enforcement ==
| |
| {{redirect|BP:BE|"building (an) encyclopedia"|Bharatpedia:Here to build an encyclopedia}}
| |
| {{See also|Bharatpedia:Sockpuppetry}}
| |
| {{policy shortcut|BP:EVASION|BP:EVADE|BP:BE|BP:BLOCKEVASION}}
| |
| Block evasion is when a user tries to hide from a block or ban under a new username. An administrator may reset the block of a user who intentionally evades a block, and may extend the duration of the block if the user engages in further blockable behavior while evading the block. User accounts or IP addresses used to evade a block should also be blocked.
| |
| | |
| === Edits by and on behalf of blocked editors ===
| |
| {{See also|Bharatpedia:Banning policy#Edits by and on behalf of banned editors}}
| |
| Anyone is free to [[Bharatpedia:Reverting|revert]] any edits made in violation of a block, without giving any further reason and [[BP:NOT3RR|without regard to the three-revert rule]]. However, this does not mean that edits ''must'' be reverted just because they were made by a blocked editor (obviously helpful changes, such as fixing typos or undoing vandalism, can be allowed to stand), but the presumption in ambiguous cases should be to revert. However, in closed discussions, comments by blocked editors should not generally be reverted or struck through.
| |
| | |
| Editors in turn are not permitted to post or edit material at the ''direction'' of a blocked editor (sometimes called '''proxy editing''' or "proxying") unless they can show that the changes are either verifiable or productive and they have independent reasons for making such edits. New accounts that engage in the same behavior as a banned editor or blocked account in the same context, and that appear to be editing Bharatpedia solely for that purpose, are subject to the remedies applied to the editor whose behavior they are imitating.<ref>See [[Bharatpedia:Requests for arbitration/Agapetos angel#Meatpuppets]]. See also: [[Bharatpedia:Tag team]]</ref> See {{section link|Bharatpedia:Sockpuppetry|Meatpuppetry}}.
| |
| | |
| ==== Enforcement by reverting ====
| |
| {{anchor|Enforcement by reverting edits}}
| |
| While reverting edits, take care not to reinstate material that may be in violation of such core policies as [[Bharatpedia:Neutral point of view]], [[Bharatpedia:Verifiability]], and [[Bharatpedia:Biographies of living persons]]. Editors who subsequently reinstate edits originally made by a blocked editor take complete responsibility for the content.
| |
| | |
| It is not possible to revert newly created pages, as there is nothing to which to revert. Accordingly, pages created by blocked editors are eligible for [[BP:CSD#G5|speedy deletion]]. Any editor can use the template {{tl|db-g5}}, or its shortcuts {{tl|db-banned}} or {{tl|db-blocked}}, to mark such a page. If editors other than the blocked editor have made substantial good-faith contributions to the page or its talk page, it is courteous to inform them that the page was created by a blocked editor, and then decide on a case-by-case basis what to do.
| |
| | |
| == When blocking may not be used ==
| |
| {{policy shortcut|BP:BLOCKNO}}
| |
| === Conflicts and involvement ===
| |
| Administrators must not block users with whom they are engaged in a content dispute; instead, they should report the problem to other administrators. Administrators should also be aware of potential conflicts involving pages or subject areas with which they are [[BP:INVOLVED|involved]]. It is acceptable for an administrator to block someone who has been engaging in clear-cut vandalism in that administrator's userspace.
| |
| | |
| === Cool-down blocks ===
| |
| {{policy shortcut|BP:CDB|BP:COOLDOWN}}
| |
| | |
| Blocks intended '''solely''' to "cool down" an [[Bharatpedia:Explode|angry user]] should ''not'' be used, as they often have the opposite effect. However, an angry user who is also being [[Bharatpedia:Disruptive editing|disruptive]] can be blocked to prevent further disruption.
| |
| | |
| === Recording in the block log ===
| |
| {{Policy shortcut|BP:AMENDLOG|BP:LOGAMEND}}
| |
| Blocks should not be used solely for the purpose of recording warnings or other negative events in a user's block log. The practice, typically involving very short blocks, is often seen as punitive and humiliating.
| |
| | |
| Very short blocks may be used to record, for example, an apology or acknowledgement of mistake in the [[Special:Log/block|block log]] in the event of a wrongful or accidental block, if the original block has expired. (If it has not, the message may be recorded in the unblocking reason.)
| |
| | |
| === Against the blocking administrator ===
| |
| A blocked administrator can block the blocking administrator, but should only do so in exceptional circumstances where there is a clear and immediate need, such as in the case of a compromised account. Use of the block tool to further a dispute or retaliate against the original blocking administrator is not allowed. If in doubt, report the issue on the [[BP:ANI|Administrators' noticeboard for incidents]].
| |
| | |
| == Requesting blocks ==
| |
| {{shortcut|BP:BLOCKREQUESTS}}
| |
| Disruptive behavior can be reported, and blocks requested at a specialized venue such as [[Bharatpedia:Administrator intervention against vandalism]] or, if appropriate, [[Bharatpedia:Administrators' noticeboard/Incidents]]. Users requesting blocks should supply credible evidence of the circumstances warranting a block. Administrators are never obliged to place a block, and are free to investigate the situation for themselves. Prior to imposing a block, administrators are expected to be fully familiar with the circumstances of the situation. See also {{section link||Explanation of blocks}}.
| |
| | |
| === Dealing with off-wiki block requests ===
| |
| Administrators who use [[Bharatpedia:IRC channels|Bharatpedia-related IRC channels]] are reminded that, while these channels have legitimate purposes, discussing an issue on IRC necessarily excludes those editors who do not use IRC from the discussion (and excludes all non-administrators from the discussion if it takes place in #bharatpedia-en-admins), and therefore, such IRC discussion is never the equivalent of on-wiki discussion or dispute resolution. [[Bharatpedia:Consensus|Consensus]] about blocks or other subjects should not be formed off-wiki.
| |
| | |
| As the practice of off-wiki "block-shopping" is strongly discouraged, and that except where there is an urgent situation and no reasonable administrator could disagree with an immediate block (e.g. ongoing vandalism or serious violations of the policy on biographies of living persons), the appropriate response for an administrator asked on IRC to block an editor is to refer the requester to the appropriate on-wiki noticeboard.
| |
| | |
| === Self-requested blocks ===
| |
| {{shortcut|BP:SELFBLOCK|BP:BLOCKME}}
| |
| Sometimes, people request that their account be blocked, for example to enforce a [[Bharatpedia:Wikibreak|wikibreak]]. Such requests are typically declined, but there is a [[:Category:Bharatpedia administrators willing to consider placing self-requested blocks|category of administrators who will consider such requests]].
| |
| | |
| As an alternative to requesting a self-block, users may use the [[Bharatpedia:WikiProject User scripts/Scripts/WikiBreak Enforcer|Wikibreak Enforcer]], a user script that can prevent a user from logging in.
| |
| | |
| == Blocking ==
| |
| === Preliminary: education and warnings ===
| |
| {{shortcut|BP:BEFOREBLOCK|BP:BEFOREBLOCKING}}
| |
| * Some of the key precepts of this section may be explained using {{tl|Before blocking}}.
| |
| | |
| Before a block is imposed, efforts should be made to educate users about Bharatpedia policies and guidelines, and to warn them when their behavior conflicts with these. [[Bharatpedia:Welcome, newcomers|Welcome newcomers]], [[Bharatpedia:Please do not bite the newcomers|do not bite them]], and [[Bharatpedia:Assume good faith|assume]] that most people who work on the project are trying to help it, not hurt it. Newcomers should make an effort to learn about [[Bharatpedia:Policies and guidelines|our policies and guidelines]] so that they can learn how to avoid making mistakes. A [[Bharatpedia:Template messages/User talk namespace|variety of template messages]] exist for convenience, although purpose-written messages are often preferable. Template warnings that state that a user may be blocked for disruption or other blockable behavior may also be issued by regular editors rather than by administrators only.
| |
| | |
| However, warnings are not a prerequisite for blocking. In general, administrators should ensure that users who are acting in good faith are aware of policies and are given reasonable opportunity to adjust their behavior before blocking, and it may be particularly desirable to communicate first with such users before blocking. On the other hand, users acting in bad faith, whose main or only use is forbidden activity ([[BP:SOCK|sockpuppetry]], [[Bharatpedia:Vandalism|vandalism]], and so on), do not require any warning and may be blocked immediately.
| |
| | |
| === Explanation of blocks ===
| |
| {{shortcut|BP:EXPLAINBLOCK}}
| |
| | |
| Blocking is a serious matter. The community expects that blocks will be made for good reasons only, based upon reviewable evidence and reasonable judgment, and that all factors that support a block are subject to independent peer review if requested.
| |
| | |
| ==== Notifying the blocked user ====
| |
| Administrators must supply a clear and specific block reason that indicates why a user was blocked. Block reasons should avoid the use of jargon as much as possible so that blocked users may better understand them. Administrators should notify users when blocking them by leaving a message on their user talk page. It is often easier to explain the reason for a block at the time than it is to explain a block well after the event.
| |
| | |
| When implementing a block, a number of ''[[pro forma]]'' block reasons are available in a [[MediaWiki:Ipbreason-dropdown|drop-down menu]]; other or additional reasons can also be added. Users can be notified of blocks and block reasons using a number of convenient template messages—see [[:Category:User block templates]] and [[Bharatpedia:Template messages/User talk namespace#Blocks]].
| |
| | |
| ==== Other important information ====
| |
| If there are any specific recommendations or circumstances that a reviewing administrator would need to know, or that may help to avoid administrator disputes upon review of a block, the blocking administrator should consider including this information in the block notice. For example:
| |
| * When there is information or evidence that may not be obvious, may not be fully appreciated, or may otherwise be relevant.
| |
| * Prior endorsement that if any administrator wishes to unblock, or there is consensus for it, they may without consulting the blocking administrator.
| |
| * Suggested conditions for an unblock.
| |
| | |
| ==== Confidential evidence ====
| |
| {{policy shortcut|BP:BLOCKEVIDENCE}}
| |
| If a user needs to be blocked based on information that will not be made available to all administrators, that information should be sent to the [[BP:ARB|Arbitration Committee]] or a [[Bharatpedia:Checkuser|checkuser]] or [[BP:SIGHT|oversighter]] for action. These editors are qualified to handle non-public evidence, and they operate under strict controls. The community has rejected the idea of individual administrators acting on evidence that cannot be peer-reviewed.
| |
| | |
| An exception is made for administrators holding [[Bharatpedia:Checkuser|Checkuser]] or [[Bharatpedia:Oversight|Oversight]] privileges; such administrators may block users based on non-public information revealed through the checkuser tool, or on edits that have been suppressed ("oversighted") and are inaccessible to administrators. As such, an administrative action is generally viewed to be made in the user's capacity as an oversighter or checkuser, although the action itself is an administrative one. All such blocks are subject to direct review by the [[Bharatpedia:Arbitration Committee|Arbitration Committee]].
| |
| * '''Contact details:''' individual [[BP:CHECK|Checkusers]] and [[BP:SIGHT|Oversighters]] are listed on the relevant pages; they can also be contacted via the [[BP:FUNC|functionaries mailing-list]] (e.g., if in doubt who to contact). Private evidence involving undisclosed paid editing may be sent to ''{{nospam|paid-en-wp|bharatpedia.org}}''.
| |
| | |
| === Implementing blocks ===
| |
| Technical instructions on how to block and unblock, and information on the blocking interface, are available at [[mw:Help:Blocking users]]. The following is advice specifically related to blocking and unblocking on Bharatpedia.
| |
| | |
| ==== IP address blocks ====
| |
| {{Main article|Bharatpedia:Blocking IP addresses}}
| |
| | |
| In addition to the further advice, there are special considerations to take into account when blocking IP addresses. IP address blocks can affect many users, and IP addresses can change. Users intending to block an IP address should at a minimum check for usage of that address, and consider duration carefully. IP addresses should rarely, if ever, be blocked indefinitely. You should notify the Bharatmedia Foundation if the IP is related to a sensitive organization or a government agency.
| |
| | |
| ===== Collateral damage =====
| |
| <!-- This section is linked to from [[BP:SPI]] and also may be linked from other pages-->
| |
| {{shortcut|BP:COLLATERAL}}
| |
| | |
| A block of a range of IP addresses may unintentionally affect other users in that range. Before blocking an IP range, especially for a significant time, you should check for other users who may be unintentionally affected by the range block:
| |
| * unregistered users – [[toolforge:xtools/rangecontribs|Range Contributions – X!'s tools]]
| |
| * registered users – ask a user with [[BP:CHECKUSER|checkuser]] access to check.
| |
| If any are found, an [[BP:IPBE|IP block exemption]] ensures they will not be affected.
| |
| | |
| ==== Duration of blocks ====
| |
| {{Policy shortcut|BP:BLOCKDURATION|BP:BLOCKLENGTH}}
| |
| The purpose of blocking is prevention, not punishment. The duration of blocks should thus be related to the likelihood of a user repeating inappropriate behavior. Longer blocks for repeated and high levels of disruption are to reduce administrative burden; they are made under the presumption that such users are likely to cause frequent disruption or harm in future. Administrators should consider:
| |
| * the severity of the behavior;
| |
| * whether the user has engaged in that behavior before.
| |
| | |
| Blocks on shared or dynamic IP addresses are typically shorter than blocks on registered accounts or static IP addresses made in otherwise similar circumstances, to limit side-effects on other users sharing that IP address.
| |
| | |
| While the duration of a block should vary with the circumstances, there are some broad standards:
| |
| * incidents of disruptive behavior typically result in blocks of from a day to a few days, longer for persistent violations;
| |
| * accounts used exclusively for disruption may be blocked indefinitely without warning;
| |
| * protective blocks typically last as long as protection is necessary, often indefinitely.
| |
| | |
| ===== Indefinite blocks =====
| |
| {{See also|Bharatpedia:Blocking IP addresses#Indefinite blocks}}
| |
| {{redirect|BP:INDEF|indefinitely protected pages|BP:List of indefinitely protected pages}}
| |
| {{Policy shortcut|BP:INDEF}}
| |
| | |
| An '''indefinite block''' is a block that does not have a definite (or fixed) duration. Indefinite blocks are usually applied when there is significant disruption or threats of disruption, or major breaches of policy. In such cases an open-ended block may be appropriate to prevent further problems until the matter can be resolved by discussion. As with all blocks, it is not a punishment. It is designed to prevent further disruption, and the desired outcome is a commitment to observe [[Bharatpedia:Policies and guidelines|Bharatpedia's policies and guidelines]], and to stop problematic conduct in future.
| |
| | |
| Indefinite does not mean "infinite" or "permanent". An indefinitely blocked user may later be [[#Unblocking|unblocked]] in appropriate circumstances. In particularly serious cases in which no administrator would be willing to lift the block, the user is effectively [[Bharatpedia:Banning policy|banned]] by the community.
| |
| | |
| ==== Block log ====
| |
| If the block arose from a discussion per {{section link|Bharatpedia:Banning policy|Community bans and restrictions}}, please include a link to the discussion in the block log. If the block is enforcing a community sanction, please note this. If consensus was to allow for regular administrative review rather than requiring community review, per {{section link|Bharatpedia:Blocking policy|Unacceptable unblocking}}, that should be noted in the log as well.
| |
| | |
| === Setting block options ===
| |
| {{shortcut|BP:OPTIONS}}
| |
| Several options are available to modify the effect of blocks, which should be used in certain circumstances:
| |
| | |
| ==== Editing block options ====
| |
| * '''Sitewide block''' will prevent the user from editing ''any page'' on Bharatpedia with the exception of their own user talk page. This is the option that is set by default, and should be used when there is a reasonable assumption that the account would disrupt ''any'' page, such as [[BP:VOA|vandalism-only accounts]] or users that are [[BP:NOTHERE|clearly not here to write an encyclopedia]].
| |
| * '''Partial block''' will prevent the user from editing a specific set of pages, or from a particular set of [[BP:NAMESPACE|namespaces]]. Either option may be set, or a combination of both may be chosen. There is a software limit of 10 pages per block; beyond this, sitewide blocking should be considered instead.
| |
| | |
| ==== Standard block options ====
| |
| * '''Autoblock any IP addresses used''' will apply an '''[[Bharatpedia:Autoblock|autoblock]]''', or automatic block, on the IP address that the account was last using, as well as any subsequent IP addresses the account tries to edit from while they are blocked with this option set. If a different [[BP:IPBE|non-exempt]] user account logs in from an autoblocked IP address and tries to edit, the user account will also be added to the autoblock list. This option should typically be ''disabled'' when blocking unapproved or malfunctioning bots (so as not to block the bot's operator or any other bots using that IP address), though it should be ''enabled'' when blocking accounts for disruptive or malicious behavior. This option is enabled by default and is only available when applying a block to an account.
| |
| * '''Prevent account creation''' will restrict the user from accessing the [[Special:CreateAccount]] function for the duration of the block. If applied to an IP address or range, it will also prevent all user accounts from being able to create additional accounts if they attempt to do so while behind the blocked IP address or range.<ref name=AccPreventionFootnote>This restriction applies to ''all user accounts'' (including administrators and stewards), regardless of their confirmed status or any local or global user rights they have. Any attempt to create an account while behind a blocked IP or range with this option set will be restricted by the MediaWiki software.</ref> If the autoblock option is also enabled on a block applied to a user account, it will also prevent accounts from being created on the IP address that the blocked user was using. It should typically be ''disabled'' when blocking accounts with inappropriate names (to allow the user to create a new account with an appropriate name), though it should be ''enabled'' when blocking [[Bharatpedia:IU|bad-faith names]] (for example, clear attacks on other users) or [[BP:VOA|vandalism-only accounts]].
| |
| * '''Prevent user from sending email''' will restrict the user from accessing the [[Special:EmailUser]] function for the duration of the block. This option is not checked by default and should '''not''' be enabled when blocking an account except only in cases where either the blocked user abuses it, or uses it to harass, threaten, intimidate, or cause disruption toward other editors. In instances when administrators feel that email abuse is extremely likely, they may use their discretion and enable this option to prevent it from occurring. When enabled, efforts should be taken to ensure that the user's talk page remains unprotected and that the user is aware of other avenues (such as the [[BP:UTRS|Unblock Ticket Request System]]) through which they can discuss the block. While this option can be enabled when blocking IP addresses or IP ranges, it serves no purpose in these situations, since anonymous users do not have access to the function.
| |
| * {{anchor|TPA}}'''Prevent this user from editing their own talk page while blocked''', if checked, will prevent the blocked user from editing their own user talk page (including the ability to create unblock requests) during the duration of their block. This option is not checked by default, and typically should '''not''' be checked; editing of the user's talk page should be disabled only in cases of continued abuse of their user talk page, or when the user has engaged on serious threats, accusations or outing which needs to be prevented from reoccurring. The [[Bharatpedia:Protection policy#Blocked users|protection policy]] has further details in cases where ''other users''<ref>Including sock puppets of blocked users.</ref> are repeatedly causing disruption to the user talk pages of blocked users.
| |
| * '''Prevent logged-in users from editing from this IP address''' will disallow all [[BP:IPBE|non-exempt]] user accounts from editing from the IP address or range during the duration of the block. This option should typically '''not''' be checked, and is typically only used in cases of [[BP:LTA|long-term abuse]], [[BP:SOCK|sock puppetry]], for IP addresses with a history of ''significant and high level'' abuse, or for being an [[Bharatpedia:Open proxies|open proxy]] or location host. See ''hard block'' under the IP address common block list below. This option is disabled by default and is only available when applying a block to an IP address or IP range.
| |
| | |
| === Common blocks imposed ===
| |
| {{shortcut|BP:HARDBLOCK|BP:SOFTBLOCK}}
| |
| There are two common blocks that may be imposed on registered accounts:
| |
| | |
| * A '''soft account block''' (autoblock disabled, account creation allowed) will only block ''the specific account'' from editing. An autoblock is not applied to the IP address the account last used, and other accounts that log in from the IP address are allowed to edit as normal. This is generally used in situations such as blocking promotional usernames or to enforce other [[Bharatpedia:Username policy|username policy]] violations. This allows the blocked account to register a new account with a username that is in compliance with the username policy, or simply choose to edit anonymously under the IP if they decide not to do so.
| |
| * A '''hard account block''' (autoblock enabled, account creation disabled) will apply an autoblock to the IP address the account last used to edit. Any additional IP address that the account attempts to edit from during the duration of the block is also [[Bharatpedia:Autoblock|automatically blocked]] and added to the [[Special:AutoblockList|autoblock list]], and any non-exempt accounts that attempt to edit from an autoblocked IP address will not be able to do so. Accounts cannot be created by any autoblocked IP address(es) or accounts nor by the original account while it is blocked.<ref name=AccPreventionFootnote /> This is typically used in cases of blocking vandalism or to prevent other disruption.
| |
| | |
| There are two common blocks that may be imposed on IP addresses:
| |
| | |
| * A '''soft IP address block''' (anon. only, account creation blocked) is used in most cases of disruption – including vandalism and edit warring, and prevents only anonymous users from editing. It also restricts any account creation by the IP address or by any user accounts while behind the blocked IP address.<ref name=AccPreventionFootnote /> Allowing account creation from a blocked IP is done under unique and special situations.
| |
| * A '''hard IP address block''' (account creation blocked, prevent logged-in users from editing from this IP address) disables all editing and account creation<ref name=AccPreventionFootnote /> from behind the blocked IP address, whether or not from logged in users (except accounts that are [[Bharatpedia:IP block exemption|IP-block exempt]]—these users can edit while behind the blocked IP, but cannot create accounts). This is typically used when the level of vandalism or disruption via creation of "throwaway" accounts is such that all editing from the IP address is to be prevented except after individual checking of requests. [[Bharatpedia:Open proxies|Open proxies]] are hard-blocked on detection, and Tor IP addresses are automatically blocked by [[mw:Extension:TorBlock|the Tor block extension]].
| |
| | |
| === Blocking bots ===
| |
| {{See also|BP:BOTBLOCK}}
| |
| | |
| Automated or semi-automated [[BP:BOT|bots]] may occasionally not operate as intended for a variety of reasons. Bots (or their associated IP address should the actual bot not be readily identifiable) may be blocked until the issue is resolved. Bots should be [[BP:SOFTBLOCK|softblocked]] (autoblock disabled) to ensure the autoblock doesn't affect other unrelated bots sharing the same IP. If only a single task is malfunctioning and the bot supports disabling individual tasks, it is preferable to disable the single malfunctioning task so that other bot tasks can continue running.
| |
| | |
| Bots that are unapproved, or usernames that violate the [[BP:U|username policy]] due to a resemblance to a bot, are immediately and indefinitely blocked if they violate the [[BP:BOTPOL|bot policy]], most commonly by editing outside the operator's or their own [[BP:userspace|userspace]].
| |
| | |
| The edits of a bot are considered to be, by extension, the edits of the editor responsible for the bot. As a result, should a bot operator be blocked, any bot attributed to them may also be blocked for the same duration as that of the blocked editor.
| |
| | |
| === Recording in the block log after a "clean start" ===
| |
| Editors may cite "[[Bharatpedia:Clean start|clean start]]" and rename themselves, asking that their previous username not be disclosed. If such editors have been blocked previously, the administrator who has been requested to make the deletion should contact a [[BP:CHECKUSER|Checkuser]] so that the connection between the accounts can be verified. The Checkuser should then consider adding short blocks to the new account to denote each entry in the user's old account log. Such short blocks should provide protection in case the "clean start" was based on a genuine risk of off-wiki harassment, by not disclosing the previous username, while at the same time eliminating the possibility of [[Bharatpedia:SOCK#Avoiding scrutiny|avoiding the scrutiny]] of the community.
| |
| | |
| The short blocks should be described in the block summary as "previous account block" and the final duration of the block should be noted. Blocks placed in error and lifted early should not be noted at all.
| |
| | |
| == Unblocking ==
| |
| Unblocking or shortening of a block is most common when a blocked user [[BP:APPEAL|appeals a block]]. An [[BP:UNINVOLVED|uninvolved]] administrator acting independently reviews the circumstances of the block, the editor's prior conduct, and other relevant evidence, along with any additional information provided by the user and others, to determine if the unblock request should be accepted. Common reasons include: the circumstances have changed, a commitment to change is given, the administrator was not fully familiar with the circumstances prior to blocking, or there was a clear mistake.
| |
| | |
| {{See also|Bharatpedia:No get out of jail free cards}}
| |
| | |
| === Unacceptable unblocking ===
| |
| {{anchor|NEVERUNBLOCK}}{{shortcut|BP:NEVERUNBLOCK}}
| |
| Unblocking will '''almost never be acceptable''':
| |
| * When it would constitute [[Bharatpedia:Wheel war|wheel warring]].
| |
| * To unblock any of one's own accounts, except in the case of self-imposed blocks.<ref>This prohibition includes blocks applied to one's alternate accounts, including bots. Historically, administrators were able to unblock themselves (the <code>unblockself</code> user right), but this ability was [[phab:T150826|removed in November 2018]]. Stewards can still unblock themselves, and self-imposed blocks can still be removed.</ref>
| |
| * When the block is [[BP:CBAN|implementing a community sanction]] which has not been successfully [[Bharatpedia:Banning policy#Appeals of bans imposed by the community|appealed]]. The community may choose to allow a block to be reviewed in the normal way, by consulting with the closing/blocking administrator, rather than requiring a formal appeal to the community. If there is consensus to allow this, it shall be noted in the closing statement and block log.
| |
| *When the block is designated as a checkuser or oversight block, and the unblocking administrator is not a member of the designated group and does not have permission from someone in that group to carry out the action.
| |
| *When the block is explicitly enforcing an active Arbitration remedy. Arbitration enforcement blocks may be appealed using the [[Bharatpedia:Arbitration Committee/Discretionary sanctions#Modifications by administrators|special appeal provisions]].
| |
| Each of these may lead to sanctions for misuse of administrative tools—possibly including [[Bharatpedia:Removing administrator rights|removing administrator rights]]—even for first-time incidents.
| |
| | |
| There is no predefined limit to the number of unblock requests that a user may issue. However, disruptive use of the unblock template may prompt an administrator to remove the blocked user's ability to edit their talk page. In this case, a block may still be appealed by submitting a request to the [[Bharatpedia:Unblock Ticket Request System|Unblock Ticket Request System]].
| |
| | |
| === Unblock requests ===
| |
| As part of an unblock request, uninvolved editors may discuss the block, and the blocking administrator is often asked to review or discuss the block, or [[#Other important information|provide further information]]. Since the purpose of an unblock request is to obtain review from a third party, the blocking administrators should not decline unblock requests from users when they performed the block. Also, by convention, administrators don't usually review more than one unblock request regarding the same block.
| |
| | |
| Except in cases of unambiguous error or significant change in circumstances dealing with the reason for blocking, administrators should avoid unblocking users without first attempting to contact the blocking administrator to discuss the matter. If the blocking administrator is not available, or if the administrators cannot come to an agreement, then a discussion at [[Bharatpedia:Administrators' noticeboard]] is recommended.
| |
| | |
| Administrators reviewing a block should consider that some historical context may not be immediately obvious. Cases involving sockpuppets, harassment, or privacy concerns are particularly difficult to judge. At times such issues have led to contentious unblocks. Where an uninformed unblock may be problematic, the blocking administrator may '''also''' [[#Other important information|wish to note]] as part of the block notice that there are specific circumstances, and that a reviewing administrator should not unblock without discussing the case with the blocking admin (or possibly [[Bharatpedia:Arbitration Committee|ArbCom]]) to fully understand the matter.
| |
| | |
| If users claim they wish to contribute constructively but there are doubts as to their sincerity, the {{tl|2nd chance}} template can be used to allow them to demonstrate how they will contribute to the encyclopedia, should their unblock request be granted.
| |
| | |
| Any user may comment on an unblock request; however, only administrators may resolve the request (either declining or unblocking).<ref>See July–August 2012 discussion at [[Bharatpedia:Administrators' noticeboard/Archive238#Unblock requests being handled by non-administrators]]</ref>
| |
| | |
| === Blocks in temporary circumstances ===
| |
| Some types of blocks are used in response to particular temporary circumstances, and should be undone once the circumstance no longer applies:
| |
| * Blocks on [[Bharatpedia:Open proxies|open or anonymous proxies]] should be undone once it is confirmed that they have been closed (but be aware some open proxies may be open only at certain times, so careful checking may be needed that it really is apparently no longer in use that way).
| |
| * Blocks of unapproved or malfunctioning bots should be undone once the bots gain approval or are repaired.
| |
| * Blocks for making [[Bharatpedia:No legal threats|legal threats]] should be undone once the threats are confirmed as permanently withdrawn and no longer outstanding.
| |
| | |
| === Unblocks in temporary circumstances ===
| |
| Users may be temporarily and conditionally unblocked to respond to a discussion regarding the circumstances of their block. Such temporary and conditional unblocks are made on the understanding that the users may not edit any pages (besides their user talk page) except the relevant discussion page(s) explicitly specified by the unblocking admin. The users are effectively banned from editing any other pages, and breaching this ban will be sanctioned appropriately. When the discussion concludes, the block should be reinstated unless there is a [[BP:Consensus|consensus]] to overturn the block.
| |
| | |
| === CheckUser blocks ===
| |
| {{See also|Bharatpedia:CheckUser#CheckUser blocks}}
| |
| {{shortcut|BP:CUBL}}
| |
| | |
| Without first consulting a [[Bharatpedia:CheckUser|CheckUser]], administrators must not undo or loosen any block that is specifically identified as a "checkuser" block, such as through the use of the {{tl|checkuserblock}} or {{tl|checkuserblock-account}} templates in the action summary.<ref>Non-CheckUsers must not review CheckUser blocks that require access to CheckUser data, e.g., when an editor is professing innocence or is questioning the validity of the technical findings in any way. Administrators may still decline unblock requests that are made in bad faith, are more procedural in nature, or are off topic.</ref> If an administrator believes that a checkuser block has been made in error, the administrator should first discuss the matter with the CheckUser in question, and if a satisfactory resolution is not reached, should e-mail the [[BP:ARBCOM|Arbitration Committee]]. A reversal or alteration of such a block without prior consultation may result in [[Bharatpedia:Arbitration Committee/Procedures#Removal of permissions|removal of permissions]].<ref>[[Special:Permalink/374236496#Statement on checkuser blocks|Arbitration Committee resolution on CheckUser blocks]]</ref>
| |
| | |
| === Oversight blocks ===
| |
| {{See also|Bharatpedia:Oversight#Oversight blocks}}
| |
| {{shortcut|BP:OSBL}}
| |
| | |
| Administrators must not undo or alter any block that is specifically identified as an "oversight" block, such as through the use of the {{tl|OversightBlock}} template in the action summary, without first consulting an Oversighter. Appeals of blocks that have been marked by an oversighter as [[Bharatpedia:Blocking policy#Confidential evidence|oversight blocks]] must be sent to either the oversight team via email ({{Oversight email}}) to be decided by the English Bharatpedia oversighter team, or to the [[Bharatpedia:Arbitration Committee/Ban appeals|Arbitration Committee]]. Blocks may still be marked by the blocking oversighter as appealable only to the Arbitration Committee, per [[Special:Permalink/374236496#Statement on checkuser blocks|the 2010 statement]], in which case appeals must only be directed to the Arbitration Committee.<ref>[[Special:Permalink/718626027#Motion: Oversight block appeals (Oversight-l)|2016 Arbitration Committee resolution on Oversight-related blocks]]</ref> Unblocking or loosening a block specifically called an "oversight block" without consent of an oversighter may result in [[Bharatpedia:Arbitration Committee/Procedures#Removal of permissions|removal of permissions]].<ref>[[Special:Permalink/542990142#Oversight-related blocks|2013 Arbitration Committee resolution on Oversight-related blocks]]</ref>
| |
| | |
| === Conditional unblock ===
| |
| {{shortcut|BP:CONDUNBLOCK}}
| |
| Administrators may, with the agreement of the blocked user, impose conditions when unblocking. Unblock conditions are designed to prevent recurrence of the behaviour that led to the block (such as a page ban to prevent further edit warring).
| |
| *If the blocked user does not reach an agreement on proposed unblock conditions with an administrator, the blocked user may post another block appeal.
| |
| *Administrators have discretion to set the expiry of unblock conditions, provided that:
| |
| **The unblock conditions of blocks that expire after one year or less will expire after no more than a year,
| |
| **The unblock conditions of blocks that expire after more than a year (including indefinite) may expire up to <u>and including</u> indefinitely.
| |
| *Unblock conditions may include [[BP:PBAN|page bans]], [[BP:TBAN|topic bans]], [[BP:IBAN|interaction bans]], revert restrictions, single account restrictions and other restrictions at the discretion of the unblocking administrator.
| |
| *A partial block may be used to enforce the unblock conditions of a sitewide block.<ref>[[Bharatpedia:Requests for comment/Partial blocks#Can partial blocks be used for conditional unblocks against a full block?]]</ref>
| |
| *If editors breach the unblock conditions or engage in fresh misconduct, they may be blocked or further restricted.
| |
| *After the blocked user has accepted the conditions and been unblocked, the conditions may be appealed only to the unblocking administrator or to [[Bharatpedia:Administrators' noticeboard]].
| |
| *The user will be notified of unblock conditions on their talk page when they are unblocked and a diff/permalink containing the restrictions must be included in the unblock log rationale.
| |
| | |
| == Partial blocks ==
| |
| {{See also|Bharatpedia:Partial blocks}}
| |
| {{policy shortcut|BP:PBPOL}}
| |
| Partial blocks may be used at the discretion of any administrator in accord with the rest of the blocking policy, or community consensus. They may also be used to [[#Enforcing bans|enforce editing restrictions]]<ref name="er11Jan"/> or as a requirement for [[#Conditional unblock|conditional unblocks]].<ref name="RfC">[[Special:Diff/935229256|Partial Blocks authorizing RfC]]</ref>
| |
| | |
| The affected editor may request an unblock following the procedures listed in {{section link||Unblocking}}, using the {{tl|unblock}} template, or appealing at the [[Bharatpedia:Administrators' noticeboard]]. Administrators can unblock a user when they feel the block is unwarranted or no longer appropriate, in accordance with the blocking policy.
| |
| | |
| == Global blocks ==
| |
| {{policy shortcut|BP:GB}}
| |
| {{see also|Bharatpedia:Global actions|m:Global blocks}}
| |
| {{redirect|BP:GB|the go button|Help:Go button}}
| |
| | |
| GlobalBlocking is a [[MediaWiki]] [[mw:Extension:GlobalBlocking|extension]] available to [[m:Stewards|stewards]] to prevent cross-wiki disruption from an IP address or a range of IP addresses. When an IP address or range of IP addresses is globally blocked, they are prevented from editing any public [[Special:SiteMatrix|Bharatmedia wiki]], except for [[m:|Meta-Wiki]], where globally blocked users may [[m:Steward requests/Global#Request for global (un)block|appeal]] the decision. (A global ''block'' is not the same as a [[meta:Global bans|global ''ban'']].) When a user's editing is prevented by a global block, the contents of [[MediaWiki:Globalblocking-ipblocked]] (formerly [[MediaWiki:Globalblocking-blocked]]) are shown as an error message (analogous to [[MediaWiki:Blockedtext]] for locally blocked users). Registered users [[:phab:T17294|cannot be globally blocked]]. The analogous action is [[:meta:Global locks|global locking]], which prevents anyone from logging into the account.
| |
| | |
| A current list of globally blocked IP addresses is available at [[Special:GlobalBlockList]].
| |
| | |
| === Unblocking and appeal ===
| |
| ''Local whitelisting'' — An IP address which is globally blocked can be unblocked locally (to edit the specific wiki concerned ''only''), by any local [[BP:ADMIN|administrator]], at [[Special:GlobalBlockWhitelist]]. It is not possible to override global locks locally.
| |
| | |
| ''Appeal against a global block'' — Globally blocked IP addresses and globally locked users may appeal through the email queue to {{nospam|stewards|bharatmedia.org}}. Globally blocked IP addresses may also appeal through their meta talk page, if access to it has not been revoked.
| |
| | |
| == See also ==
| |
| {{Bharatpedia glossary}}
| |
| * [[Block (Internet)]]
| |
| * [[Bharatpedia:Banning policy#Difference between bans and blocks|Difference between bans and blocks]]
| |
| * [[MediaWiki:Blockedtext]] – the message shown to blocked users when they attempt to edit
| |
| * [[Bharatpedia:Appealing a block]] – information about contesting a block
| |
| * [[Bharatpedia:Autoblock]]
| |
| * [[Bharatpedia:Blocking IP addresses]] and [[Bharatpedia:Blocking IP addresses#Sensitive IP addresses|sensitive IP addresses]] – information relating to blocking IP addresses
| |
| * [[Bharatpedia:Guide to appealing blocks]]
| |
| * [[Bharatpedia:Global actions]]
| |
| * [[Bharatpedia:Here to build an encyclopedia]]
| |
| * [[Bharatpedia:Template messages/User talk namespace]]
| |
| * [[Bharatpedia:WikiWar]]
| |
| * [[meta:Global blocks]]
| |
| * [[:Category:User block templates|User block templates]]
| |
| * [[User:ThisIsaTest]], created for blocking practice
| |
| * [[Bharatpedia:Zero tolerance]], a short essay on no warning blocks
| |
| | |
| == Notes ==
| |
| <references />
| |
| {{notelist}}
| |
| {{Administrators' guide|state=collapsed}}
| |
| {{Bharatpedia accounts|collapsed}}
| |
| [[Category:Bharatpedia blocking|*]]
| |
Kedarnath Yatra 2026 Registration Process
Kedarnath is one of the Char Dham and twelve Jyotirlingas of Lord Shiva; Char Dham is known as a path to Moksh. Every Hindu must visit the Char Dham at least once in their lifetime. Each Dham reflects its own unique ancient traditions and has its own significance. The four dhams are Yamunotri Dham, Gangotri Dham, Kedarnath Dham, and Badrinath Dham.
Kedarnath registration is compulsory for all pilgrims since it is a government-mandatory registration process; not only that this registration ensure the pilgrim’s safety, crowd management, as well as a smooth travel experience. Without completing the registration, pilgrims will not be able to move ahead of the checkpoint. The registration can be done at the official portal of Uttarakhand Tourism. Also, keep in mind that this registration applies to every age category and gender. Vaayu Aviation believes in assisting the pilgrims with a smooth and guided government registration process, ensuring government guideline compliance.
Step-by-Step Kedarnath Dham Registration Process 2026
Below is the complete Kedarnath registration 2026 process guide-
Step 1: Visit the official Uttarakhand tourism portal using the link mentioned below- https://registrationandtouristcare.uk.gov.in/
Step 2: Register/Login to the web portal, followed by entering the correct personal details of the pilgrim, including name, age, and gender.
Step 3: Choose your preferred Kedarnath 2026 darshan dates. Government authorities need it to check daily availability limits.
Step 4: Upload government-authorised ID proof and a photograph of the pilgrim.
Step 5: Select your travelling mode (helicopter, foot, or pony).
Step 6: Submit and download your Yatra e-pass; it will have a QR Code, which will further be scanned at the Shrine’s checkpoint. Make sure to carry it for checkpoint verification.
You can register from any digital device (phone, desktop, or laptop).
Kedarnath Registration Fees at
Kedarnath registration 2026 is free of cost, i.e., there is no separate cost of registration. Pilgrim can register through the registrationandtouristcare.uk.gov.in official Uttarakhand portal.
Documents Required for Kedarnath Registration
The key documents required before registration are-
Government-issued photo ID (such as Aadhar/ PAN/ Voter ID).
Passport-size photograph of every individual
Current phone number for One-time password verification.
Why is Kedarnath Registration Important in 2026?
Registrations help the authorities to monitor pilgrims and offer emergency assistance if needed.
Tracks the daily visitor limits to avoid overcrowding at the Dham.
Pre-bookings of travel and stays in order to avoid last-minute hassle.
Enable emergency support and health monitoring.
Registration helps in balancing a smooth coordination among the local authorities of Uttarakhand to avoid any future conflicts.
If you have not registered for the Kedarnath yatra, then you will not be allowed to enter the Kedarnath temple.
Important Guidelines for Kedarnath Pilgrims
Pilgrims must carry their Yatra e-pass (in the form of a digital or hard copy).
Pilgrims must visit the Kedarnath temple on their registered date only.
In case of a missed slot, the pilgrims will not be allowed to transfer their registration.
It is essential to carry a medical kit, as well as follow the weather and safety advisories regularly.
Kedarnath temple has daily visitor limits; crossing the limit would create an imbalance and may even lead to penalties.
Visiting Kedarnath Without Registration?
You will be prohibited from entering the Kedarnath temple without pre-registration. Pilgrims who do not have a Yatra e-pass can not go beyond the Patna check post or the Sonprayag check post. The key aim of the Uttarakhand government behind mandating this registration is to ensure effective crowd management and pilgrims’ safety. Hence, this registration is made free so that every devotee can visit.
Assisted Kedarnath Registration by Vaayu Aviation- Start Your Kedarnath Journey Today
Vaayu Aviation brings you hassle-free, convenient, and comfortable Kedarnath Yatra packages for all devotees planning their yatra in 2026. We at Vaayu Aviation believe in assisting the pilgrims with a smooth and guided registration process, ensuring government guideline compliance so that you do not feel stressed at the last moment.
FAQs
Is Kedarnath registration necessary?
Yes, according to the official Uttarakhand government guidelines presented, each pilgrim must register their Yatra at the official website. Please check the official website or refer to the ‘Step-by-Step Kedarnath Dham Registration Process’ section.
Do I need to pay for the Kedarnath registration 2026?
No, registration is completely free of cost.
Is there a separate registration process for booking a helicopter to reach Kedarnath?
No, during registration, you will be asked about the travel mode; opt for the one that fits your needs.
Can Vaayu Aviation complete the Kedarnath registration 2026 process on my behalf?
Yes, we offer assisted registration services for each pilgrim. Our team will reach out to you to collect your necessary details and ensure an error-free registration completion.
When will Kedarnath registration for 2026 open?
The booking slots for the Kedarnath yatra will open in mid-March or April 2026.
Can the pilgrim change the registration dates after booking?
No, once the registration is done, it becomes non-transferable, since there is a daily pilgrim limit. Further registration will only be accepted if there are any available slots.
