Bulbapedia:Dealing with vandalism: Difference between revisions

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search
(link)
Line 15: Line 15:
# Unlocking the database, then reverting the changes as outlined above.
# Unlocking the database, then reverting the changes as outlined above.


At a later stage, once all vandalism has been reverted, the user and their revisions may be completely removed from the database. Please be sure to lock the database and take a before starting.
At a later stage, once all vandalism has been reverted, the user and their revisions may be completely removed from the database. Please be sure to lock the database before starting.


[[Category:Bulbapedia guides|{{PAGENAME}}]]
[[Category:Bulbapedia guides|{{PAGENAME}}]]
[[Category:Bulbapedia administration|{{PAGENAME}}]]
[[Category:Bulbapedia administration|{{PAGENAME}}]]

Revision as of 16:38, 3 January 2008

Regular users

Regular users should immediately report vandalism to an administrator via instant messaging or IRC. Do not use User Talk pages - these will not alert the user until they visit Bulbapedia.

In the meantime, regular users should manually revert any vandalism.

Administrators

Administrators should ban large-scale vandals on sight. To revert changes, go to the user's list of contributions and click the rollback links. When reverting changes, please remember to add &bot=1 to the URL of the list of contributions, for example: http://bulbapedia.bulbagarden.net/w/index.php?title=Special:Contributions&target=Vandal&bot=1 This will hide both the vandalism and the reverts from the recent changes list.

System administrators

Extremely large-scale vandalism involving the use of multiple sockpuppets should be resolved by immediately enacting the following measures:

  1. Blocking all instances of the vandal. Be sure to check the user list for unactivated ones.
  2. Locking the database, preventing all edits and new user registrations.
  3. Altering the MediaWiki configuration to prevent new user registrations.
  4. Unlocking the database, then reverting the changes as outlined above.

At a later stage, once all vandalism has been reverted, the user and their revisions may be completely removed from the database. Please be sure to lock the database before starting.