Conservapedia:Administrator's Guide

From Conservapedia
Jump to: navigation, search

If you are reading this for the first time, congratulations! You have joined a group of editors here to protect Conservapedia, and act as "stewards" of the project. Below are some guides that will make you more effective and a better example to editors in your job as a Sysop:

Terms explained
  • Administrators, also known as sysops, are editors with the ability and authority to enforce Conservapedia's rules and resolve disputes.
  • Bureaucrats are Administrators with the additional ability to change user rights.

Working with others

Some new users might simply misunderstand our policies and need some guidance. Not all initial efforts which violate policy are done out of opposition or indifference to project goals.

A sysops' responsibility is to help users by providing guidance. If a user seems stubborn or indifferent, try shepherding or mentoring the user. The relationship between Sysop and Editor should not be adversarial. Do not compound the problem by being argumentative. You should interact peacefully and positively with users, direct newbies to the appropriate Guideline page or clause that deals with certain problems, and issue polite warnings as required. If necessary, you may impose editing restrictions, undo useless work, userfy inadequate articles, or try short blocks.


Conservapedia Administrators are expected to afford registered users the same standard of editing etiquette, decorum, and interaction you yourself, and the Conservapedia project as a whole, require and appreciate from others. You must be civil. No bullying. Violators of the CP Guidelines may face sanctions.

There is a difference between intelligent discourse, and attacking or being attacked for what someone may believe. Wikipedia condones bullying and mob rule, Conservapedia does not.

Incivility and personal attacks should be replaced with the {{personal remark removed}} template. As a last resort, and in the most extreme circumstances, the sysop or blocking editor may have to resort to a block.

The {{hide collapse}} template could be used when a posting derails, either purposely or unwittingly, the original topic thread. However, the template needs to be used with caution and not simply as a means to silence critics. Ideally, the original creator of the topic thread would use the template if they feel a poster is attempting to derail the topic with excess, superfluous information, or off-topic derailment.


In dealing with vandalism, Page Protect after Reversion should be the first method. It is important to create a Log of attacks for other Admin to see. Duration of the Protect should be at least 1 Hour, and possibly as long as 6 Months after a repeated pattern of attacks on a particular article Mainspace has been established. Some High traffic pages need longer protection, but those are rare exceptions. Blocking a new user should not be the first immediate, impulsive reaction, unless profanity or other serious violations occur. Some newbies need time to learn the rules, guidance, encouragement, and interaction from other users to become good productive editors.

The vandals are showing you their interests, or what is stuck in their craw, so take advantage of their lapse in judgement to force them to ask permission to make changes. Experience shows that immediately resorting to Blocking does not, and cannot, stop a determined vandal. Use their weakness and revelations of personal bias to lead you to what Mainspaces need Page Protect, and frustrate their ambitions. Immediate resort to Blocking only serves to multiply, exponentially, the use of sockpuppets by enemies of the site.

Remember, Vandal patrol is not simply a game of whack-a-mole or Space Invaders where you get to zap your opponents. It entails defending the wiki while not doing harm to growing our userbase.


See also: Conservapedia:Blocking policy
  1. If you have determined a user should be blocked, there are multiple more factors to consider:
    1. Should the user be blocked for a reason not based on the quality of his edits or legitimacy? (For example, a vulgar username.) Then make sure the checkbox titled: "Automatically block the last IP address used by this user..." is unchecked (it is checked by default) so that the user can create a new account.
    2. If the user should be blocked based on his actions on the wiki, carefully consider how long the user should be blocked. If the user is a blatant vandal, generally 6 month blocks are handed out. If the user is merely edit warring or some similar offense, a shorter block (2 days, a few weeks, months?) is more appropriate after warnings are given out. Keep in mind that users and IP addresses can change - long term and infinite blocks are therefore discouraged.
  2. If you have run checkuser (which you should generally only do with probable cause) and determined the user has created sock-puppet accounts, the user should be blocked. Be wary that multiple distinct users might just be editing from a public location - for example a school, a coffee house or a library.
  3. Furthermore, users with blocking rights must be very careful in the issuance of a block. Unwarranted blocks that may be undone clog the block log, and future Administrators may unfairly consider an established user as a troublemaker, when the real problem lies with an unjustifiable block made by an Administrator. When a blocking error occurs, it's best for everyone involved for the original blocking editor to undo the action so as to limit confusion. However, this is not always possible. Use the Edit summary to create a permanent record for blocking justification.
  4. The primary purpose of the blocking tool is aimed at behavior modification, not vengeance.

Guideline concerning avoiding unwarranted blocks

Editor retention is important for wikis. Therefore, unwarranted blocks are to be avoided and the benefit of the doubt should be given to editors so editors are not blocked due to good faith mistakes and/or mistakes due to ignorance of wiki policies.

For example, many new wiki editors are not aware that they cannot copy and paste a material from other wikis or other websites without giving attribution (quoting material). If a new editor were to do such a thing, he should be cordially warned and not blocked. Work with the editor, and avoid creating an intimidating or hostile environment.

Editors should be blocked for actual behaviors and not merely suspicions.


Sysops should be careful not to delete other sysops talk page comments, including on their user pages.


  1. To move a page, click the "move" tab on the upper pane. It should be directly to the right of the "delete" tab. Once you have clicked this button, you will see a page which enables you to move the content of one page to a page with a different title. Simply type the new title of the page in to the box entitled "To new title:", and give a short reason in the "Reason:" box. By default, the "move associated talk page" checkbox should be marked; this should always be marked. It's up to you whether or not you want to "watch" the page (this places it on your watchlist).
  2. If a page already exists with the new name, you will be warned and asked if you want to delete that page. It is recommended that you answer "no" to this, and delete the page manually. The reason for this is that if you allow the software to delete the page, it will not delete the accompanying talk page, which means that the talk page of the article you are moving will not itself be moved. If you already know that there is no accompanying talk page, then answering "yes" will work.


Please check the upload log frequently to protect any new images. This will in turn prevent any image vandalism.

(Images are usually not on anyone's watchlist except that of the person who uploaded them, and cannot be reverted if someone replaces the image. This makes protecting images more important than protecting articles or templates, both of which are more easily reverted and/or more likely noticed.)


Checkuser can trace the originating IP or proxy of vandals and sockpuppets. If the IP address check shows that the IP is being used by two usernames the person is likely a sockpuppet who is using the same computer connection to edit Conservapedia. The user will be blocked and if a mistake was made the error can be easily undone. Be sure to always act in good faith and not bite the newbies.


Some administrators are granted the additional ability to lock and unlock the database (locking prevents all editing). This is known as siteadmin rights.

Siteadmins are listed here.


Oversighters have the ability to permanently remove revisions from view. This is used to hide personally identifiable information that was posted inappropriately. Oversight can also be used to hide particularly harsh libel or personal attacks, or inappropriate language, such as obsenity. Oversight is a maintenance tool to protect privacy and Conservapedia's family friendly atmosphere, not a weapon to stifle criticism and active discussion.

Wheel warring

Avoid wheel warring. Calm down. Discuss. Make sure any sysop action is justifiable under Conservapedia Commandments and Guidelines.

Keeping informed of new developments

An area of Conservapedia has been created for discussion of concerns within the Conservapedia community so Sysops can be informed of various developments. The area is located here: Conservapedia:Community Portal.

See also