Twitter ID isn't validated before creating name tag

[seanyo]

This issue is basically a todo list for validating the tid.

When we start working on each of these todos, remove it from this issue and start a new one for that specific work.

• We need to ensure tid's a valid, so something like ^[a-zA-Z09]+ and tid.length <= 15

  Validation should be part of the js code, since users could manually enter a URL or we might offer external calls to the nametag widget. So, while we could do validation on the landing page form, I don't think its as useful to validate form input as script data

[ccharles]

Removing the following issue (fixed along with issue 5):

Twitter ID also needs to be tested for public/private status; if the account is private we should ask for their credentials in a friendly way - I'm not sure if full blown OAuth is needed or not, but I could see that it might be: http://dev.twitter.com/pages/oauth_faq

[ccharles]

Removing the following issues (fixed in issue #6):

• If the Twitter ID doesn't exist, the nametag is still created but is empty.

  A simple test for this could be a null length object from the getJSON call

• Twitter.com isn't tested to see if it is available. We need to ensure Twitter is responding and throw a friendly error for humans if it isn't.

  Let's start by testing for a non-200 HTTP Response Code from the tweeturl variable The jsXHR object looks useful here for response codes and hopefully a null state as well: http://api.jquery.com/jQuery.ajax/#jqXHR

[ccharles]

Do we need to distinguish between "invalid Twitter ID" (i.e. this profile cannot exist) and "Twitter can't find your profile" (i.e. this profile can exist, but probably doesn't)?

[ccharles]

I'm going to go ahead and close this. I don't see any value in testing for a possibly valid TwitterID before requesting the JSON file from Twitter.

If there is a valid reason to test this (and some reliable source can be found for what actually is a valid Twitter ID) this can be reopened.