WikiQueer:Twinkle/doc

Once Twinkle is installed, you will be presented with a number of additional tabs or links, depending on the page you are on.

Installation
Installing Twinkle is easy. Refer to the "quick info" section of the script's page for easy-to-follow instructions. Before you start using Twinkle, you really should read this page to familiarize yourself with some of the possibilities and functions of Twinkle. There are multitudes of options that you can configure to change some of the default behaviours of Twinkle.

Note: Never forget that you take full responsibility for any action performed using Twinkle. You must understand WikiQueer policies and use this tool within these policies, or risk being blocked.

Troubleshooting installation
There are a number of reasons Twinkle installation may fail completely:
 * You must be registered, and your account must be autoconfirmed (it must be at least four days old and have at least ten edits), to use Twinkle.
 * You must use a supported web browser. Twinkle does not work with Internet Explorer version 8 or older; hence, it will not work on Internet Explorer on Windows XP, and you may need to upgrade to Internet Explorer 9 if you use Windows Vista or Windows 7.
 * If you are using older versions of Opera, Safari, or Firefox, try enabling the JavaScript Standard Library gadget under your preferences → Gadgets → Library and compatibility gadgets.
 * After installation, you may have to clear your browser cache. Instructions on how to do this can be found at WikiQueer:Bypass your cache.
 * In case of manual installation, Twinkle must be installed in your skin's .js file (not .css'').
 * If you have switched skins and are not using the Gadget version of Twinkle, make sure that your current skin's script file is actually importing Twinkle.

If you have tried all of the above suggestions and you still cannot use Twinkle, or if you notice other problems, check the discussion page and, if needed, post the issue there. If you do, please include the following information: You are strongly urged to have a look at http://www.chiark.greenend.org.uk/~sgtatham/bugs.html for hints how to report bugs effectively, to make sure the issue you are describing can be resolved as promptly as possible.
 * 1) What is the behaviour you're seeing?
 * 2) What is the behaviour you're expecting to see?
 * 3) How can the incorrect behaviour be reproduced? Describe exactly what you're doing and seeing.
 * 4) Confirm that you have tried bypassing your browser cache.
 * 5) Make note of your browser, browser version, operating system, and operating system version.
 * 6) Append relevant JavaScript errors your browser logged. To do that, open your JavaScript console or error console, and copy the relevant error messages. Where you find your javascript console depends on your browser:
 * 7) * Internet Explorer: Press F12; refresh the WikiQueer page; JavaScript errors appear on the "Console" tab of the F12 tools.
 * 8) * Firefox: Menu → Tools → Error console (or Firefox Button → Web Developer → Error Console). You should click the "Errors" button at the top, in order to hide the vast number of ignorable warnings, etc.
 * 9) * Opera: Menu → Page → Developer Tools → Error Console.
 * 10) * Chrome: Page menu → Developer → JavaScript Console (Ctrl+Shift+J).
 * 11) * Safari: Page menu → Develop → Show Error Console (Ctrl+Alt+C or Shift+Command+J). You might have to enable it first in Preferences → Advanced.

Installing individual Twinkle modules
Previously, it was possible to install Twinkle modules individually. This method of installation no longer applies. Including an individual module will load the entire set of Twinkle modules. The recommended ways to install Twinkle are described at WQ:TW.

Modules
Twinkle is made up of many "modules", each providing a quicker way of carrying out a certain maintenance task. Most modules can be accessed by the tabs along the top of each page (in the Monobook skin), or under the "TW" drop-down menu next to the search box (in the Vector skin).

CSD (speedy deletion)
CSD stands for Criteria for Speedy Deletion. If you believe an article meets a criterion for criteria for speedy deletion, you can use this Twinkle module to quickly tag it for deletion.

Using this module
Click on the CSD tab. You will be presented with a list of reasons, which differ depending on which namespace the page you are viewing is in. When you select one of the items, Twinkle will begin acting right away: you may be prompted for extra information (such as a rationale, URL of copyvio, etc.), and then the page will be tagged with the appropriate template (for instance, clicking "G5: Banned user" tags the page with db-banned).


 * If you have the Notify if possible box checked, and your Twinkle preferences are set appropriately, the user who created the page will be notified using a boilerplate warning template, as requested by speedy deletion policy. If the creator's talk page does not exist, they will also be welcomed, using the firstarticle template. Normally, there is no reason to un-check the "notify" box; however, consider that the notification may not always be appropriate (such as when dealing with outdated technical pages like "meta-templates": see WQ:DTTR), so use it with care.
 * The Tag with multiple criteria option at the top of the window opens a series of further windows, where you will be able to choose several criteria to be included in the db-multiple template. The list of criteria is somewhat smaller than that for non-multiple CSD – each code appears only once, due to the way is implemented. Once you have chosen all the criteria that apply, click the "No more criteria apply - finish tagging" button at the top. No more than ten criteria may be selected for multiple tagging, but it is rare to apply more than two at a time.
 * In your Twinkle preferences, you can turn on the CSD userspace log. This feature keeps a log in your userspace of all pages you nominate for CSD. Because pages that are deleted do not appear in your contributions, using this feature is the only way non-admins can track their deletion taggings and evaluate how many were deleted. It is also useful for tracking declined speedy deletions (by the presence of blue links in the log, as opposed to red links) and learning from them, hence helping you to improve your tagging habits.
 * Nominating a page for CSD will add the page to your watchlist by default, for most criteria. You can disable this, or choose a different set of criteria, in your Twinkle preferences. Additionally, when using CSD on a page reached from Special:NewPages, Twinkle will automatically mark the page as patrolled. Again, you can disable this using preferences.

Take note

 * Twinkle CSD offers a quick easy way to tag pages for speedy deletion. However, always keep in mind that you are responsible for all actions taken using Twinkle, so always think twice before tagging a borderline case with a CSD tag. Also, remember not to bite the newbies.
 * Twinkle does not notify page creators when tagging with certain criteria (including G6 and G8). This is to prevent notifications in cases where they are not really needed, or where they will possibly be counterproductive (such as for CSD G5 - banned user). You can enable notifications for these criteria in your Twinkle preferences, if you especially want them: but note that warning templates for some criteria do not actually exist.

Extra functionality for administrators
Admins can delete pages (and optionally the associated talk page and/or all redirects), and unlink some or all backlinks to the deleted page. The deletion reason can be changed before deletion takes place.

RPP/PP (page protection)
Request for Page Protection - Sends a request for protection to the page of the same name. Used for heavily vandalized articles or for articles that are current and likely will have traffic due to a real-life occurrence.

PROD (proposed deletion)
PROD is short for Proposed Deletion, a process whereby articles that are deemed to be uncontroversial targets for deletion can be deleted if there is no objection within seven days. Twinkle allows you to quickly apply PROD tags.

A similar process, proposed deletion of biographies of living people, can be used on BLP articles that are completely unsourced. The article will then be deleted after ten days, unless at least one source (reliable or not) is introduced to the article. You can also use Twinkle to tag articles for BLP PROD.

(A third kind of proposed deletion, book PROD, is not supported by Twinkle.)

The PROD tab only appears on articles, as they are the only pages eligible for the PROD and BLP PROD deletion processes.

Using this module
Click on the PROD tab on the article page. You will be prompted firstly to choose a PROD type (regular PROD or BLP PROD - see above). If you select regular PROD, you will need to enter a reason explaining why the article may be eligible for deletion. BLP PROD nominations do not require a reason.
 * If you have the Notify if possible box checked, the user who created the page will be notified by substituting the prodwarning template on their talk page. (For BLP PROD, it is not possible to turn off the notification, and the prodwarningBLP template is used instead.) Please note that, at present, Twinkle does not give the creator a welcome message, even if their talk page does not exist.
 * When you tag an article that already contains a PROD tag, Twinkle will ask whether you would like to endorse the existing PROD, using the prod-2 template. If an article contains a regular PROD tag, and you choose to apply a BLP PROD tag in Twinkle, the prod-2 tag is applied with the reason "unsourced BLP".
 * In your Twinkle preferences, you can turn on the PROD userspace log. This feature keeps a log in your userspace of all pages you tag for PROD and BLP PROD. Because pages that are deleted do not appear in your contributions, using this feature is the only way non-admins can track their PROD taggings and evaluate how many are deleted or declined.
 * By default, tagging for PROD or BLP PROD will add the page to your watchlist. You can disable this in your Twinkle preferences.

Take note
Proposed deletion tags are only for uncontroversial deletions. If the deletion may be controversial, consider using Twinkle's XfD module instead. On the other hand, if the page falls under one of the speedy deletion criteria, you should instead use the CSD module, to ensure more rapid page deletion.

Extra functionality for administrators
Administrators have additional access to Twinkle's de-PROD tool, which automatically clears a PROD category. As with all of Twinkle's batch deletion tools, it is rather flaky, and may require several runs to completely clear the category.

XfD (deletion discussions)
XfD is short for Anything for Deletion (where the word "anything" is replaced by the algebraic unknown, x). More specifically, XfD is a collective term for the different venues that exist to discuss the deletion of pages on WikiQueer. You can use Twinkle to quickly start deletion discussions for all pages (except stub templates and stub categories).

See WQ:XFD for help on choosing an appropriate discussion venue. (Note that you cannot presently use Twinkle to create discussions at stub types for deletion; you can make nominations manually at the SfD page.)

Upon running the XfD tool, the page is tagged with a deletion notice, the deletion discussion is created (this involves creating a new page for AfD and MfD), the discussion page is transcluded onto the daily list (for AfD and MfD only), the page creator is notified (if you requested it), and (optionally for MfD) the owner of the userspace is notified.

Using this module
Click on the XfD tab. In the window that appears, you can choose the deletion discussion forum that is appropriate for the page. Normally Twinkle's initial choice is fine, but sometimes it gets it wrong (especially for userboxes in the Template: namespace, which need to be sent to MfD).

When you choose (or Twinkle chooses for you) a discussion venue, you will be presented with additional options specific to that venue, as follows:
 * AfD:
 * Wrap deletion tag with : This is a rarely-used option that is only needed for articles that are transcluded.
 * Deletion discussion category: Due to the large volume of deletion discussions at AfD, a sorting system is in place, so that users can track deletion discussions that are relevant to their interests and editing. Choose the most appropriate category; if totally unsure, choose "indiscernible or unclassifiable topic".
 * TfD:
 * Inline deletion tag: This option should be selected for templates that appear in line with text: templates such as the infamous fact, and referencing-related templates. If you do not select this option, a line break and wide deletion notice will appear above every instance of the template (as is intended for non-inline templates, like navboxes and cleanup tags).
 * FfD:
 * Possibly unfree file: Choose this to send the file to PUF for discussion instead of FFD.
 * CfD
 * Type of action wanted: You can specify whether the category should be deleted, renamed, merged, or converted into a list in article space. The three last options prompt for a Target page in the box below - this is the category to merge with, the name to which the category should be renamed, or the article to which the category should be converted.
 * MfD
 * Wrap deletion tag with : Use this option for userboxes, and other items that are transcluded (like some project pages, and pieces of portals).
 * Also notify owner of userspace if they are not the page creator (User: and User talk: namespaces only): If the page you are nominating was not created by the same user who has it in their userspace (for example, rescued articles), the owner of the userspace will be notified about the deletion. (But if the owner of the userspace created the page, and you turn off the "Notify if possible" box, no notification will happen ... we think.)
 * RfD has no extra options.

There is one option that applies to all deletion venues:


 * The Notify if possible box, when checked, will cause Twinkle to give the user who created the page an appropriate notification using a boilerplate warning template. This is usually a good idea, but not always necessary, particularly in the case of malfeasant editors. For MfD, the owner of the userspace can also be notified: see above under MfD.

Of course, you must specify a reason why the page should be deleted. You can use full wiki formatting in your reason.

XfD-related pages can be added to your watchlist if you choose this option in your Twinkle preferences. By default, no pages are added to your watchlist when using Twinkle's XfD module. More information is available at the preferences panel.

No userspace log function exists for XfD, as records of all deletion discussions are kept in project space.

Take note
Sometimes, during XfD processing, Twinkle may stall, particularly while adding the discussion to the daily list. The reason for this is unknown; it is believed to be a server issue. You may need to wait more than 20 seconds in some cases.

Extra tools for administrators
For administrators, Twinkle includes a "closer" tool for quickly closing AfD discussions. It has not been extensively tested, and you might have to clean up after it.

Last
This option shows you a diff between the current revision of a page and the previous one.

Unlink
This option unlinks backlinks. Backlinks are links from other pages to a given page. Unlinking them delinks the terms linking to that given page. This is often necessary after speedy deletion to prevent a page on a non-notable, vandalism, or other problematic topic from being recreated. It prevents a bunch of redlinks from showing up all over the place when you delete an article. Depending on the article being deleted, you may or may not want to unlink backlinks.

Tag


The tag tab will tag the article or redirect with the template(s) of your choice.

All templates that are checked will be added to the article in their proper respective locations. Templates that support it will automatically be added with the  parameter populated to the current month and year. If the "Group into if possible" checkbox is ticked, Twinkle will group supported templates into an Multiple issues template, if there are four or more. All other selected templates are then added to the article normally. If there are three or fewer selected templates that are supported by the Multiple issues template, the setting is ignored, and all templates are added to the article normally.

Two templates in the list, globalize and notability, allow you to select from a list of subcategories of the respective templates. The standard template is the default, and selecting a subcategory is not required, but it does place a more specific version of the template on the article.

If you are viewing a redirect page (in any namespace), the tab will present you with a set of redirect categorization tags, from Category:Redirect templates.

DI (delayed speedy deletion for files)
Deletable Image - This part of Twinkle tags files without fair use rationales, sources, or copyright information.

ARV
ARV stands for Advanced Reporting and Vetting (a backronym). This functions similarly to the warn tab. When on any user namespace page, or on Special:Contributions/USER, click this button to report them to administrators for several possible infractions:
 * Vandalism - Reports the user to Administrator intervention against vandalism; use this when the user has vandalized after a final warning has been issued. If you have just reverted the user's vandalism and the user talk page has opened, the fields about the vandalized article (title, revision IDs) should be automatically filled in. Check the appropriate boxes that apply to the user.
 * Vandalism after final warning given - should be checked for most reports
 * Vandalism after recent release of block
 * Evidently vandalism-only account - for username accounts only, with no constructive edits
 * Account is evidently a spambot or a compromised account
 * Account is a promotion only account
 * Username - Reports the user to Usernames for administrator attention. Check the policies at WikiQueer:Username policy to ensure that one of the 4 general reasons applies before ticking off the subexamples.
 * Sockpuppet - Use this to report that a case of suspected sockpuppetry, including the suspected puppeteer and relevant evidence. It will create a new page at Sockpuppet investigations.

Warn (user talk warnings)
On user talk pages, the warn tab allows you to leave one of a variety of warning messages on a user's talk page. To use, first click the warn tab. A window will appear with the following options:
 * Two drop-down menus with the warning level and warning type (see list of warnings)
 * The article name to reference for the warning (this is often automatically populated if you are warning on a user talk page that was opened as the result of a Twinkle rollback)
 * Any additional comments that you wish to be included in the warning message.

Clicking Submit will post the chosen warning to the user's talk page and then refresh the page in your browser.

TB (talkback)
The tb tab will allow you to easily leave talkback templates on other users' talk pages. It supports all of the talkback template's options that you would have available as if you were leaving the template by hand.

Wel (welcome)
The wel tab will welcome the user with selected template.

If an article is specified in the input field, and the template supports an article link, Twinkle will automatically link the template to the article you specified. All templates that support this are marked with an asterisk ("*"). In the case of normal welcome templates, the article would be one that the user contributed positively to. In the case of problem user welcome templates, the article would be one that the user vandalized or did not contribute positively to. This input field is automatically populated if the  URL parameter is found, which is populated by Twinkle after doing a rollback.

Twinkle is capable of supporting a custom list of templates that displays below the standard set of Welcome templates. If you have installed Twinkle, you can add a list of templates that you would like to be added to the Welcome dialogue by changing the "Custom welcome templates to use" option in your Twinkle preferences. Any templates added to this list, when selected, will simply be placed on the user's talk page with no heading, no arguments, and will be followed by your signature.

Shared IP tagging
The shared IP tab will tag the IP as a shared IP address.

Most of the Shared IP templates require that the name of the organization that owns or operates the IP address be input. If one of these templates is selected, Twinkle will require that you fill in the "Organization name" input field, which supports wikitext.

Revert and rollback
When viewing a diff between revisions of a page, Twinkle will place four new links above the previous revision and the new revision:


 * 1) restore this version - Makes that version of the page current.
 * 2) rollback (AGF) - Labels the original edit as AGF in edit summary. (preview)
 * 3) rollback - Performs rollback, then asks for input for edit summary.
 * 4) rollback (VANDAL) - Labels rollback as vandalism in edit summary, and opens vandal's talk page.

Note that the 3 rollback links will only show up on the current revision. If you are viewing a diff between 2 old revisions of a page, only the "restore this version" links will show.

A welcome link will also appear next to a user in a diff view if the user's talk page is empty. Depending on your preferences, this link will automatically welcome the user with the template specified in the "Template to use when welcoming automatically" preference, or open the user's talk page with Twinkle's welcome dialogue already visible (by default). This feature is available when viewing any diff across all namespaces.

Modules for administrators
As well as having access to more features in some of the main modules, administrators also have some modules to themselves:


 * Batch image deletion: This module allows one to delete several images found on a page, or in a category, and unlink them from pages. As this module is fully automatic, it's important to take great care to know what it will do. It might not be the best solution in some circumstances. You should be quite careful with this script, as it has the potential to cause massive damage if used improperly.
 * Batch deletion: Similar to batch image deletion, but for normal pages instead. There are two modules because the processes are not identical. This one is good for closing huge mass AfDs or TfDs.
 * Batch undeletion: Similar to batch deletion, but undeletes instead. Only works on user subpages, so you have to create a list of pages (or transclude one) in your userspace.
 * Batch protection: Similar to batch deletion, but protects the pages instead. It's used often as an emergency option against heavy multiple-page vandalism.
 * Traverse: It wades through a category of images, and for each image it displays it, the page, the history, the file history, the file usage, and allows you to delete it.
 * De-prod: See the PROD section above.
 * Closer: Allows you to quickly close AfC and AfD discussions. For AfD, it deletes the page in question, if that is the outcome of the discussion.

Configuration
The easiest way to configure Twinkle is by using the preferences panel, located at WQ:TW/PREFS. This works by saving a JSON object to Special:MyPage/twinkleoptions.js, which is then read by Twinkle every time you load a page. (That might sound like a performance hit, but your browser will normally cache your personal options page, so it doesn't have to be downloaded every time.)

If the preferences panel goes wrong, or you want to set up some of the advanced preferences described below, you can manually edit Special:Mypage/twinkleoptions.js. Its format is as follows (non-JavaScript-savvy users beware):

Advanced parameters
These parameters are handy to tweak if your browser or network connection is struggling to perform operations without encountering database locks or network timeouts. They are not shown in the preferences panel, and must be modified by manually editing Special:MyPage/twinkleoptions.js.

Regular users can take advantage of the following parameter:


 * : Defines the maximum number of revisions to query when looking for a clean revision to roll back to. The server limit is 50. Default is.

Administrators can use other parameters to fine-tune batch operations, etc.


 * : Defines how many pages should be processed at a time when performing batch deletions. The server limit is 50.  It is recommended that you not change this configuration parameter. Default is.


 * : Defines how many current pages should be left in the process of being deleted before a new batch is allowed to be initialized. It is recommended that you not change this configuration parameter. Default is.


 * : Defines how many pages should be processed at most by any batch function. It is recommended that you not change this configuration parameter. Default is.


 * : Defines how many pages should be processed at a time when performing batch protections. The server limit is 50.  It is recommended that you not change this configuration parameter. Default is.


 * : Defines how many current pages should be left in the process of being protected before a new batch is allowed to be initialized. It is recommended that you not change this configuration parameter. Default is.


 * : Defines how many pages should be processed at a time when performing batch undeletions. The server limit is 50.  It is recommended that you not change this configuration parameter. Default is.


 * : Defines how many current pages should be left in the process of being undeleted before a new batch is allowed to be initialized. It is recommended that you not change this configuration parameter. Default is.


 * : Defines the number of images that will be processed at a time when doing a batch deletion. It is recommended that you not change this configuration parameter. Default is.


 * : Defines the maximum number of images that will be processed when doing a batch deletion. It is recommended that you not change this configuration parameter. Default is.


 * : Defines how many pages should be processed at a time when performing batch prod deletions. The server limit is 50.  It is recommended that you not change this configuration parameter. Default is.

Location of Twinkle menu items
The default location of the Twinkle menu items in the Vector skin is in a drop-down menu; in all other skins they are displayed on the top row of tabs. If you like, you can change the location and layout of those items on your page by manually setting some options in your twinkleoptions.js:

For example, if you want to move the items to the toolbox menu on the left-hand side of the screen, add the line  to your Twinkle preferences, like so:

If you want to display the items as tabs as in the old monobook skin, add the line  to your Twinkle preferences, like so:

is the ID of the portlet you'd like the menus to appear in. In these case, 'p-tb' indicates the toolbar, while 'p-views' indicates the menu bar. For a full list see the catalogue of CSS classes).

Alternatively, you can create a new menu just for the Twinkle items. In that case, add

The  parameter now refers to the specific Twinkle tool set, 'p-twinkle'. indicates where the menu should appear (the value 'column-one' is the sidebar for Monobook; for Vector it is 'panel' and for Modern it is 'mw_portlets'; Other options include 'left-navigation' and 'right-navigation' in Vector and 'mw_contentwrapper' in Modern, which will appear on a new level above the other tabs). Change  to dictate which ID the new Twinkle menu should precede; in this case 'p-search' means it will come before the search box. Change the  parameter to change the name displayed named along with the new menu, if applicable - in this case, "Twinkle".

Ask for support at the Twinkle talk page if you're unsure what to change.