Most web based user authentication systems don't like usernames that contain characters other than letters, numbers and underscores.
Is there any particular reason for that?
+1
A:
Depends how your usernames are used. There isn't a general rule, without knowing the context.
Noon Silk
2010-01-12 23:47:34
A:
People may want to write their usernames like_this rather than likethis or LikeThis.
John at CashCommons
2010-01-12 23:47:53
+2
A:
Because it allows multiple words to be represented in a somewhat readable manner.
Peronally I really, really wish folks would expand things a bit to allow dashes and apostrophes. This would allow people to use non-english phonetic names (eg: Native American tribal names like She-Ki and Ke`Xthsa-Tse)
T.E.D.
2010-01-12 23:48:05
+4
A:
A well-designed system doesn't necessarily need to prevent any special characters in usernames.
That said, the reason underscores have traditionally been accepted, is that underscore is typically treated as a "word" character, along with letters and numbers. It is usually the only other character given this distinction. This is true in regular expressions, and even at a base level in most operating systems (type an underscore in a word and double click the letters. The selection will extend past the underscore. Now try the same with a dash, it most likely will not.)
Renesis
2010-01-12 23:48:39
Well characters which are not easy to read or ones that make the system messy are good candidates to disallow. A username like !@#$% would be bad.
Veger
2010-01-12 23:50:51
Although Veger's comment is valid from a usability standpoint, it misses Renesis point, which is a technical one: there are no inherent technical limitations to what comprise a "username".
gWiz
2010-01-12 23:53:45
+2
A:
The main reason websites enforce such rules is readability (because usernames like ~-|this<>one|-~ are annoying). It might also be because it's less work (underscores get matched by a \w+ regex, while dashes and other special characters don't), but I doubt that's a major reason.
There is no "standard", so if neither of the above reasons bother you, do whatever you'd like. Personally I'd like to see more websites accept dashes and periods, but it's really a personal preference of readability and consistency vs expression.
musicfreak
2010-01-12 23:50:49
Renesis
2010-01-13 00:06:05
@Renesis: Yeah but you could just add a number to the end of the name anyway. Sure, it's more obvious than a period, but it'll work no matter what character restrictions you add to the system.
musicfreak
2010-01-13 00:09:10
+1
A:
Underscore was traditionally allowed in identifiers in most programming languages, and was generally the only "special" character allowed.
But many web login still do not accept ANY special character and are limited to lower/upper case characters and digits...
And other are fine with really special ones ;-)
François
2010-01-12 23:50:55
+2
A:
When not specified I use this:
^\w(?:\w*(?:[.-]\w+)?)*(?<=^.{4,32})$
This requires a length of 4 with maximum 32 characters. It must start with a word character and can have non continuous dots and dashes. The only reason I use this is because it's strict enough to integrate with almost anything :)
Valid :
test.tost
Invalid :
test..tost
Diadistis
2010-01-12 23:57:30
A:
I don't like the readability argument when it interferes with the ability for people to use their native language in usernames.
I recommend you experiment with using character classes that incorporate http://msdn.microsoft.com/en-us/library/20bw873z.aspx#SupportedUnicodeGeneralCategories or http://msdn.microsoft.com/en-us/library/20bw873z.aspx#SupportedNamedBlocks. I haven't tried this, but
[\p{L}\p{N}\p{M}]
might be worth an experiment.
John Saunders
2010-01-13 00:17:13