Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

difference to django-socialregistration #560

Closed
johanneswilm opened this Issue Dec 31, 2012 · 2 comments

Comments

Projects
None yet
3 participants

It would be good if the documentation would specify what the difference to http://pypi.python.org/pypi/django-allauth and http://pypi.python.org/pypi/django-socialregistration is.

Currently it seems that one has to try each one of these out to understand the difference.

I just setup django-socialregistration but I realize now that it doesn't use the facebook user name when auto-creating an eccount name, nor does it use the facebook-registered email address. I understand that django-social-auth is able to do this?

Owner

omab commented Dec 31, 2012

@johanneswilm, a section comparing the available solutions would be good (at the moment I lack the time). About facebook username, yes, DSA tries to build username using the facebook user username if available, otherwise tries to use the name returned by their API. This happens with any available backend where some kind of username is returned (on some cases we use the email handle to build it).

@omab omab closed this Sep 19, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment