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.
Upgrade Devise

Upgrades Devise to lock it at the 2.2.x version of the gem.
Removes deprecated (and unused) configuration variables
Merge.
Removed the debug information from Twitter. The facebook error was coming from the Facebook settings end of things. Wtih a tweak to redirect url, Facebook now authenticates.
Failing code for Google.
This is the code build that runs on Eric R.'s computer. The error I am getting on mine is 'Authentication failure! service_unavailable: OpenSSL::SSL::SSLError, SSL_connect returned=1 errno=0 state=SSLv3 read server key exchange B: bad ecpoint.' Eric hypothesizes that it might be particular to my computer. Only change is the one line of code. If it is local to my machine, this will make all three authentications work. Refs #109.
Refs #109. Deleted an unncessary/unsuccessful workaround for the Google authentication. All three are working - the errors I got were local to my computer.
Closes #151.
Fixes the problem by adding a conditional in the header file. If the e-mail is equal to 'none@nomail.com' it will automatically pass it the Twitter id. The workaround works, and fixes the issue. But I'm not sure it's the most elegant solution. It's ready to close so long as we don't mind hammering the change through in what way. Now it will display 'Signed in as @walshbr.' Note that the @ symbol is added in ruby and is not part of the database.
Closed a couple conditional statements that would have caused a crash if a new user tried to create an authentication.
Cleans out some unneeded code. Refs #155.
Refs #153. Now it uses figaro to store the keys as ENV variables in config/application.yml, which is in .gitignore. For that reason, people won't be able to use the omniauth authentications on their local machines, and we'll have to figure out some other way to get the credentials for deployment in heroku.
Fixes all the things.
Makes users can log in with either email or nickname. Makes it so email and nickname are not required. Adds a couple tests for displaying email and nickname on the page. Still remaining bug - you can log in without either a nickname or email now.
Currently, the code won't register any users.
This is a placeholder before I start deleting twitter.
Twitter nuked. Code passing.