Django user model for 1.5

[gaqzi]

The changes to the user model for 1.5 will change things for us and as far as I've been able to discern we'll have to redo some quite important parts of friendface.

I was originally planning on converting friendface to 1.5 and use that for housewife but I'm starting to think we should probably discuss this a bit more before we do that. And just how we should design this to work as seamlessly as possible.

Some quick questions:

• Even if we can swap out Djangos standard user model, should we? Especially if we want to make it a small thing to install friendface. And how will that work out with slowstagram?
• Should we instead opt for adding a relationship to the standard user. And then ensure that we only got one Django user and several FacebookUsers and then have to scope them at use?
• What other kind of changes do we need?
• How do we support both 1.5 and <1.5 with these changes?

[kitsunde]

I've had the issue with multiple apps and multiple users brewing in my head for a while now. We probably must do a ForeignKey from FacebookUser to the User model.

The main issue would be discovering the facebook user for the current facebook application. See #18. This is a duplicate of #19 also probably.Maybe add a request.facebook_user that is lazy evaluated.