It might be a bug in django-social-auth. I've had a couple of people complain about it, but I can't reproduce it even if I create a new GitHub account. I've found bugs in DSA before, such as https://github.com/omab/django-social-auth/pull/697
I'll have to look into it more. Sorry about that. :(
In Show HN: Floobits – Remote pair programming done rightomab
django-social-auth
Python2011–2013
omab / django-social-auth
django-social-auth
Django social authentication made simple
10Distinct people
11Mentions
0Explicit recommenders
2.6KGitHub stars
What to know before exploring
What it is
Django social authentication made simple
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month11 dated mentions
Observed mentions: 2011-01-12 21:03:29 UTC to 2013-07-18 17:01:20 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jan 2011 | 2011-01-01 00:00:00 UTC | 2011-02-01 00:00:00 UTC | 2 | 1 | 1 |
| Feb 2011 | 2011-02-01 00:00:00 UTC | 2011-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2011 | 2011-03-01 00:00:00 UTC | 2011-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2011 | 2011-04-01 00:00:00 UTC | 2011-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2011 | 2011-05-01 00:00:00 UTC | 2011-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2011 | 2011-06-01 00:00:00 UTC | 2011-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2011 | 2011-07-01 00:00:00 UTC | 2011-08-01 00:00:00 UTC | 1 | 0 | 1 |
| Aug 2011 | 2011-08-01 00:00:00 UTC | 2011-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2011 | 2011-09-01 00:00:00 UTC | 2011-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2011 | 2011-10-01 00:00:00 UTC | 2011-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2011 | 2011-11-01 00:00:00 UTC | 2011-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2011 | 2011-12-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2012 | 2012-01-01 00:00:00 UTC | 2012-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2012 | 2012-02-01 00:00:00 UTC | 2012-03-01 00:00:00 UTC | 3 | 1 | 2 |
| Mar 2012 | 2012-03-01 00:00:00 UTC | 2012-04-01 00:00:00 UTC | 1 | 0 | 1 |
| Apr 2012 | 2012-04-01 00:00:00 UTC | 2012-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2012 | 2012-05-01 00:00:00 UTC | 2012-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2012 | 2012-06-01 00:00:00 UTC | 2012-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2012 | 2012-07-01 00:00:00 UTC | 2012-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2012 | 2012-08-01 00:00:00 UTC | 2012-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2012 | 2012-09-01 00:00:00 UTC | 2012-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2012 | 2012-10-01 00:00:00 UTC | 2012-11-01 00:00:00 UTC | 1 | 0 | 1 |
| Nov 2012 | 2012-11-01 00:00:00 UTC | 2012-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2012 | 2012-12-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2013 | 2013-01-01 00:00:00 UTC | 2013-02-01 00:00:00 UTC | 2 | 0 | 2 |
| Feb 2013 | 2013-02-01 00:00:00 UTC | 2013-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2013 | 2013-03-01 00:00:00 UTC | 2013-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2013 | 2013-04-01 00:00:00 UTC | 2013-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2013 | 2013-05-01 00:00:00 UTC | 2013-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2013 | 2013-06-01 00:00:00 UTC | 2013-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2013 | 2013-07-01 00:00:00 UTC | 2013-08-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
NOTE: THIS LIBRARY IS DEPRECATED IN FAVOR OF python-social-auth. RIGHT NOW
THIS LIBRARY DEPENDS DIRECTLY ON python-social-auth AND SHOULD BE CONSIDERED
AS A MIGRATION STEP
Django Social Auth
Django Social Auth is an easy way to setup social authentication/authorization
mechanism for Django projects.
Crafted using base code from django-twitter-oauth and django-openid-auth,
it implements a common interface to define new authentication providers from
third parties.
You can view this app's documentation on Read the Docs too.
Table of Contents
Django Social Auth
Features
Demo
Contact
Documentation
Dependencies
Installation
Support
Copyrights and Licence
Features
This application provides user registration and login using social site
credentials. Some features are:
Registration and login with social sites using the following providers
at the moment:
Google OpenID
Google OAuth
Google OAuth2
Yahoo OpenID
OpenId like myOpenID
Twitter OAuth
Facebook OAuth
Some contributions added support for:
DISQUS OAuth
LiveJournal OpenID
Orkut OAuth
Linkedin OAuth
Foursquare OAuth2
GitHub OAuth
Dropbox OAuth
Flickr OAuth
Vkontakte OAuth
MSN Live Connect OAuth2
Skyrock OAuth
Yahoo OAuth
Evernote OAuth
Mail.ru OAuth
Odnoklassniki OAuth
Mixcloud OAuth2
BitBucket OAuth
Douban OAuth
Fitbit OAuth
Instagram OAuth2
Twilio
Trello OAuth
Weibo OAuth2
Yandex OpenId
Shopify OAuth2
StockTwits OAuth2
Stackoverflow OAuth2
Fedora OpenID
Exacttarget HubExchange
Appsfuel OAuth2
Basic user data population and signaling to allows custom fields values
from providers' responses
Multiple social account associations to a single user
Custom User model override if needed (auth.User by default)
Extensible pipeline to handle authentication/association mechanism
Demo
There's a demo at http://social.matiasaguirre.net/.
Note: It lacks some backends' support at the moment.
Contact
Join the django-social-auth discussion list and bring any questions or suggestions
that would improve this application.
Also join the IRC channel #django-social-auth on Freenode server.
Documentation
Extensive documentation at Read the Docs.
Dependencies
Dependencies that must be met to use the application:
OpenId support depends on python-openid
OAuth support depends on python-oauth2
Several backends demands application registration on their corresponding
sites
Installation
From pypi:
$ pip install django-social-auth
or:
$ easy_install django-social-auth
or clone from github:
$ git clone git://github.com/omab/django-social-auth.git
and add social_auth to PYTHONPATH:
$ export PYTHONPATH=$PYTHONPATH:$(pwd)/django-social-auth/
or:
$ cd django-social-auth
$ sudo python setup.py install
Support
If you're having problems with using the project, use the support forum at CodersClan.
Copyrights and Licence
django-social-auth is protected by BSD licence.
Some bits were derived from others' work and copyrighted by:
django-twitter-oauth:
Original Copyright goes to Henrik Lied (henriklied)
Code borrowed from https://github.com/henriklied/django-twitter-oauth
django-openid-auth:
django-openid-auth - OpenID integration for django.contrib.auth
Copyright (C) 2007 Simon Willison
Copyright (C) 2008-2010 Canonical Ltd.
Read the full README on GitHubWhat Hacker News says
11 sourcesFirst suggestion: show the 2nd level in your Table of Contents.
That's helpful for customers like me who would buy the book if they knew a bit more details about what's inside (I don't want to buy something and then find out I know most of the contents already).
Another suggestion that would get me to buy the book: does the book addressed particular issues that I know I need to figure out (and will save me from having to do my own research).
In particular, would be useful if the marketing of the book told me that it would discuss specific tasks/decisions. Some examples of tasks:
-how to code my django app so it works in both python 2.7 and python 3? What's the best way to do that? Django six? How do I setup virtualenv to support my dual configuration? I think this is what the django core team is doing nowadays so I can also adopt t
Read the rest
he same strategy, right?
-what's the best way to replace django templates with jinja2?
-for python 3, what is the alternative to PIL?
-as mentioned elsewhere, how do I do database migration when the models change. Especially, what are the different alternatives for doing the migration (django south seems too complicated -- can I just make sure the manage.py db schema and the actual db schema are the same as the docs suggest?)
-should I use store much of my model data in a json field so I don't have to deal with db migration? Any software packages or coding tips about this?
-how do I use SQL Alchemy with django? Issues with doing this (besides not getting a lot of django goodies).
-how do I configure django-social-auth ( https://github.com/omab/django-social-auth ) beyond the default setting (ie: the pipeline)
-what is a good web host for django. Answer: webfaction. How do I set up virtualenv on webfaction?
I'm not sure what this has to do with the focus of the book, Django has session support so I doubt a book about Django would fully cover re-writing one of its components. Django used to only be able to store nothing in the session cookie other than the ID so that part can definitely happen (new in Django 1.4 are Cookie Based Sessions that used signed cookies to store data in cookies, but it's something you have to turn on).
This is all fully documented, if you're curious you should read it.
https://docs.djangoproject.com/en/1.5/topics/http/sessions/
As for tying into OpenId or other similar systems, it's a piece of cake. There are numerous Django apps out there to accomplish it. I have used django-social-auth for a project and had no problems getting things running:
https://github.com/omab/django-social-auth
In Our Django Book is LaunchedIn one of my apps, which is highly targeted towards Enterprise IT types, we're using LinkedIn and Google exclusively.
In another app I'm writing, I'm only implementing Github oAuth (as it's closely tied in to Github).
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.
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.
I once had a Flickr-tools site (long-since shuttered), obviously, Flickr oAuth dominated that site.
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 oth
Read the rest
er 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.
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, https://github.com/omab/django-social-auth (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.
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.
django-social-auth https://github.com/omab/django-social-auth
It has very good docs http://django-social-auth.readthedocs.org/en/latest/index.ht... and supports more than just facebook so unless you have very good reasons to allow only login with facebook (excluding regular login with username and password) consider implementing others, like twitter, google, etc.
In Ask HN: Which authentication app you use in your django application?BrowserID support was just pushed. https://github.com/omab/django-social-auth/commit/4136ea49e5...
Edit: Link to changeset.
In Django Social AuthIt'd be great if this supported BrowserID.
Edit: Oh, hey, there's a bug filed for that: https://github.com/omab/django-social-auth/issues/228
In Django Social AuthHow did OpenID fail (it's widely used)? How is it complicated for the user?
Properly implemented, OpenID looks like this to the user:
http://springpadit.com/login
And something like this for the average developer:
https://github.com/omab/django-social-auth
In Introducing BrowserID: A better way to sign inDjango social authentication/authorization made simple. There's a demo located at http://social.matiasaguirre.net/
1 points · Open discussionHere are the Django solutions I've found:
* https://github.com/pennersr/django-allauth (at least seems to work out of the box, looks to be some of the Pinax account app integrated with a decent way of both logging in and connecting to additional accounts after logging in. Pretty good demo at http://jug.gl/)
* https://github.com/flashingpumpkin/django-socialregistration (basic functionality, note the many forks)
* https://github.com/agiliq/Django-Socialauth (outdated, note the many forks)
* https://github.com/dgouldin/django-socialite
* https://github.com/omab/django-social-auth
* https://github.com/kmike/django-registration-facebook-backen...
* https://github.com/tschellenbach/Django-facebook
In Rails has Omniauth. Django has... a ton of one-off, limited social auth apps?