Cannabis Ruderalis

Blocks exist to protect the project from harm, and reduce likely future problems. Appropriate use of a block can help prevent imminent problematic conduct and disruption to Wikipedia.

When not to block

Do not block someone where you have, or may seem to have, a conflict of interest with regards to the editor in question or the topic in dispute – known as being "involved". This is generally construed very broadly by the community, to include current or past conflicts with an editor (or editors) and disputes on topics, regardless of the nature, age, or outcome of the dispute. However, issuing warnings, calm and reasonable discussion and explanation of those warnings, advice about communal norms, and suggestions on possible wordings and approaches, do not make an administrator 'involved'.

In cases which are straightforward, (e.g. blatant vandalism), the community has historically endorsed the obvious action of any administrator – even if involved – on the basis that any reasonable administrator would have probably come to the same conclusion. When in doubt, however, raise the matter at the relevant noticeboard and let other administrators take action, if appropriate.

Remember that even if you issue a block in a completely uninvolved, nonpartisan manner and perfectly in-line with policy and past precedent, you are stopping another person from being able to contribute to the world's largest encyclopedia project, and they are unlikely to react to the block positively. If you have any doubts - don't block.

Admin mop.PNGWhen to block

Common User block templates
Temporary Indefinite
Vandalism: {{uw-vblock}} {{uw-voablock}}
3RR: {{uw-3block}}
Spamming: {{uw-sblock}} {{Spamblock}}
UserName: {{uw-ublock}}
Legal threats: {{uw-lblock}}
Sockpuppetry: {{uw-spoablock}}
Harassment: {{uw-hblock}}
Generic Block: {{uw-block}} {{uw-blockindef}}

One critical point to remember is that we block users to protect the encyclopedia from harm; blocks should not be punitive. Blocks are most often used for:

Blocking may be used in other situations (not just the above), where particular situations are addressed by more specific policies dealing with particular issues.

Blocks sometimes are used to allow discussions (such as AfD discussions) to proceed without interruption. The block length is usually based on how long you think the block needs to be in place to protect the encyclopedia. 31 hours is the standard duration for most blocks. Edit warring blocks (including WP:3RR) are usually 24 hours (some administrators prefer 31 hours). Registered sockpuppet accounts receive indefinite blocks, however, IP sockpuppet accounts only receive temporary blocks. Discussion blocks might last long enough to conclude the discussion. If you use Twinkle to block, it will automatically supply the standard durations based on the preset chosen.

Blocks are most often used after a user continues to vandalize despite repeated warnings. Such blocks generally are imposed when a user continues to vandalize after a final warning (corresponding to a level 4 warning template) but this is a guideline, not a hard and fast rule. Template warnings are often used but are not required. Single purpose accounts or vandalism-only accounts may warrant blocking with fewer warnings. In cases of gross or extreme vandalism a warning is not needed at all, such as in the case of promotion of hate and racism, or uploading shock images. Some users will deserve only one warning, others more warnings. Decide on the severity of the behavior and the likelihood of salvaging a good user. No hard and fast rule will do; use your good judgment.

Admin mop.PNGWhen to unblock

You must not unblock any user who has been blocked as a CheckUser, Oversight, or Arbitration Committee action, as this can result in the removal of your admin rights, even for a first-time offense.

You may want to consider unblocking a user in a number of circumstances. These can include:

Administrators should not normally unblock users blocked in good faith by another administrator. If you plan on undoing another admin's block, ask them to consider unblocking first. The blocking administrator may have further information and history (e.g.,: action taken at WP:ANI or WP:AE) that is not immediately visible on an unblock request. If that is not possible (e.g.,: if the blocking admin has since retired) and there is good reason to unblock, notify the original blocking admin and consider posting a note at WP:AN to let other administrators review your intended actions. This will prevent wheel warring which would otherwise escalate into a dispute.

If you think the blocking administrator has a conflict of interest, you should still assume good faith that the block is correct, and discuss it at WP:AN.

Admin mop.PNGHow to block

Blocking a user is accomplished by filling out the blocking form. For the purposes of this guide we will use this form provided by the MediaWiki software. However, in practice you may more often use semi-automated tools for blocking such as Twinkle, which can make the process considerably easier, and add an appropriate message to the user's talk page that explains why they have been blocked, and how to appeal.

The blocking form can seem complicated at first with all of its checkboxes and options; however, once you understand what these options do, it is easy to determine which are needed and which aren't. Below is a step by step guide on how to make blocks to different groups of users. Follow the instructions through and then block the users as the guide says.

Yes, it's fine for you to block User:ThisIsaTest, User:192.0.2.16, User:2001:DB8:10:0:0:0:0:1 and User:Keegagan !!

Note: After you are done, please make sure to unblock the users/IPs that you have test-blocked and removed the block messages from their talk page so that these steps may be repeated by the next Admin.

Admin mop.PNGUser blocks/unblocks

User:ThisIsaTest has been causing massive disruption since he created his account 5 minutes ago. He has sequentially received the four warnings {{uw-vandalism1}}, {{uw-vandalism2}}, {{uw-vandalism3}}, and {{uw-vandalism4}} (which is more than adequate warning), yet he still continues his rampage. With his continued rampage after adequate warning, he needs to be blocked to stop any further disruption.

Typical Admin blocking form
  1. View ThisIsaTest's talk page, verify that they have been adequately warned and that the warnings are recent.
  2. Click on ThisIsaTest's contributions.
  3. Verify that ThisIsaTest has continued to vandalize after being adequately warned.
  4. Directly under the title you should see "talk|block|block log|uploads" among other links – click on block. This will bring you to ThisIsaTest's blocking form. (see diagram on the right)
  5. Scroll to the bottom of the blocking form page, you will see the blocking form that is to be filled in. The username of the user to be blocked should already be there.
  6. Click on the Expiry: drop down menu – as ThisIsaTest is a vandalism-only account, select indefinite. ( A )
    • directly underneath this drop down menu ( B ), you can specify your own length of block. You can type in just about anything here e.g. 1 week, 2 months, 71 hours etc., or enter a specific end date (useful if modifying an existing block) – use either the drop down menu, or type your own length in, not both.
  7. Click on the Reason: drop down menu ( C ) – select Vandalism only account (you may use the other reasons in different situations as well as enter a custom reason in the D field).
  8. You then come to several check boxes: ( E )
    • Block account creation stops the user from creating a new account for 24 hours after the block is made – this typically should be left ticked.
    • Block user from sending e-mail prevents the user from sending email – this should be left un-ticked unless the blocked user abuses the email function.
    • Prevent this user from editing their own talk page while blocked self-explanatory – this should be left unticked unless the blocked user disruptively edits their talk page or posts unblock abuse.
    • Autoblock any IP addresses used blocks all IP addresses the editor may use in the future whilst blocked. Autoblocks last for 24 hours, except in the case of dynamic IP pools such as those used by residential ISPs – this typically should be left ticked.
    • Watch this user's user and talk pages adds the blocked user's page to your watchlist – you may wish to tick this checkbox to be informed if the user adds an unblock rationale on their talk page.
  9. Now click Block.
  10. Leave {{subst:uw-voablock}} on ThisIsaTest's talk page to explain that he has been indefinitely blocked.

User:ThisIsaTest's block settings may need to be changed.

  1. Once again go to ThisIsaTest's contributions – click on block. This will bring you to the block form again.
  2. You will see a message at the top that says: "ThisIsaTest is already blocked. Do you want to change the settings?" – enter the new settings in the fields below.
  3. Now click Re-block the user with these settings.
  4. Leave a message on ThisIsaTest's talk page explaining that the block settings have been changed.

User:ThisIsaTest now says he is sorry – no, he says he is really sorry and has waited six months (per the standard offer) and you wish to unblock him:

  1. Click on ThisIsaTest's contributions.
  2. Directly underneath the title you should see "talk|change block|unblock|block log" (among other links) – click on unblock. This will bring you to the unblock form for ThisIsaTest.
  3. Under the reason field, give the reason you are unblocking User:ThisIsaTest.
  4. Click Unblock. You then see the message "You have unblocked ThisIsaTest".

For the purpose of these practice steps, please remove the {{subst:uw-voablock}} post from ThisIsaTest's talk page.

Admin mop.PNGIP blocks/unblocks

User:192.0.2.16 has been causing massive disruption today and has received warnings from {{uw-vandalism1}} to {{uw-vandalism4}}, yet she still continues her rampage. The IP needs to be blocked to stop any further disruption.

  1. Click on 192.0.2.16's contributions.
  2. Directly underneath the title you should see "talk|block|block log|uploads" among other links – click on block. This will bring you to 192.0.2.16's blocking form.
    If you block any IP in the ranges listed under "Sensitive IP addresses", you must notify the Wikimedia Foundation Communications Committee immediately (see contact instructions there or use the notifications page).
  3. Scroll to the bottom of the page, you will see the blocking form that is to be filled in. The IP of the user to be blocked should already be there.
  4. Click on the Expiry: drop down menu – as 192.0.2.16 has received no previous blocks, select a short amount of time: 31 hours.
    • directly underneath this drop down menu, you can specify your own length of block. You can type in just about anything here e.g. 1 week, 2 months, 71 hours etc. – use either the drop down menu, or type your own length in, not both.
  5. Click on the Reason: drop down menu – select Vandalism.
  6. You then come to several check boxes:
    • Block account creation stops users from this IP creating an account – this should be left ticked.
    • Block user from sending e-mail prevents users from this IP from sending email – this should be left unticked unless the user is abusing this function.
    • Prevent this user from editing their own talk page while blocked self-explanatory – this should be left unticked unless the blocked user disruptively edits their talk page or posts unblock abuse.
    • Watch this user's user and talk pages adds the blocked user's page to your watchlist – you may wish to tick this checkbox to be informed if the user adds an unblock rationale on their talk page.
    • Prevent logged-in users from editing from this IP address blocks all users, registered and unregistered, from editing from the IP address. This may cause collateral damage so should be left unticked.
  7. Now click Block.
  8. Leave {{subst:uw-ablock}} on the IP's talk page to explain that it has been blocked for a short period of time.

User:192.0.2.16 now says she is sorry and you wish to unblock her:

  1. Click on 192.0.2.16's contributions.
  2. Directly underneath the title you should see "talk|block|block log|uploads" (among other links) – click on unblock. This will bring you to the unblock form for 192.0.2.16.
  3. Under the reason field, give the reason you are unblocking 192.0.2.16.
  4. Click Unblock. You will then see "You have unblocked 192.0.2.16".

For the purpose of these practice steps, please remove the {{subst:uw-ablock}} from 192.0.2.16's talk page.

Admin mop.PNGBlocking a range of IPs

Sometimes disruption persists from a small range of IPs, where blocking each individually is ineffective. In such cases it may be feasible to perform a range block. This however should be avoided if at all possible, as it will cause collateral damage. It is suggested you discuss range blocks before making them, and if you aren't familiar with the Internet protocol suite and CIDR ranges, you shouldn't be making them.

Things to do before considering a range block:

  • Ensure page protection is not a viable alternative, for instance, if only one or two pages are affected.
  • Check the contributions from the range and ensure there are not good-faith editors that will be blocked from editing.

Tools for computing the range of IPs:

Tools to check range contributions:

  • Range calc gadget (recommended). Go to your gadgets and enable "Allow /16, /24 and /27 – /32 CIDR ranges on Special:Contributions". From here you can go to Special:Contribs and enter the CIDR range in just as you would any user or IP. If you have WP:POPUPS turned on, you can hover over the "diff" links to verify you won't be blocking any constructive users
  • xtools
  • HelloAnnyong's rangecontrib tool

Blocking ranges works much the same way as you would block any IP, except you provide the CIDR range. If you feel a range block is warranted but are uncomfortable doing it yourself, you may wish to contact one of the admins in Category:Wikipedia administrators willing to make range blocks.

Admin mop.PNGUsername blocks/unblocks

User:Keegagan is an inappropriate username due to it being too similar to an existing user. Assume that this is a clearly inappropriate username of the kind that can be blocked on sight by any administrator. To block,

  1. Click on Keegagan's contributions.
  2. Directly underneath the title you should see "talk|block|block log|uploads" among other links – click on block. This will bring you to Keegagan's blocking form.
  3. Scroll to the bottom of the page, you will see the blocking form that is to be filled in. The username of the user to be blocked should already be there.
  4. Click on the Expiry: drop down menu – as Keegagan's username is inappropriate, select indefinite.
    • directly underneath this drop down menu, you can specify your own length of block. You can type in just about anything here e.g. 1 week, 2 months, 71 hours etc. – use either the drop down menu, or type your own length in, not both.
  5. Click on the Reason: drop down menu – select {{uw-uhblock}}
  6. You then come to several check boxes:
    • Block account creation stops the user from creating a new account for 24 hours after the block is made – this tick should be changed to unticked.
    • Block user from sending e-mail prevents the user from sending email – this should be left unticked.
    • Prevent this user from editing their own talk page while blocked self-explanatory – this should be left unticked.
    • Autoblock any IP addresses used blocks all IP addresses the editor may use in the future whilst blocked – this should be changed to unticked.
    • Watch this user's user and talk pages adds the blocked user's page to your watchlist.
  7. Now click Block.
  8. Leave {{subst:uw-uhblock-double}} on Keegagan's talk page to explain that he has been indefinitely blocked.

User:Keegagan now says Keegagan is a family name and you wish to unblock him:

Typical Admin Un-block form
  1. Click on Keegagan's contributions.
  2. Directly underneath the title you should see "talk|change block|unblock|block log" (among other links) – click on block. This will bring you to the unblock form for Keegagan.
  3. Under the reason field, give the reason you are unblocking Keegagan.
  4. Click Unblock You then see the message "You have unblocked Keegagan".

For the purpose of these practice steps, please remove the {{subst:uw-uhblock-double}} post from Keegagan's talk page.

Admin mop.PNGPartial blocks

Partial blocks can prevent a user from:

  • Editing specific pages or all pages within a specific namespace.
  • Emailing other users or creating other accounts, while still being allowed to edit normally

To partially block a user, the following additional fields are used on the blocking form:

  • To allow the user to continue to edit pages normally while blocking other actions:
    1. Uncheck the Editing checkbox.
    2. Check the other actions to block where appropriate.
  • To prevent the user from editing specific pages or within a namespace:
    1. Select the Partial radio button below the Editing checkbox.
    2. Enter the specific pages in the Pages box.
    3. Enter the specific namespaces in the Namespaces box.

Tools

Executing blocks

  • Twinkle – A comprehensive block+template tool. Allows you to choose a preset that auto-supplies the standard block duration, block summary, and template to issue to the user. You will see different presets and options when blocking IPs versus accounts. You can also use this gadget just to template the user and not block, and vice versa. If the user has been blocked in the past, a link to the block log will be shown. Also automatically disables a hard block when blocking bots.
  • EasyBlock – Block+template script with numerous options on types of blocks. This is quicker than Twinkle but does not allow you to choose block options. Many admins use both scripts.
  • massblock – Block multiple users at once. Use with caution!
  • Note you can also block while patrolling recent changes with Huggle

WHOIS

  • Domaintools – Probably the most comprehensive of the WHOIS tools, however requires you enter a CAPTCHA and has a limit of about 50 lookups a day. Be sure to check not just the ASN but the network name, etc, when attempting to determine if an IP belongs to a school or is otherwise shared.
  • Whois Gateway on labs – free, CAPTCHA-less and limitless WHOIS lookups for IPs. May not show the network name in some situations.
  • Betacommand's WHOIS tool – returns the ASN and CIDR range for an IP, checks for global blocks and returns the block log. To use, append the IP to the URL like ?ip=1.2.3.4
  • For an up-to-date list of the most commons tools used when checking IPs, refer to {{anontools}}, passing it an IPv6 address if needed.

Range blocks

General information

Calculating a range

Checking range contributions

Range contributions are now supported in MediaWiki core. Simply enter the range at Special:Contributions.

You can also do a wildcard search (e.g. 83.217.178.*) using the Contribsrange gadget gadget. Enable "Allow /16, /24 and /27 – /32 CIDR ranges" at Special:Preferences#mw-prefsection-gadgets under "Advanced". Then type in any CIDR range into Special:Contribs.

See also

Leave a Reply
https://thcscience.wiki/term/cannabaceae/cannabis/cannabis-ruderalis/?rdp_we_resource=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FWikipedia%3AAdministrators%2527_guide%2FBlocking
thcscience.wiki
crawl=CC-MAIN-2022-49
164165
application/http; msgtype=response
sha1:KE2WBP5LLPNTSJABRMHAGUHJC6J6IWY2
<urn:uuid:e292ddcc-154f-4240-960a-8ebc6aa69512>
2022-12-01T02:37:56Z
208.113.215.32
text/html
sha1:3DA6NUYV7JNRPHYJY44T3UAJTCV6WSPL
<urn:uuid:b7d3b778-22bf-40f8-ba6d-76a8e22fe0d1>
https://thcscience.wiki/term/cannabaceae/cannabis/cannabis-ruderalis/?rdp_we_resource=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FWikipedia%3AAdministrators%2527_guide%2FBlocking
response
<urn:uuid:61dd2237-2f95-4693-a122-545fdf5855a2>
isPartOf: CC-MAIN-2022-49
publisher: Common Crawl
description: Wide crawl of the web for November/December 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-199
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/