Devise

I had a look at the device authenticator and did two things:

1. Update to devise 3. The problem here is that I had to kill :token_authenticatable, as we discussed last Wednesday. I then wanted to have a look on how to solve the fallout from this, but I fail to see any. Could you elaborate where this feature is used at the moment and what this change breaks?

2. Add a private ConfirmationsController implementation to allow sign in after confirmation. This feature is potentially unsafe though, as it relies on an email security model that doesn't exist.