{"id":121,"date":"2009-09-22T14:12:05","date_gmt":"2009-09-22T21:12:05","guid":{"rendered":"http:\/\/kai.mactane.org\/blog\/2009\/09\/22\/what-characters-are-allowed-in-twitter-usernames\/"},"modified":"2013-02-22T09:20:20","modified_gmt":"2013-02-22T17:20:20","slug":"what-characters-are-allowed-in-twitter-usernames","status":"publish","type":"post","link":"https:\/\/kagan.mactane.org\/blog\/2009\/09\/22\/what-characters-are-allowed-in-twitter-usernames\/","title":{"rendered":"What Characters Are Allowed in Twitter Usernames"},"content":{"rendered":"

A while back, when I was writing Hummingbird, I needed to look for Twitter usernames in various strings. More recently, I’m doing some work that involves Twitter at my new job. Once again, I need to find and match on Twitter usernames.<\/p>\n

Luckily, this time, Twitter seems to have updated its signup page with some nice AJAX that constrains the user’s options, and provides helpful feedback. So, for anyone else who needs this information in the future, here’s the scoop:<\/p>\n

    \n
  1. Letters, numbers, and underscores only. It’s case-blind, so you can enter hi_there<\/code>, Hi_There<\/code>, or HI_THERE<\/code> and they’ll all work the same (and be treated as a single account).<\/li>\n
  2. There is apparently no minimum-length requirement; the user a exists on Twitter<\/a>. Maximum length is 15 characters.<\/li>\n
  3. There is also no requirement that the name contain letters at all; the user 69<\/a> exists, as does a user whose name I can’t pronounce<\/a>.<\/li>\n<\/ol>\n

    If you want a regex to match on this, \/[a-zA-Z0-9_]{1,15}\/<\/code> would be nice and safe for use in both POSIX and Perl-style regex syntax. (If you’ve got Perl-compatible regexes, \/\\w{1,15}\/<\/code> is quick and easy. Update:<\/strong> And it’s wrong<\/em>; see comment 6 below, by Mark Fowler.)<\/p>\n","protected":false},"excerpt":{"rendered":"

    A while back, when I was writing Hummingbird, I needed to look for Twitter usernames in various strings. More recently, I’m doing some work that involves Twitter at my new job. Once again, I need to find and match on Twitter usernames. Luckily, this time, Twitter seems to have updated its signup page with some […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[7,62,71,64,36,72],"_links":{"self":[{"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/posts\/121"}],"collection":[{"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/comments?post=121"}],"version-history":[{"count":4,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/posts\/121\/revisions"}],"predecessor-version":[{"id":122,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/posts\/121\/revisions\/122"}],"wp:attachment":[{"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/media?parent=121"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/categories?post=121"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/tags?post=121"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}