PDA

View Full Version : Implement RPXNow? (openid, google, facebook, etc)


psylenced
Sun 9th Aug '09, 10:04pm
After reading a few blogs i have become aware of http://rpxnow.com/

It is a paid service, but as far as i can tell, the standard free service should be fine for most people.

What it is, is a standard API that wraps many providers - openid, myspace, google, facebook, windows live, yahoo.

The API for RPX should never change, so as changes come through for any 3rd party provider they will be upgraded with no code changes needed on the forum side of things.

Free service offers 6 providers (that should handle all the main ones), profile data (name, email, birthday, d.o.b, profile pic) and 1 admin which should be fine for 99% of people. Only thing it doesnt offer is mapping.

This also off-loads development and changes from vbulletin to the rpx provider, so there wont need to be time wasted following up changes with all the providers.
Nick
Sun 9th Aug '09, 10:14pm
Hm, that looks very interesting. You may want to check this out though: http://www.vbulletin.com/forum/showthread.php?t=314946
psylenced
Sun 9th Aug '09, 11:26pm
Hm, that looks very interesting. You may want to check this out though: http://www.vbulletin.com/forum/showthread.php?t=314946

Yeh i had seen that. I think the reason IB wanted it as a 3rd party product and why VB hasnt picked it up, is due to the effort keeping up with all the changes made by various platforms.

This offloads that to a dedicated (basically outsourced) team so all VB needs to do is implement it once and forget about it. Will be zero cost once implemented. They could possibly even enter some sort of revenue sharing agreement with them and share the profits from referrals to the paid versions.
Simetrical
Mon 10th Aug '09, 9:24pm
What exactly does this provide that OpenID doesn't? It's tied to a single provider. If that provider goes out of business or decides to stop providing the service, it will become useless. Using an open standard would be greatly preferable.
Nick
Mon 10th Aug '09, 9:36pm
What exactly does this provide that OpenID doesn't? It's tied to a single provider. If that provider goes out of business or decides to stop providing the service, it will become useless. Using an open standard would be greatly preferable.
I guess it makes it easier to integrate into your site without needing custom coding done.
Simetrical
Tue 11th Aug '09, 8:22pm
A properly-done OpenID solution wouldn't need custom coding either.