-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instagram check produces a false positive if the user has disabled their profile (but kept the username) #94
Comments
Not entirely sure what the fix for this would be, as a disabled account and non existent account produce the same "error" (html response). The username check could attempt to populate the registration form, which does an async check for username availability (it would have to pickup on the "x" css element). Regards, |
@phunkfoo, is the problem only occurs from Instagram? btw, it's quite weird that they don't remove the account actually... |
@seeeturtle yes, only for instagram, as far as I can tell. I only noticed the behaviour described after I searched for a username I have - but have deactivated. Regards, |
@phunkfoo , can you tell me a username that has the problem? |
@seeeturtle search for "phunkfoo" on the app. The IG bit says it's available. Then try to register it under a new account and IG will tell you the username is taken). Issue here happens because: https://www.instagram.com/phunkfoo/ (user is attached to a registered account that's been deactivated); and Regards, |
I can't find the difference between the response of not existing usernames and removed usernames. Anyway, I found that the instagram check the username by using the graph api. Maybe we can just tell the users to notice that it may be wrong. @jayvdb, @manu-chroma , how do you think? |
Hi,
Instagram users can disable (but not delete) their accounts, while still retaining the username. In essence, if an account with the username "xyz" is created and then disabled (but not deleted), the check will show the username "xyz" as available, but the registration process will fail due to it already being in use.
Regards,
M
The text was updated successfully, but these errors were encountered: