বাধাদান করার মাধ্যমে প্রশাসকগণ অবদানকারীকে উইকিপিডিয়ায় কোনো রকম সম্পাদনা করা থেকে বিরত রাখতে পারেন। ধ্বংসাত্মক কর্মকাণ্ড ও উইকিপিডিয়ার জন্য ক্ষতিকর কোনো কাজ থেকে উইকিপিডিয়াকে রক্ষা করতেই এই বাধাদান, ব্যবহারকারীকে শাস্তি দেবার জন্য নয়। বাধাদান একদিকে যেমন ব্যবহারকারীকে উইকিপিডিয়ার জন্য ক্ষতিকর কোনো কাজ না করার ব্যাপারে সচেতন করে তেমনি, গঠনমূলক সম্পাদনা করার জন্য তাকে ও অন্যদের উৎসাহ দেয়।  প্রশাসকদের আলোচনাসভায় কোনো ব্যবহারকারী বাধাদানের জন্য আবেদন করতে পারেন। কী কারণে বাধা দেওয়া হবে, তা পর্যাপ্ত প্রমাণসহ লেখার জন্য ব্যবহারকারীকে সেখানে অনুরোধ করা হচ্ছে।  উদ্দেশ্য ও লক্ষ্য কোনো পৃষ্ঠাকে কোনোরকম ক্ষতি থেকে রক্ষা করা ও ভবিষ্যতে তা এ ধরনের সমস্যা এড়িয়ে চলার জন্য বাধাদান পদ্ধতি ব্যবহার করা হয়।  সমস্যাগুলি পুনরাবৃত্তি হলে বাধাদানের মেয়াদকাল বাড়তে পারে। ব্যবহারকারী বিরুদ্ধে প্রতিশোধ বা শাস্তি হিসেবে নয় বরং প্রকল্প এবং অন্যান্য ব্যবহারকারীদের ব্যাঘাত এবং অনুপযুক্ত আচরণ থেকে রক্ষা করতে এবং ভবিষ্যতে অনুপযুক্ত আচরণের পুনরাবৃত্তি রোধ করার জন্য এ পদ্ধতি। বাধাদান হল সবচেয়ে শক্তিশালী হাতিয়ার যা প্রশাসকদের উপর ন্যস্ত করা হয়, যারা হস্তক্ষেপ করার পূর্বে পরিস্থিতির সাথে পরিচিত হওয়া উচিত যাতে কাউকে বাধাদানের আগে  ইস্যুটি ভালোভাবে বুঝা যায় এবং বাধাদানের উপযুক্ত কিনা গণ্য করা যায়।   সাধারণভাবে, একবার কোনো বিষয় "ঠাণ্ডা" হয়ে গেলে এবং বর্তমান ক্ষতির ঝুঁকি স্পষ্টভাবে শেষ হয়ে গেলে,  যদি একটি চলমান বা গুরুতর উদ্বেগ অব্যাহত থাকে, বা ব্যবহারকারীর সম্ভাব্য অনুমোদনের অনুমতি দেওয়ার জন্য বেশ কয়েকটি সংঘাত নিরসন প্রক্রিয়া বিদ্যমান থাকে তাহলে এপরিস্থিতিতে,  পূর্ব আলোচানায় বাধাপ্রাপ্ত ব্যবহারকারী পুনরায় চালু করা সাধারণত উপযুক্ত হবে না   বাধা তুলে দেয়ার জন্যে আপিল করা যেতে পারে। বাধা মুক্ত করার অনুরোধগুলিও  আবেদন ও বাধাদানের কারণ পর্যালোচনা আলোকে সিদ্ধান্ত নেওয়া হয়। যদি ব্যবহারকারী একই ধরনের সমস্যা তৈরি থেকে বিরত থাকতে সম্মত হন এবং বিষয়টি থেকে শিক্ষা নিয়েছেন বলে মনে হয়, অথবা যদি পরিস্থিতি সাময়িক ছিল এবং এখন শেষ হয়ে গেছে তাহলে একজন ব্যবহারকারী অবরুদ্ধ থেকে মুক্তি পেতে পারে। অনুরূপভাবে, যে ব্যবহারকারী পূর্বে অন্য অবরোধ থেকে মুক্তির পর অনুপযুক্ত আচরণে ফিরে এসেছেন, তাদের অবরোধের অনুরোধটি পর্যালোচনাপূর্বক প্রত্যাখ্যান করা যেতে পারে, যাতে পরিবর্তনের গুরুত্ব এবং আচরণের অগ্রহণযোগ্যতার উপর জোর দেওয়া যায়।   বাধাদান কখনো শাস্তিমূলক উদ্দেশ্যে নয়:    প্রতিশোধ নিতে;  অপমান করা;  শাস্তি; অথবা  যদি উদ্বেগ হওয়ার মতো কোন আচরণে সমস্যা না থাকে।   বাধা দেয়ার উদ্দেশ্যে হওয়া  উচিত:    উইকিপিডিয়ার আসন্ন বা অব্যাহত ক্ষতি এবং ব্যাহত হওয়া রোধ করা;  বর্তমান, বিঘ্নমূলক আচরণের ধারাবাহিকতা বন্ধ করা; এবং  সম্প্রদায়ের নীতিমালায় মধ্যে আরও সক্রীয়করণ, উপযোগী সম্পাদনা শৈলীকে উত্সাহিত করা।  একই ভুল বা সমস্যার পুনরাবৃত্তির আশংকার উপর ভিত্তি করে প্রতিরোধ করা। উদাহরণস্বরূপ, যদিও কিছুদিন আগে একজন সম্পাদককে বাধাদান করা  করা যুক্তিযুক্ত হয়ে থাকলে, এই ধরনের বাধাদান নতুন করে যুক্তিযুক্ত হতে পারে না,  যদি ব্যবহারকারী তৈরি সমস্যাগুলো বা একই ভুল বন্ধ হয়ে যায় বা আচরণগত সমস্যাগুলি ব্যবহারকারী নিজ থেকে সমাধান করে নেয়।   বাধাদানের ক্ষেত্রে সাধারণ যুক্তি   ব্লক/বাধাদানের জন্য কয়েকটি সাধারণ যুক্তি নীচে দেওয়া হল।  একটি নিয়ম ভঙ্গ করলে বা  সন্দেহ হলেই কোনো ব্যবহারকারীকে বাধাদানের বিপরীতে  অন্যান্য প্রশাসকদের সাথে পরামর্শ করতে উৎসাহিত করা হয়। একটি সম্ভাব্য বিতর্কিত কোনো বিষয়ে বাধাদানের পর, পিয়ার পর্যালোচনার জন্য ঘটনাটি প্রশাসকদের নোটিশবোর্ডে বাধাদানের একটি টিকা তৈরি করা ভাল কাজ হতে পারে।  নতুন ব্যবহারকারীদের সাথে আচরণ করার সময় প্রশাসকদের বিশেষ যত্ন নেওয়া উচিত। কারণ নতুন সম্পাদক/উইকিপিডিয়ান প্রথমত উইকিপিডিয়া নীতি এবং আচরণের সাথে অপরিচিত, এবং তাই তাদের আচরণ প্রাথমিকভাবে বিঘ্নিত হতে পারে। এই নতুন ব্যবহারকারীদের অতিরিক্ত নিয়ম-নীতি বা শক্ত ভাষায় নোটিশ করলে ভবিষ্যতে তাদের সম্পাদনা থেকে নিরুৎসাহিত করতে পারে।  দেখুন: উইকিপিডিয়া:দয়া করে নতুন ব্যবহারকারীকে দংশাবেন না।   সুরক্ষা  উইকিমিডিয়া ফাউন্ডেশন, এর ব্যবহারকারী বা জনসাধারণের অধিকার, সম্পত্তি রক্ষা বা নিরাপত্তার জন্য প্রয়োজনে একজন ব্যবহারকারীকে অবরুদ্ধ করা যেতে পারে। সাইটকে সুরক্ষিত রাখতে নিম্নোক্ত কারণে বাধাদান করার প্রয়োজন হতে পারে:  ক্রমাগত বা গুরুতর ব্যক্তিগত আক্রমণ;  ব্যক্তিগত, পেশাদার বা আইনি হুমকি প্রদান (উইকিপিডিয়া সাইটের বাইরেসহ);  ব্যবহারকারীদের বিপদে ফেলার ক্রিয়াকলাপ;   উইকিপিডিয়া:শিশু সুরক্ষা অনুসারে, শিশুদের সুরক্ষায় বিপত্তি করতে পারে এমন ক্রিয়াকলাপ;  অন্যের ব্যক্তিগত তথ্য প্রকাশ (তথ্য সঠিক হোক বা না হোক);  ক্রমাগত কপিরাইট লঙ্ঘন;  জীবিত ব্যক্তিদের সম্পর্কে অপ্রত্যাশিত, দুর্বল বা ভুলভাবে উল্লেখিত বা সম্ভাব্য মানহানিকর তথ্য ক্রমাগত যোগ; বা  একটি অ্যাকাউন্ট বেহাত হয়েছে বলে মনে হলে (জরুরী ব্যবস্থা হিসাবে), যেমন, অ্যাকাউন্টটি নিবন্ধিত ব্যক্তি ব্যতীত অন্য কেউ ব্যবহার করছে বলে বিশ্বাস করার কারণ থাকলে।   ব্যবচ্ছেদ   একজন ব্যবহারকারীকে অবরুদ্ধ করা হতে পারে যখন তাদের আচরণ প্রকল্পটিকে মারাত্মকভাবে ব্যাহত করে; অর্থাৎ, যখন তাদের আচরণ নাগরিক, কলেজের পরিবেশের সাথে অসঙ্গতিপূর্ণ এবং একটি বিশ্বকোষ তৈরি করার জন্য সম্পাদকদের একসাথে কাজ করার প্রক্রিয়াতে হস্তক্ষেপ করে। এর প্রতিক্রিয়ায় ব্যাঘাতের জন্য ব্লক করা প্রয়োজন হতে পারে:  ধ্বংসপ্রবণতা;  চরম অসভ্যতা;  হয়রানি;  স্প্যামিং;  deliberately tripping the edit filter  breaching the policies or guidelines, especially sock puppetry;  attempts to coerce actions of editors through threats of actions outside the Wikipedia processes, whether onsite or offsite.  Edit warring, especially breaches of the three-revert rule, often results in a block, either from the pages the user is disrupting or from the entire site.   শুধুমাত্র ব্যবচ্ছেদ   Some types of user accounts are considered disruptive and may be blocked without warning, usually indefinitely:  Accounts used exclusively for disruptive purposes, such as vandalism.  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 Wikipedia:Conflict of interest and Wikipedia:Spam.  Accounts with inappropriate usernames.  Public accounts (where the password is publicly available or shared with a large group).  Bots operating without approval or outside their approval, or that appear to be malfunctioning.   খোলা বা বেনামী প্রক্সি   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 proxies, in particular, are "exit nodes" for only a short time; in general, these proxies should not be blocked indefinitely without consideration. See Wikipedia:Blocking IP addresses for further details.  There is also a Wikipedia project, the WikiProject on open proxies, which seeks to identify and block open proxy servers.   নিষেধাজ্ঞা বলবৎ   A Wikipedia ban is a formal revocation of editing privileges on all or part of Wikipedia. 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 Wikipedia—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.Editing restrictions placed before 11 January 2020 should not be converted to partial blocks without consensus to do so. Wikipedia:Requests for comment/Partial blocks#Should partial blocks be used to enforce editing restrictions?   "এখানে বিশ্বকোষ তৈরির জন্য আসেননি"  This often-used blocking rationale is described at .   Evasion and enforcement   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   Anyone is free to revert any edits made in violation of a block, without giving any further reason and 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 Wikipedia solely for that purpose, are subject to the remedies applied to the editor whose behavior they are imitating.See Wikipedia:Requests for arbitration/Agapetos angel#Meatpuppets. See also: Wikipedia:Tag team See .   Enforcement by reverting   While reverting edits, take care not to reinstate material that may be in violation of such core policies as Wikipedia:Neutral point of view, Wikipedia:Verifiability, and Wikipedia: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 speedy deletion. Any editor can use the template , or its shortcuts  or , 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    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 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   Blocks intended solely to "cool down" an angry user should not be used, as they often have the opposite effect. However, an angry user who is also being disruptive can be blocked to prevent further disruption.   Recording in the block log  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 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 Administrators' noticeboard for incidents.   Requesting blocks   Disruptive behavior can be reported, and blocks requested at a specialized venue such as Wikipedia:Administrator intervention against vandalism or, if appropriate, Wikipedia: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 .   Dealing with off-wiki block requests  Administrators who use Wikipedia-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 #wikipedia-en-admins), and therefore, such IRC discussion is never the equivalent of on-wiki discussion or dispute resolution. 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   Sometimes, people request that their account be blocked, for example to enforce a wikibreak. Such requests are typically declined, but there is a category of administrators who will consider such requests.  As an alternative to requesting a self-block, users may use the Wikibreak Enforcer, a user script that can prevent a user from logging in.   Blocking   Preliminary: education and warnings    Some of the key precepts of this section may be explained using .  Before a block is imposed, efforts should be made to educate users about Wikipedia policies and guidelines, and to warn them when their behavior conflicts with these. Welcome newcomers, do not bite them, and 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 our policies and guidelines so that they can learn how to avoid making mistakes. A 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 (sockpuppetry, vandalism, and so on), do not require any warning and may be blocked immediately.   Explanation of blocks   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 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 Wikipedia: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   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 Arbitration Committee or a checkuser or 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 Checkuser or 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 Arbitration Committee.  Contact details: individual Checkusers and Oversighters are listed on the relevant pages; they can also be contacted via the functionaries mailing-list (e.g., if in doubt who to contact). Private evidence involving undisclosed paid editing may be sent to .   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 Wikipedia.   IP address blocks   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 Wikimedia Foundation if the IP is related to a sensitive organization or a government agency.   Collateral damage   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 – Range Contributions – X!'s tools  registered users – ask a user with checkuser access to check. If any are found, an IP block exemption ensures they will not be affected.   Duration of blocks   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   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 Wikipedia'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 unblocked in appropriate circumstances. In particularly serious cases in which no administrator would be willing to lift the block, the user is effectively banned by the community.   Block log  If the block arose from a discussion per , 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 , that should be noted in the log as well.   Setting block 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 Wikipedia 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 vandalism-only accounts or users that are 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 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 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 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.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. 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 bad-faith names (for example, clear attacks on other users) or 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 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.  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 protection policy has further details in cases where other usersIncluding sock puppets of blocked users. 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 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 long-term abuse, sock puppetry, for IP addresses with a history of significant and high level abuse, or for being an 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   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 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 automatically blocked and added to the 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. 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. 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 from behind the blocked IP address, whether or not from logged in users (except accounts that are 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. Open proxies are hard-blocked on detection, and Tor IP addresses are automatically blocked by the Tor block extension.   Blocking bots   Automated or semi-automated 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 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 username policy due to a resemblance to a bot, are immediately and indefinitely blocked if they violate the bot policy, most commonly by editing outside the operator's or their own 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 "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 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 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 will almost never be acceptable:  When it would constitute wheel warring.  To unblock any of one's own accounts, except in the case of self-imposed blocks.This prohibition includes blocks applied to one's alternate accounts, including bots.  Historically, administrators were able to unblock themselves (the unblockself user right), but this ability was removed in November 2018. Stewards can still unblock themselves, and self-imposed blocks can still be removed.  When the block is implementing a community sanction that has not been successfully 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, unless the unblocking administrator is a member of the designated functionary group, or has approval 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 arbitration enforcement appeal provisions. Each of these may lead to sanctions for misuse of administrative tools—possibly including 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 Unblock Ticket Request System.   বাধা অপসারণের অনুরোধ  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 provide further information. Since the purpose of an unblock request is to obtain review from a third party, the administrators who performed the block should not decline unblock requests. 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 Wikipedia: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 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 ArbCom) to fully understand the matter.  If users claim they wish to contribute constructively but there are doubts as to their sincerity, the  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 (by either declining or unblocking).See July–August 2012 discussion at    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 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 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 consensus to overturn the block.   CheckUser blocks   Without first consulting with a CheckUser and receiving approval, administrators must not undo or "loosen" (lowering the block duration or disabling any block options applied) any block set, or unblock any user when the block is specifically identified as a "CheckUser block", such as through the use of the  or  templates in the action summary, or by explicitly stating in the action summary that the block is a "CheckUser block" or is "checkuser-related".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. 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 Arbitration Committee. Any unauthorized reversal or alteration of such a block and without prior consultation and approval from a CheckUser may result in removal of permissions.Arbitration Committee resolution on CheckUser blocks   Oversight blocks   Without first consulting with an Oversighter and receiving approval, administrators must not undo or "loosen" (lowering the block duration or disabling any block options applied) any block set, or unblock any user when the block is specifically identified as an "Oversight block", such as through the use of the  template in the action summary, or by explicitly stating in the action summary that the block is an "Oversight block" or is "Oversight-related". Appeals of any Oversight blocks that are set must be sent to either the Oversight team via email () to be discussed in private by the English Wikipedia Oversight team, or to the Arbitration Committee. Blocks may still be marked by the blocking Oversighter as appealable only to the Arbitration Committee, per the 2010 statement, in which case appeals must only be directed to the Arbitration Committee.2016 Arbitration Committee resolution on Oversight-related blocks Any unauthorized reversal or alteration of such a block and without prior consultation and approval from an Oversighter may result in removal of permissions.2013 Arbitration Committee resolution on Oversight-related blocks   Conditional unblock   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 and including indefinitely. Unblock conditions may include page bans, topic bans, 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. 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 Wikipedia: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. The restrictions should be (but do not have to be) logged at Final warnings / Unblock conditions.   আংশিক বাধাদান   আংশিক বাধাদান যেকোনো প্রশাসক অন্যান্য বাধাদান নীতি অথবা সম্প্রদায়ের ঐকমত্য অনুযায়ী নিজ বিবেচনায় ব্যবহার করতে পারেন। এটি সম্পাদনা সংক্রান্ত সীমাবদ্ধতা কার্যকর করার জন্যও বা শর্তসাপেক্ষ বাধা অপসারণের পূর্বশর্ত হিসেবেও ব্যবহার করা যেতে পারে।আংশিক বাধাদানের জন্য অনুমোদন দেয়া ইংরেজি উইকিপিডিয়ার মন্তব্যের অনুরোধ  আংশিক বাধাপ্রাপ্ত সম্পাদক ে তালিকাভুক্ত পদ্ধতি অনুসরণ করে  টেমপ্লেট ব্যবহার করে অথবা উইকিপিডিয়া:প্রশাসকদের আলোচনাসভায় আবেদন করতে পারেন। প্রশাসকরা যদি মনে করেন যে, বাধাদান বাধাদানটি অযৌক্তিক বা বর্তমানে আর উপযুক্ত নয়, তখন তারা বাধাদান নীতি অনুসারে কোনও ব্যবহারকারীর বাধা অপসারণ করতে পারেন।   বৈশ্বিক বাধাদান   বৈশ্বিক বাধাদান মিডিয়াউইকির একটি এক্সটেনশন, যা স্টুয়ার্ডদের জন্য উন্মুক্ত, যা কোনো আইপি ঠিকানা, আইপি ঠিকানার একটি পরিসর বা একটি অ্যাকাউন্ট থেকে আন্তঃউইকি বিঘ্ন রোধ করতে ব্যবহৃত হয়। যখন কোনো আইপি ঠিকানা, আইপি ঠিকানার একটি পরিসর বা অ্যাকাউন্ট বৈশ্বিকভাবে বাধাদান করা হয়, তখন তারা যেকোনো পাবলিক উইকিমিডিয়া উইকিতে সম্পাদনা করতে পারে না, তবে মেটা-উইকি ব্যতীত; সেখানে বৈশ্বিকভাবে বাধাদানপ্রাপ্ত ব্যবহারকারীরা এই সিদ্ধান্তের বিরুদ্ধে আপিল করতে পারে। (বৈশ্বিক বাধাদান এবং বৈশ্বিক নিষেধাজ্ঞা এক নয়।) বৈশ্বিকভাবে বাধাদানের পাশাপাশি, নিবন্ধিত ব্যবহারকারীরা (অস্থায়ী অ্যাকাউন্ট ছাড়া) বৈশ্বিক তালাবদ্ধও হতে পারে, যা কাউকে সেই অ্যাকাউন্টে লগইন করতে বাধা দেয়।  বর্তমানে বৈশ্বিকভাবে বাধাদানকৃত আইপি ও অ্যাকাউন্টের তালিকাটি বিশেষ:বৈশ্বিক বাধাদানের তালিকায় পাওয়া যাবে।   বাধা অপসারণ ও আবেদন  স্থানীয় সাদা তালিকাভুক্তি — যে কোনো বৈশ্বিকভাবে বাধাদানপ্রাপ্ত আইপি ঠিকানা বা অ্যাকাউন্টকে স্থানীয়ভাবে বাধাদান প্রত্যাহার করা যেতে পারে (শুধুমাত্র সংশ্লিষ্ট নির্দিষ্ট উইকিতে সম্পাদনার জন্য), যা কোনো স্থানীয় প্রশাসক বিশেষ:বৈশ্বিক বাধাদানের সাদাতালিকা থেকে করতে পারেন। এর একটি লগ বিশেষ:লগ/gblblock পাতায় পাওয়া যাবে। বৈশ্বিক তালাবদ্ধকরণ স্থানীয়ভাবে অকার্যকর করা সম্ভব নয়। বৈশ্বিক বাধাদানের বিরুদ্ধে আবেদন — বৈশ্বিকভাবে বাধাদানপ্রাপ্ত আইপি ঠিকানা ও অ্যাকাউন্ট এবং বৈশ্বিকভাবে তালাবদ্ধ ব্যবহারকারীরা -এ ইমেইল করার মাধ্যমে আবেদন করতে পারেন। বৈশ্বিকভাবে বাধাদানপ্রাপ্ত আইপি ঠিকানা ও ব্যবহারকারীরা, যদি তাদের সেই অধিকার প্রত্যাহার না করা হয়ে থাকে, তবে তাদের মেটা আলোচনা পৃষ্ঠার মাধ্যমেও আপিল করতে পারেন।   আরও দেখুন   সংরক্ষণ নীতি  নীতিমালা ও নির্দেশাবলী   তথ্যসূত্র   বিষয়শ্রেণী:উইকিপিডিয়ার প্রশাসন