Jump to content

વિકિવિધેય:અવરોધ નીતિ

From Wikifunctions
This page is a translated version of the page Wikifunctions:Blocking policy and the translation is 36% complete.

Administrators are given the ability to administer blocks to users when appropriate. A blocked user is usually restricted from editing, among other things. In a general sense, blocks are a last resort for behaviour that has the potential to damage Wikifunctions or disrupt its collegial atmosphere. Blocks may be sitewide or partial (affecting only certain actions). In this way, blocking is designed to be a preventative measure and not a punitive one; "cool-down" blocks are not condoned.


અવરોધો ઘણા કારણોસર લાગી શકે છે. એમાંના અમુક સામાન્ય કારણો નીચે મુજબ છે:

  • ભાંગફોડ. વિક્ષેપક સંપાદનો અવરોધને આમંત્રણ આપી શકે છે. ઉદાહરણ તરીકે:
    • બિનજરૂરી અશ્લીલતાનો સમાવેશ
    • અર્થહીન લખાણ
    • પાનાંમાંથી સામગ્રી દૂર કરવી
  • સ્પેમ.
  • પ્રકાશનાધિકાર ઉલ્લંઘન.
  • Edit warring.
  • Personal attacks or harassment. Accounts and IP addresses which are used primarily to create a hostile environment for another user may be blocked. Good faith disputes between users, however, should be brought to project chat for outside input. Tracking a user's contributions for policy violations is not harassment.
  • Unauthorized or non-responsive bot accounts. Bot accounts not authorized by the Wikifunctions community are not allowed to operate on Wikifunctions, and questionable bot-like editing that cannot be explained by the user should be blocked until discussion takes place. Bot proposals can be discussed at WF:Bots or project chat. Bots may not be operated on Wikifunctions without prior approval (which can be sought at WF:Bots/Requests).
  • Approved bot accounts that are temporarily malfunctioning. This is to prevent additional damage until the bot-owner can address the problem.
  • અયોગ્ય સભ્યનામો.
  • Evasion of blocks. An administrator may reset the block of a user who intentionally evades a block (and revert their contributions), and may extend the duration of the block if the user engages in further blockable behaviour while evading the block. User accounts or IP addresses used to evade a block may and should also be blocked.
  • Abusing multiple accounts to mislead, deceive, disrupt, distort consensus or to evade blocks or other sanctions. Secondary accounts are typically blocked indefinitely. The primary account may or may not be subject to new or extended blocks depending on the circumstances.
  • Open or anonymizing proxies are typically blocked upon detection in accordance with Wikimedia-wide policy. The normal duration of such blocks is one year.

‌ પ્રબંધકો માટે સૂચનો

અવરોધિત કરતા પહેલા

  • For blocks based on disruptive behaviour, such as vandalism, repeated copyright violations and manual promotional activities, ensure that the user has been appropriately warned, preferably using a block warning template. No warning is necessary when blocking open proxies and users with inappropriate or abusive usernames. Accounts and IP addresses used solely for severely disruptive purposes such as automated spamming, serious vandalism or harassment may also be blocked without prior warning.
  • Controversial blocks may be discussed at the blocks and protections noticeboard, preferably before they are applied if at all possible. As a rule of thumb, when in doubt, do not block.
  • Range blocks are especially powerful tools, and discussion of these is particularly encouraged. Range blocks with a duration longer than 24 hours should be discussed with a checkuser to assess the likely impact.

અવરોધિત કરતી વખતે

  • Blocks can be applied to registered users, IP addresses or address ranges.
  • As blocks are preventative rather than punitive, use a block duration that is proportional to the time likely needed for the user to familiarize themselves with relevant policies and adjust their behaviour. Also consider the user's past behaviour and the severity of the disruption. When blocking IP addresses, keep in mind that innocent third parties sharing the same addresses may be affected.
  • Provide a reason for the block. The rationale should preferably use links to relevant policies to help the blocked user understand why they have been blocked. Where appropriate, diffs or permanent links documenting the reason for the block are also helpful.
  • Account creation should be prevented in most cases, but may be allowed when blocking an inappropriate user name to allow creation of a different name.
  • Autoblocking of IP addresses used by the blocked user should typically be enabled for users who were blocked for disruptive behavior. It should be disabled in most other cases, like blocking malfunctioning bots and usernames that don't follow the username policy.
  • Only prevent the blocked user from using their talk page or sending e-mail if they are likely to abuse these privileges.

અવરોધિત કર્યા પછી

  • અવરોધિત સભ્યને સૂચિત કરો, પ્રાધાન્ય રીતે તો કોઈ સભ્ય અવરોધ ઢાંચા વડે.
  • Watch the blocked user's user talk page and ensure that requests for unblock are attended to.
  • Blocks based on disruptive behaviour should be lifted if there is reason to believe that the disruptive behaviour will not resume.
  • Controversial blocks may also be discussed at the blocks and protections noticeboard after they have been applied. To avoid wheel warring, another administrator should lift a block only if there is consensus to do so, even if there is no clear consensus in favor of the original block.

Appealing a block

Blocked users are informed that they may request unblocking. They may do this by adding {{unblock|reason for the request}} to their own user talk page. Alternatively, they may request unblocking with an appropriate reason via e-mail to the blocking administrator or another administrator.

An appropriate reason will almost always include one of the following:

  • An acknowledgement that the block was appropriate and a credible promise that the behaviour that led to the block will not be repeated
  • An explanation of why the block is not appropriate based on this and other relevant policies and guidelines or is likely to be a mistake or an unintended side effect

An unblock request may be granted or declined. Before granting a request to lift a block placed by another administrator, the reviewing administrator should consult with the blocking administrator, except in obvious, uncontroversial cases. Requests made on user talk pages may only be declined by an uninvolved administrator.

Making repeated unblocking requests without appropriate reasons may be considered abusive. As noted above, users who have abused or are likely to abuse the ability to edit their own user talk page and/or send e-mail in this or any other way may have either or both of these privileges revoked, which also prevents these privileges from being used for unblocking requests.

આ પણ જુઓ