On Fri, 17 Sep 2010 08:47:02 +0200, Michael Snoyman
Hi cafe, Hi,
Let me preface this by stating that this is purposely a half-baked idea, a straw man if you will. I'd like to hear what the community thinks about this.
I mentioned yesterday that I was planning on building haskellers.com. The first technicality I considered was how login should work. There are a few basic ideas:
* Username/password on the site. But who wants to deal with *another* password?
I don't really bother, I generate them and store them encrypted.
* Facebook/Twitter/Google: We get the users email address, but do we *really* want to force users to have one of those accounts?
No. However by nature Diaspora would become an option.
* OpenID. Fixes the extra password problem, but doesn't give us any extra information about the user (email address, etc).
I would go this way. Building a new cross-sites authentication system would a big loss of time. Then you're right one needs a place to store more information about the users, I see some options: - OpenID do provides with customizable profiles that could hold some information, I don't remember the details though. - If it is not enough, then having such a service for the community would be doable and independent of the authentication. This service could holds permissions for the different services around. Best regards, -- Nicolas Pouillard http://nicolaspouillard.fr