TechInfoDepot:Signatures

Signing your posts on talk pages, both for the article and non-article namespaces, is good practice, and facilitates discussion by helping identify the author of a particular comment. Other users can then navigate to a talk page and address their comments to the specific, relevant user(s). Discussion is an important part of collaborative editing, because it helps all users to understand the progress and evolution of a work.

Comments posted on user talk pages, article talk pages and other discussion pages should be properly signed. Signature use that is intentionally and persistently disruptive may lead to blocking under the disruptive editing policy.

When editing a page, main namespace articles should not be signed, because the article is a shared work, based on the contributions of many people, and one editor should not be singled out above others.

Purpose of signatures
Signatures on TechInfoDepot identify you as a user and your contributions to TechInfoDepot. They encourage civility in discussions by identifying the author of a particular comment and the date and time at which it was made. Because of that, having an uncivil signature is strongly discouraged (in some cases, to the point of blocking the user until it is changed). In general, anything that is not allowed in a user name should not be used in a signature either.

Furthermore, signatures also serve a technical purpose: various user scripts and talk-page archiving bots, including MiszaBot, rely on their time stamps to know when to archive old threads. It's because of this that it's also important to avoid overly customizing the date output of a signature, as doing so can lead to stale threads persisting long after they'd otherwise be archived.

When signatures should and should not be used
Any posts made to the user talk pages, article talk pages and any other discussion pages must be signed. Edits to articles must not be signed, as signatures on TechInfoDepot are not intended to indicate ownership or authorship of any article. Rather, the page history takes care of the need to identify edits with users. Therefore, signatures should not be used in edit summaries, as they do not translate from. In other instances, when posts should not be signed, specific instructions are provided to contributors.

Using four tildes
There are two ways to sign your posts:


 * 1) At the end of your comments simply type four tildes (~), like this:.
 * 2) If you are using the edit toolbar option (it usually appears above the edit screen as a default), click the signature icon: Signature icon.png or Insert-signature.png, to add the four tildes.

Your signature will appear after you have saved the changes. The end result is the same in both cases.

Typing four tildes will result in the following:

Since typing four tildes adds the time and date to your resulting signature, this is the preferred option for signing your posts in discussions.

Note that if you choose to contribute without logging in, regardless of whether you have an account, you should still sign your posts. In this case your IP address will take the place of your username, and will link to your contributions history. Your IP address might look something like 192.0.2.213 or 2001:DB8:CEEE:21B:DB60:07FE:4277:63FF.

If, for some reason, you are not getting the above results when signing, see the SineBot Frequently Asked Questions for tips.

Using three tildes
Typing three tildes results in the following:

However, since this does not date-stamp your signature, you may wish to sign this way only when leaving general notices on your user page or user talk page. This is also a convenient shortcut (rather than typing out the full code) when you want to provide a link to your user page.

Using five tildes
Typing five tildes will convert to a date stamp with the current date and time, without adding your signature, like this:

In general, when communicating with others, you should use one of the previous options, and not only a timestamp.

Customizing your signature


Every editor's default signature (defined by MediaWiki:Signature) will display when  is typed. This looks like:

Example (talk), 27 August 2024 (UTC)

Unregistered users who sign manually with a pseudonym or tag such as --anon. or 192.58*, still have their IP address stored in the page history. If you choose to sign in that way, to make it easier for other users to communicate with you, you should still type four tildes: --192.58*.

Registered users can customize their signatures by going to Special:Preferences and changing the field "Signature". If you do not check the "Treat the above as wiki markup" box, the exact text you enter will be shown as your signature, for example:

NICKNAME (talk), 27 August 2024 (UTC)

If you check the "Treat the above as wiki markup" box, you may enter wikitext (such as and wiki-markup ) for your signature. However, you should consider the guidelines below.

When customizing your signature, please keep the following in mind: A distracting, confusing, or otherwise unsuitable signature may adversely affect other users. For example, some editors find that long formatting disrupts discourse on talk pages, or makes working in the edit window more difficult. Complicated signatures contain a lot of code ("markup") that is revealed in the edit window, and can take up unnecessary amounts of narrative space, which can make both reading and editing harder.

Signature forgery
Never use another editor's signature. Impersonating another editor by using his or her username or signature is forbidden. Altering the markup code of your signature to make it look substantially like another user's signature may also be considered a form of impersonation. Editing the code of your signature to link it to another editor's user page is not permitted. It is also ineffective, as the change log of the page records the IP address and (if applicable) username of all editors; as such, any impersonators can easily be caught if the signature in the diff view differs from the editor's default signature. While not an absolute requirement, it is common practice for a signature to resemble to some degree the user name it represents.

If you encounter a user whose signature is disruptive or appears to be impersonating another account, it is appropriate to ask that user to consider changing their signature to meet the requirements of this guideline. When making such a request, always be polite, and assume good faith. Do not immediately assume that the user has intentionally selected a disruptive or inappropriate signature. If you are asked to change your signature, please avoid interpreting a polite request as an attack. Since the success of TechInfoDepot is based on effective teamwork, both parties should work together to find a mutually acceptable solution.

Signature formatting has been the subject of Requests for Comment, and has also resulted in some very heated debates. In one case a user who refused to alter an unsuitable signature was ultimately required to change it by the Arbitration Committee. This is an extreme measure for users who refuse to cooperate with reasonable requests, and should be considered a last resort. When dealing with potentially problematic signatures, simply being polite is often sufficient and can prevent the situation from escalating into a dispute.

Appearance and color
Your signature must not blink, scroll, or otherwise inconvenience or annoy other editors.


 * Avoid markup such as  and  (or more) tags (which produce big text), or line breaks (  tags), since they disrupt the way that surrounding text displays. The limited use of non-breaking spaces to ensure that the signature displays on one line is allowed.
 * Be sparing with superscript or subscript. In some cases, this type of script can also affect the way that surrounding text is displayed.
 * Do not make your signature so small that it is difficult to read.
 * As some users have vision problems, be sparing with color. If you insist on using different colors in your signature, please ensure that the result will be readable by people with color blindness, defective color vision, and other visual disabilities.
 * Do not include horizontal rules.

To display your signature in a different color for yourself only, add the following to Special:MyPage/common.css, replacing YOUR_NAME with your username:
 * #bodyContent a[title="User:YOUR_NAME"] { background-color: #ff7700; color: #ffffff; }

For guidance on how to use color to customize the appearance of your signature, see this Tutorial.

Images
Images of any kind must not be used in signatures for the following reasons:
 * They are an unnecessary drain on server resources, and could cause server slowdown
 * A new image can be uploaded in place of the one you chose, making your signature a target for possible vandalism and denial-of-service attacks
 * They make pages more difficult to read and scan
 * They make it more difficult to copy text from a page
 * They are potentially distracting from the actual content
 * Images do not scale with the text, making the lines with images higher than those without them
 * They clutter up the "file links" list on the respective image's page every time one signs on a different talk page
 * Images in signatures give undue prominence to a given user's contribution

Length
Keep signatures short, both in display and in markup.

Extremely long signatures with a lot of HTML/wiki markup make page editing and discussion more difficult for the following reasons:
 * Signatures that take up more than two or three lines in the edit window clutter the page and make it harder to distinguish posts from signatures.
 * Long signatures give undue prominence to a given user's contribution.
 * Signatures which have long HTML/wiki markup and contain no spaces cause other editors' edit boxes to show unnecessary horizontal scrollbars (such signatures may have spaces added to them by any editor).
 * Signatures that occupy more space than necessary in the edit box displace meaningful comments, thus forcing the editor to scroll when writing their reply.
 * The presence of such long signatures in the discussion also disrupts the reading of comments when an editor is formulating their reply.

The software will automatically truncate both plain and raw signatures to 255 characters of code in the signature box. If substitution of templates or another page is used, please be careful to verify that you are not violating the length limit, as the software will not do this automatically.

Internal links
Signatures must include at least one internal link to your user page, user talk page, or contributions page; this allows other editors easy access to your talk page and contributions log. The lack of such a link is widely viewed as obstructive.

If, while making modifications, you accidentally disable this link, see TechInfoDepot:How to fix your signature. When you insert your signature on your talk page or user page, a link to that page will appear black, bold and inactive, so test your signature elsewhere, such as the Sandbox.

Disruptive links
It is better to put information on your user page rather than in your signature. Brief additional internal links are generally tolerated when used to facilitate communication or to provide general information, but undesirable if seen as canvassing for some purpose.

Do not place any disruptive internal links, such as SIGN HERE!!! , which refers to an autograph page.

Transclusion of templates (or other pages)

 * Transclusions of templates and parser functions in signatures (like those which appear as, for example) are forbidden for the following several reasons:
 * Certain automated scripts (bots) are used to automatically archive particularly active talk pages. These bots read the source of the talk page, but don't transclude templates, and so don't recognize the template as a signature.
 * Signature templates are vandalism targets, and will be forever, even if the user leaves the project.
 * Signature templates are a small but unnecessary drain on the servers. Transcluded signatures require extra processing—whenever you change your signature source, all talk pages you have posted on must be re-cached.
 * Substitutions of templates in signatures is permissible but discouraged, as the substituted page may be vandalized without the user knowing.
 * Users who choose to substitute their signature are required to be highly vigilant of their signature whenever they sign.

Simple text signatures, which are stored along with the page content and use no more resources than the comments themselves, avoid these problems.

Categories
Signatures must not contain categories. Categorizing talk pages by who has edited them is unhelpful, and the same information can be found by using your contributions list. Many of the various edit counting utilities also provide this data.

Non-Latin usernames
Editors with non-Latin usernames are welcome to edit in TechInfoDepot. However, non-Latin scripts, such as Arabic, Armenian, Chinese, Cyrillic, Greek, Hebrew, Indic scripts, Japanese, Korean, Persian, Thai and others, are illegible to most other contributors of the English TechInfoDepot. Not everyone uses a keyboard that has immediate access to non-Latin characters, and names that cannot be pronounced cannot be retained in memory. As a courtesy to the rest of the contributors, users with such usernames are encouraged to sign their posts (at least in part) with Latin characters. For an example refer to User:Παράδειγμα, who signs his posts as Παράδειγμα/Paradigma.

A signature consisting of or ending with characters from a right-to-left script will appear when viewing pages as --DD ,HH:MM (NAME) Month YYYY and in the edit box as  . Adding a left-to-right marker symbol, at the end of the raw signature (HTML code: ), will resolve this. Or, if you include both Latin and a right-to-left script, such as Hebrew or Arabic, in your signature, consider putting Latin second, where it will be directly next to the timestamp.

Dealing with unsigned comments
The templates unsigned and unsignedIP can be used at the end of an unsigned comment to attach the username or IP to the comment. None of these templates automatically populate (fill in) the name or IP of the poster and the time of the post. That information is best copied from the history page and pasted into the following templates. Note: All of the unsigned templates must be substituted.

The templates unsigned2 and unsignedIP2 do almost the same as unsigned and unsignedIP when used with two parameters, but the ordering of the parameters is reversed. The resulting display is the same. These templates may be useful when copying and pasting from the edit history, where the timestamp appears before the username.

It is also a good idea to notify users, especially new users, that they should sign their comments. You may use the template uw-tilde on the user's talk page or one of the welcome messages for new users.

Also, the template undated can be used at the end of comments where the user gave his or her username but no timestamp:

Automatic adding of signatures
The bot SineBot signs comments on talkpages and pages in Category:Non-talk pages that are automatically signed, for unregistered users and users who have less than 800 edits. To re-enable autosigning of your unsigned comments, you can place on your user page or user talk page.

Dealing with problem signatures
TechInfoDepot's Username policy describes accepted practices and behavior in naming and operating a user account on TechInfoDepot that apply to both usernames and signatures. A purpose of your signature is to identify you as a contributor. If your signature is unnecessarily confusing or inaccessible, editors may request that you change it. An editor with a confusing signature may be blocked sooner than usual for other inappropriate behavior such as disruption or vandalism, if their confusing signature contributes to the disruption.

Signatures that link to, but do not display, the user's username (for example by signing with a nickname, as in  User:Nickname  or  Nickname ) can be confusing for editors (particularly newcomers). The actual username always appears in the page history, so using just the nickname on the relevant talk page can make your signed comments appear to be from a different person. Alternatives include changing your username and including your account name in addition to the username, e.g. in the form  User:Example/Nickname .

Persistent failure to sign may become disruptive, and if it is persistent, despite the problems being pointed out to the user, doing so may be subject to sanctions.