In one of my apps, which is highly targeted towards Enterprise IT types, we're using LinkedIn and Google exclusively.<p>In another app I'm writing, I'm only implementing Github oAuth (as it's closely tied in to Github).<p>In the past, I've written apps that implemented any or all of the usuals, Google, Twitter, Facebook, Yahoo, Foursquare, Dropbox, Flickr, Instagram and (not oAuth, but) OpenID.<p>In my experience, it really depends on what you're building. The first site I mentioned leans towards LinkedIn. More consumer-oriented sites lean towards Facebook/Twitter, followed closely by native auth.<p>I once had a Flickr-tools site (long-since shuttered), obviously, Flickr oAuth dominated that site.<p>If you're building a Facebook app, my guess is that the majority of your users will be Facebook users, so I wouldn't bother to implement anything other than that. If it's an app that will be embedded into Facebook, then your decision's already made, as you can practically inherit logins from Facebook users. If you're planning to serve apps outside of Facebook, then also make sure you're doing native auth.<p>Offtopic slightly, what about dailycred didn't work with your site? In all of the applications I've built, I've only used one auth login library, <a href="https://github.com/omab/django-social-auth" rel="nofollow">https://github.com/omab/django-social-auth</a> (except for the Flickr site, which wasn't Django.) If you have something like dailycred not working, you might need to reconsider how you're structuring your data.<p>The typical implementation pattern is to have User objects (like you'd have if they performed a native auth), and various authentication types that all resolve into the singular User object. Users can authenticate via whatever they want, but only one 'account' exists for them, such that you can attach multiple authentication providers to the same user. FWIW, dailycred does this, and attempts to automatically reconcile (by email I believe) users who might use Twitter to log in today, and Google to log in tomorrow, but are otherwise the same user.