MSPA Wiki:Signature policy

The purpose of a user's signature on the wiki is to identify that user when they sign posts. Accordingly, while we allow users to customise their signatures, there are certain limits that must be adhered to, in order to ensure that the primary purpose of signatures is not compromised.


 * 1) A link to the user's userpage is mandatory, and the text of a signature must include the username, or at least something extremely similar, in clearly readable Latin text. All of this is to ensure the purpose of identification is not compromised.
 * 2) Signatures should not have pointless excess text. This is because having a large quantity of text that is not the username detracts from the purpose, and also looks untidy. Something like -- Username (talk |contribs ), August 28, 2024 (UTC) is fine. Anything much longer than that is not. Furthermore, all text in the signature should serve a purpose by linking to a page. If the text is not a useful contribution to the signature, it should be left out.
 * 3) *It is suggested, but not mandatory, that the signature include a link to the user's talk page. This link can be separate, as above, or some of the username text may be used.
 * 4) Images, text, frames, or whatever else goes into the signature must not exceed 15 pixels in height, i.e. the signature must not increase inline height or visibly overlap the lines above and below. 15px is the height of a line of text.
 * 5) Signatures may include no more than one small image. This rule is non-negotiable.
 * 6) *Animations are strongly discouraged, and the EnglishO.gif gif, or anything similarly distracting, is prohibited.
 * 7) A certain amount of visual flair is permitted, but if it's more than about half a line of markup, make it a template, and ensure that it transcludes, not substitutes. See the section below for information on this.

Permitted
Just about any decoration possible with wikimarkup is permitted, provided it is in moderation and adheres to the above rules. Here are some examples of permitted customised signatures, in order of increasing complexity.

Per Ankh, ED
 * Per Ankh uses no real markup flair in his signature. The only notable feature is that ED stands for experimentalDeity, his chumhandle, and those two letters link to his talk page.

Ryūlóng ( 竜龍 )
 * Ryulong's signature is simple. The accented letters are perfectly readable, and it is clear whose signature this is. There is a little colour used to make it more lively, but not to the point of being garish. Finally, the non-Latin text is permitted because it is not obscuring the username, and it serves a purpose by being a talk page link.

J i m c l o u d 
 * Jimcloud's signature is plain text, decorated with each letter being a slightly different colour so as to form a gradient. The first three letters link to her userpage, the next three to her talk page, and the final two to her contributions.

 s k a i a r o r N e t b o d y 
 * Sorceror Nobody's signature demonstrates perhaps the limit of what policy permits. His username is not used; however, his chumhandle, skaiarorNetbody, is extremely similar to his username, and so he uses it in his signature. Like Jimcloud, he uses a colour gradient, and also split linking, with the first half linking to his userpage and the second to his talk page. Finally, he has a text glow effect which does not increase line height, and the glow radius (less than two pixels) is small enough that it doesn't visibly overlap other lines.

Forbidden
In order to avoid making a negative example of specific people, these samples are fabricated. However, they are all based on actual signatures which have been used on the wiki in the past.

ǝwɐuɹǝs∩
 * This is not Latin text. It is a string of mostly meaningless symbols that happen to resemble upside-down Latin text, and suffice to say, even if they were actual upside down letters, that still wouldn't be allowed. Signatures must be clearly readable. The user whose signature this is based on also had the "text" saying something not even remotely close to their username.

NotARealUsername
 * The displayed name is nothing like the actual username, both the images and the frame are well over 15px high, and the images add nothing, as they don't link to anything other than their own File pages. Furthermore, there are two images, when only one is permitted.

  User n@me~ <span style="border:2px dashed skyblue; background-color:black; border-top-right-radius:10px; border-bottom-right-radius:10px; width:23em; padding: 1px">
 * In the original signature, the leftmost image linked to the userpage (not ideal, but technically allowed), the text linked to the user talk page, and the aspect symbol linked to the user's contributions. However, the block of colour is over 15px and will therefore either increase line height or overlap surrounding lines. Two images is one too many, and the LE gif is specifically prohibited. Furthermore, given the colour splitting of the username, the LE gif is unneeded, as the userpage link could be on the green half of the username. The nonstandard use of an ampersat (@) and tilde (~) in the signature are, however, permissible, as they don't impair readability

How to create a signature
Create the page "User:(your username}/Signature". On this page, save the markup for your signature. It's as simple as that. Your signature can then be used by simply typing " " (the five tildes for a timestamp) instead of the standard four tildes.

If you want to be able to use your template signature by simply typing four tildes as normal, this is possible, but you must not simply transclude your signature into the custom signature field in your preferences. Doing so would substitute all of the code of your signature instead of just transcluding it, which would result in large blocks of markup all over talk pages.

Instead, you must create a second page in your userspace, e.g. "User:(name}/Signature2", and on that page, place the transculsion code, " ". You can then place this page as a transclusion, "  ", in the custom field in your preferences. Now, when you use " ~ " to sign, it will substitute the second page, which is simply  a transclusion of the first, rather than substituting the first page and leaving a mess of code.