3 ms·
I think you will need to make a decision as to whether you are hoping to serve as a proxy login (you log into me with twitter ; i log into them on your behalf)
by gregcohn 13y ago
I think you will need to make a decision as to whether you are hoping to serve as a proxy login (you log into me with twitter ; i log into them on your behalf) or to have a separate standalone service that's clearly demarcated from the host publisher.
I believe you'll find the former is challenging. It would be against the TOS of most authentication providers to do this as an arm's-length intermediary. I think you could do it as the contracted agent of the publisher (which implies a white-label approach). See, for example, the way JanRain works.
The best examples of the latter I can think of are Disqus, Echo, et al. You might want to check them out.
- partisan 13y agoGreg, Thanks for the reply. I was thinking to have a standalone service that is clearly demarcated from the host publisher. I wouldn't store passwords, I would simply serve as an authenticator for websites that would use the service as an alternative to the standard oauth provider from twitter or facebook, etc. The issue is that I would probably have an app on their ecosystem to facilitate the process. BTW, brnr.me sounds like a great service.
- gregcohn 13y agothanks!