Raymond Penners

This scenario has been discussed before in https://github.com/pennersr/django-allauth/issues/191#issuecomment-13477334. I am not yet convinced that we need to "pollute" the signup flow by making it a hybrid signup-connect flow, especially given...

I am not sure I fully understand, but you can already fully manage social apps without having provider settings in your settings.py. You can even have multiple providers of the...

I am aware of this issue and have been pondering about it for some time now. Pre/postfixing all providers does not feel right. Most of the providers are not true...

For 0.22.0 the mo files have been updated, though I quite dislike having to do this manually and committing binaries to the git repo. I am keeping this ticket open...

There is no easy setting for this, yet, though it can be realized as follows: You should let `is_open_for_signup` on the account adapter always return `False`. The counterpart in the...

Even if you would go the social-only route, it typically still makes sense to store the user email address for user communication purposes. So, if you would architect things differently...

There is already basic AJAX support built into the existing allauth endpoints. For example, when doing an AJAX POST request to the password change form, you'll get a JSON response...

Please do provide feedback on what you all think is missing. As for a bit more background information: adding dedicated XHR/API endpoints is difficult to get right. For example, for...

Before taking any action I would first like to inventorise what scenario's need to be covered. See my comment above.

No news from this side. So far this issue is not really actionable. My callout above asking for concrete scenarios to be covered has not been answered...