convore.json/groups/rails/does-it-make-more-sense-to-store-third-party-account-information-on-the-user-or-authentication-model/messages.json

[{"user_id": 22410, "stars": [], "topic_id": 17123, "date_created": 1301890371.6605351, "message": "That's what I was leaning towards, but I'm unsure if all types of authentication would share the same fields. For instance, Twitter has a username, but others may not. Then you kind of start to get into STI...", "group_id": 447, "id": 520374}, {"user_id": 22410, "stars": [], "topic_id": 17123, "date_created": 1301890536.8851111, "message": "Hrm, yeah I suppose.", "group_id": 447, "id": 520383}, {"user_id": 27410, "stars": [], "topic_id": 17123, "date_created": 1301890445.1134591, "message": "Just because your record has a username field doesn't mean it has to be populated", "group_id": 447, "id": 520381}, {"user_id": 22410, "stars": [], "topic_id": 17123, "date_created": 1301889846.0155289, "message": "So for instance, if I'm using OmniAuth, and letting people link their twitter accounts, I store provider and uid on the Authentication, but would it make sense to store the twitter username there as well, or on the user?", "group_id": 447, "id": 520314}, {"user_id": 27410, "stars": [], "topic_id": 17123, "date_created": 1301890103.852525, "message": "I'd put all 3rd party auth info on the same record, but I'm an old-school OOP guy.", "group_id": 447, "id": 520353}]