ballantyne/omniauth-tqq — comment on commit 8ef550aa8ccf3bdf625f869c8bab1bd262b13a56
File:  line 0
By ballantyne:

I'm just reimplementing them as gems because that is the way it works
for strategies in omniauth 1.0. Its the new way. I also found the
uid problem and think that the only way that I found was an additional
api call.

On Tue, Nov 1, 2011 at 2:18 PM, utensil

wrote:
> Hi!
>
> I've been using the tqq strategy implementation from omniauth itself(oa-oauth/lib/omniauth/strategies/tqq.rb) which is originally contributed by @he9qi. Also the t163, weibo, douban, sohu etc.
>
> I wonder why you're working on them again, and if you're done, they would probably conflict with them?
>
> As for the uid issue, IMHO, it's ok to make another api call to get uid, since an user_info api call was already made. Actually I opened an issue at https://github.com/intridea/omniauth/issues/519 to discuss the lost of uid, and planned to fix it.....Though I've already done some fall-back(such as using a unique username field) in my app to work around even when there's no uid.
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/ballantyne/omniauth-tqq/commit/8ef550aa8ccf3bdf625f869c8bab1bd262b13a56#commitcomment-686901
>