convore.json/groups/django-social-auth/twitter-email/messages.json

[{"user_id": 31418, "stars": [], "topic_id": 46594, "date_created": 1318712188.977747, "message": "Hello guys, I went through the docs and I haven't seen a way how can I request an email address from twitter backend; is it possible?", "group_id": 5196, "id": 2355856}, {"user_id": 20656, "stars": [], "topic_id": 46594, "date_created": 1318713039.773561, "message": "You can't, Twitter doesn't supply the user email address.", "group_id": 5196, "id": 2355920}, {"user_id": 34431, "stars": [], "topic_id": 46594, "date_created": 1319384644.363709, "message": "I just noticed this. Surely it is a bad decision on Twitter's behalf to offer 3rd party oauth login without disclosing the email address? How are the 3rd party website supposed to verify that the user doesn't already have a different account with them (assuming they are not using django-socia-auth!)?", "group_id": 5196, "id": 2413581}, {"user_id": 20656, "stars": [], "topic_id": 46594, "date_created": 1319481950.003794, "message": "Any oauth/openid provider gives you a unique identifier for each user, that allows you to identify unique users, 3rd party sites should store it to check for uniqueness.", "group_id": 5196, "id": 2422573}]