Chase Gilliam

Sorry, I was reading it on my phone. I'll look at the generators. Honestly, we're probably going to take a serious look at the generators for 1.0.

That makes sense. We could make this default behavior for linkedin, but it would probably be good to generalize this sort of thing.

I think it might be best to drop Oauth support in Sorcery 1.0 for Linkedin. But, I'm not 100% confident in that decision. Thoughts?

Sorry, I meant OAuth 1.0 in favor of 2.0. I have to stop replying to these on my phone.

@athix I think that is the best path forward as well.

awesome.

This is an interesting use case. @rivsc, what are you doing with this problem now?

@brendon come join us on the new repo over at the new repo https://github.com/Sorcery/sorcery. Unfortunately using Sorcery with Devise isn't a supported use case at the moment.

@brendon ahh good old active admin. If you file an issue over at the new repo, we'll take a look. A demo app might be helpful.

I kind of get the inclination to use `Slim`, as I used to be a `Haml` fan, but I think `eex` works well enough and doesn't add an extra dependency....