4 ms·

I wouldn't consider that settling :-)

• brlewis 19y ago
  OK, here's my assessment: Clickpass and idselector both allow a "one click" login experience for return users. Both let you type in usernames for large OpenID providers to make things friendlier for people who don't want to type URLs. Clickpass also provides a uniform registration interface. This helps new users tie their OpenIDs to existing accounts, and/or register a new account reusing profile information from previous registrations. This is especially handy if you collect square profile photos. Idselector most likely does not do anything registration-related, although it potentially could using SREG. As a result it's much easier to implement. If you already support OpenID, just add some code to your login page and you're set. Clickpass requires some real development work. If the Clickpass login button doesn't already work on sites that haven't done full integration, look for Clickpass to come out with a "lite" version that just works like idselector. Look for JanRain to do more with registration in the future. I expect sites that use idselector will soon feel that that piece is sorely missing.
  • justindz 19y ago
    My goal is to allow the use of OpenID, to minimize as much as possible the DRY violation that is profiles (e.g. keep the minimum amount on my system, make whatever I use the most re-usable and source images, etc. from an already established and reusable location). So, it sounds like the best path is to either add Clickpass now or wait and see what someone like JanRain does. Making it, ultimately, a matter of style and timing? I use Disqus, so maybe Clickpass gets one extra vote. Thanks!