From Miraheze Meta, Miraheze's central coordination wiki

Automatic archival service is provided by revi via Revibot. Currently, this is done only for Miraheze Meta, but if you want to use this on your wiki, contact revi. Note that your talk page must have the same structure as it is on this wiki. This means Structured Discussions (also known as Flow), and other discussion threading software are not supported.

Constraints[edit | edit source]

  1. Make sure your archiving page is a subpage of the original page, or it will not work unless bot owner's approval. For the approval, please contact revi.
  2. The Bot only archives texts below h2 level section (==Your topic==) and nothing above it. There is currently no way to change this value.
  3. The Bot does not care whether your topic is very important that deserves longer visibility. It only cares about the date of the last comment. If you want to prevent the bot from archiving your important comment, put the following snippet to the section: <!--23:59, 31 December 2099 (UTC)--> Removing this will trigger archive as defined by the template.
  4. The Bot only recognizes standard signature time, like 10:10, 5 March 2018 (UTC). Timestamps that do not follow this format are ignored, this means your comment will not be considered when the bot checks if the section will be archived, and nobody will get an exception. Use the standard timestamp format. You will get this if you just use ~~~~~.
  5. By default, the bot will skip your talk page if it has less than 5 topics after archiving them. You can override this by using |minthreadsleft=(your value).
  6. By default, the bot will skip your talk page if it has less than 2 topics to archive. You can override this by using |minthreadstoarchive=(your value).
  7. If you need to unarchive it, unless archival is done in error, revi suggests that you open a new, fresh section with the old discussion link because the fact that it is archived means it was archived because did not attract interest.
  8. The Bot cannot edit pages protected as "Allow only logged in users". Either do not protect with such protection level, or disable the bot. revi currently has no interest in fixing the bot to support user protection level.

See {{Autoarchive/config}} for setup.