Lots of broken stuff related to omniauth.
Refs #109 - I circle ever closer. No fixed tests here, but I am sure that I solved one of the errors the site was throwing at me. The problem was that I accidentally mixed a piece from  the omniauth tutorial in without moving to the next step where I generated its controller. Now that is sorted, but it is giving me this error: ActiveRecord::StatementInvalid in Users::OmniauthCallbacksController#twitter

SQLite3::SQLException: no such column: users.provider: SELECT  users.* FROM users  WHERE users.provider = 'twitter' AND users.uid = '936961322' LIMIT 1
Refs 109. I fixed the previous error as well as a Cookie overflow error that popped up. Now when I click through, it just reroutes you back to the main page. I have also been running into problems with the callback - based on stackoverflow discussions, it looks like Twitter's system is not particularly supportive of running local servers as callbacks. I think the current situation has to do with the twitter method in users/omniauth_callbacks_controller.rb. It looks like it runs the authentication but doesn't log that as making a user. Stackoverflow suggests making some sort of flag so that the system knows that a user has been created. I also started tinkering with a dummy facebook account in relation to this, but then I decided to stick with the work on twitter.
Successfully authenticates through twitter now! We have to pass it a fake e-mail though, which now displays as the 'signed in as XX' name. We might want to switch the display there to display the nickname instead. We will also want to have a conversation about how we're using e-mails instead of user names right now. Refs #109.
Merge.