One thing I really hate about sites is that you typically have to register and go through all the steps of activating a new account. When I look for something to buy, I usually prefer sites which have Google Checkout enabled so I don't have to re-enter all my information again.
Of course, you have to trust the service provider -- in this case Google -- with your private information. Never the less, there an inherent trust in existing providers that you already have given your information to.
But what about Mustfindit? Our early prototype had a login system which allowed account creation, activation, password recovery and profile management. With some extent, an OpenID system would have been a better choice where Mustfindit would have been an Id provider.
So how does this play into our site's feature set. Well, we prefer to use an OpenID provider and allow them to manage authorization. This allows anyone access to our site while we only have to manage a subset of the users's profile which is pertinent to our system.
Much simpler solution don't you think?
If you recall that we were trying to decide which framework to use, web2py has a very nice authorization class built into the framework. You enable an the authorization system and that's that. But you can extend the class so you can integrate with RPX. This should take the hassle out of signing up new contributors.
0 comments:
Post a Comment