| I thought this|
was supposed to be
In general, RationalWiki discourages blocking, especially for extended periods of time.
Blocking should never occur if somebody is attempting to discuss an issue in a reasonable manner. Blocking is not to censor alternate opinions, but to prevent disorder.
Blocking should only be used if somebody is maliciously editing a page or pages, as explained below.
RationalWiki has a special "vandal bin" feature, which restricts its members edits to 1 edit per 30 minutes, making spamming and vandalism significantly less rewarding. If somebody is persistent, but not clearly a vandal, it may be useful to restrict their edit rate, but not block them.
 Malicious editing
Malicious editing occurs when somebody wants to harm RationalWiki. Because it does not contribute to constructive dialogue, and merely causes disorder, malicious editing is a blockable offense.
Blockable malicious editing is the performance of any of the below:
 Short-term blocks
- Ban evasion: Avoiding bans imposed for other reasons.
- Blanking a page: Removing all or a significant portion of a page. Signified by "Blanked the page" messages in the edit summary.
- Edit warring: Reverting the non-obviously-malicious edits of others without explanation or discussion on the talk page.
- Creating an account with a name that impersonates another user's, is offensive, or is ridiculously long.
- Interfering with other users' talk page comments or votes.
- Unfunny vandalism: Adding stupid, boring, angry shite to a page; we'd be more inclined to treat you nicely if, after insulting RationalWiki and everything it stands for, you gave a little praise to the Sky Goat.
- It should be noted that adding what seems like gibberish or irrelevant information is not necessarily malicious; assume good faith. If it seems crazy, just copy it over to the talk page and ask the person to justify their addition.
A fairly short block (hours to days), or a visit to the vandal bin, is preferred.
 Long-term blocks
- Doxing: Adding personal information about others into a page. This also includes soliciting for such information off of RationalWiki.
- Legal threats: Raising legal threats against RationalWiki, the RationalMedia Foundation, or any RationalWiki editors. If you have a concern with some content about you, argue why it should be changed. Going around slapping people with lawsuit threats is not conducive to constructive debate.
- Harassment: Adding purely offensive material, solely for the purpose of causing emotional harm, into a page.
- Spam: Adding advertising, especially media of or links to illegal or obscene items, into a page. Or, adding huge chunks of text to a page. Or, adding something to many pages.
 Blocking tools
In order to block a user, one must do one of the following:
- Go directly to Special:Block and enter the user's username
- If in an edit history, every edit includes the user's username, followed by "(Talk | contribs | block)". Click "block" and it takes you to the block page.
- If in a user's contributions, at the top of the page is a big ol' list of that user's pages. Click the "block" one and it takes you to the block page.
When sysops block users, they see five checkboxes:
- Prevent account creation: If checked, this prevents users or IPs from creating new accounts, which might allow them to avoid the block. This checkbox should almost always be checked.
- Prevent this user from editing their own talk page while blocked: Usually, blocked users will be able to edit their own userpage and talkpage. This checkbox should almost never be checked, because blocked users should always be allowed to protest their block. The only exception is if the blocked user decides to spam their userpage, in which case this box may be checked and the block extended.
- Automatically block the last IP address used by this user, and any subsequent IP addresses they try to edit from: If checked, this prevents the user from editing from their previous IP address, and any other address, if they log in first. This checkbox has almost no impact, and so it doesn't matter if it's checked or not.
- Watch this user's user and talk pages: This checkbox adds the user's userpage and talkpage to your Watchlist, which makes it easier to patrol them, if they decide to spam more or apologize.
- Prevent logged-in users from editing from this IP address: Usually, if an IP is blocked, a person can log in and avoid the IP block. This checkbox should almost never be checked, as the block itself should do enough damage and an IP block may hurt innocent users.
Sysops should almost always avoid blocking for long periods of time, such as year-long or infinite blocks. It is highly unlikely that a block of more than a few days will ever be needed, because most vandals get bored after waiting for a few days and forget about RationalWiki.
When a sysop is in the blocking window, a sysop can see the block history of the person being blocked. If somebody is a repeat offender, then the duration of the block can acceptably be increased.
Non-obscene human vandals can be blocked for up to 1 day, depending on how annoying their edits are.
Obscene human vandals can be blocked for up to 1 month, depending on how hateful/illegal/disgusting their edits are.
Spambots can be blocked for up to 3 months, but sysops should only block if there is repeated spamming from an IP address.
Repetitive malicious editors can have their blocks extended for up to 3 months.
For any longer block, please get community consensus at the Chicken coop.
RationalWiki has a special feature called the vandal bin. Sysops and bureaucrats can put vandals into a special list which limits them to 1 edit per 30 minutes. Users in the vandal bin also lose the ability to relocate pages. This allows RationalWiki to restrict the abilities of vandals, while still allowing them the opportunity to edit the wiki, and contribute if they have a change of heart. The vandal bin works very well to make malicious editors get bored and go away.
Vandal binning IP addresses and using the autoblock feature is discouraged, because those IPs will remain in the bin forever (until somebody notices and takes them out), and this may affect innocent users in the future. Using short blocks for IPs is preferred.
 Hiding revisions
We have the ability to "hide" individual revisions from public view without having to delete the entire page history. It is only used whenever someone posts personal information (e.g. street address, phone number, real name, place of work, etc.) without the subject's permission. These changes to revisions are logged in the.
When you look at a page's edit history, next to each revision you will see a checkbox, and in the header and footer you will see a button labeled "Show/hide selected revisions". You will also see a (show/hide) button in various places, for example when viewing diffs. Clicking these buttons brings you to a screen containing a list of options for hiding the revision(s) from public view:
- Hide revision text — Checking this hides whatever changes were made.
- Hide edit comment — Obviously, checking this hides whatever the edit summary was. Only use this if the edit summary also contains inappropriate information.
- Hide editor's username/IP — Checking this hides the username or IP address of the person who made the edit. This is usually not necessary, and will hide the edit from the user's contributions page.
Also make sure to say why you are hiding the revision in the "Log comment" box, such as "Removing post containing personal information (i.e. phone number, address, real name, etc.)".
If the revision needs to be hidden from other sysops, e.g. because it contains personal information, please contact a moderator.
If you must practice using this ability, practice only on your own userpage, or a sandbox in your userspace.
 Cleaning up afterwards
After sysops block a user, it's standard practice to go to the user's contributions page and review each of their recent edits, in order to revert other malicious edits that the user may have performed. This ultimately matters more than blocking or vandalbinning, since it preserves the missions of RationalWiki, while blocking or vandalbinning merely prevents or slows future disorder.
If a page is repeatedly vandalized, it may be necessary to protect it.
 How NOT to block
Sysops should exercise caution when issuing blocks or vandalbinning. It is important that sysops avoid mistakenly blocking innocent non-malicious editors, particularly if they're newcomers. Sysops should assume good faith, and if and when that faith is betrayed, not panic. A few edits by vandals does not a crisis make. Sysops should wait until a new editor makes an edit or two. If the edits are clearly vandalism, then punish them. If the edits are questionably vandalism, sysops should ask them about it on their talk page before assuming vandalism.
If possible, sysops should attempt to engage the malicious editor, not block them. Obviously someone editing random pages to insert gibberish or blank them is not going to respond to kindness, but if an editor seems to be trying to say something, it is good to try get them to go to the talk pages.
RationalWiki does not block merely for associating with sites we disagree with. RationalWiki also does not block for off-wiki actions, such as a block on Wikipedia. So long as they don't vandalize the pages, you shouldn't stop them; rather, encourage them to have constructive discourse.
 Joke blocks
Some naughty sysops issue "joke blocks" on their fellow sysops, lasting a few seconds to a couple minutes in length (although overuse of minute-plus blocks, or blocks against sysops in the middle of editing, are never appreciated by the blockee, and are rather frowned upon). Furthermore, when giving out a friendly block, sysops should uncheck Automatically block the last IP address used by this user, and any subsequent IPs they try to edit from.
Also, users may request that their IP address be blocked to force them to log in, or simply block it themselves.
 See also
- RationalWiki:Chicken coop
- RationalWiki:Community Standards
- RationalWiki:Sysop guide
- RationalWiki:All things in moderation
- Help:How to handle vandalism