How will you let others know once this falls off the front page?
We're turning off Clickpass March 15. How to keep your HN account.
51–60 of 68 posts
Re: We're turning off Clickpass March 15. How to keep your HN account.
#52Thanks. Big win for user security on the Internet.
How so?
Re: We're turning off Clickpass March 15. How to keep your HN account.
#53The fact that Clickpass even exists made me realize openID was DOA. I spent a day implementing openID for the users of my website, because I realized, hey, what a cool idea, a URL can represent a single user on the internet, and that user can authenticate against it universally. The sad truth was that I could not expect a single one of my users to even understand what the hell was going on, because for most test open…
I always thought that the problem with openID is they didn't use email addresses instead of URLs. e.g. use john@example.com and require a certain url template for the endpoint e.g. example.com/openid/john That way I don't have to remember another identifier and we already trust at least part of our identity to our email provider. Not perhaps as open, but much more approachable as a user.
[deleted]
Re: We're turning off Clickpass March 15. How to keep your HN account.
#54I am one of the co-founders of Clickpass and I think this is a great move.
I wrote the HN code in about 2 days and I was learning lisp/arc so it was awful code (RTM did the openID part) and literally no one has touched Clickpass code for 2.5 years. The fact that it still works is always surprising to me :).
Also I think Oauth beat OpenID hands down.
Re: We're turning off Clickpass March 15. How to keep your HN account.
#55Earlier quoted context omitted.
Yes! Please please please implement BrowserId. This is the one authentication/login system that actually has a real fighting chance. We've implemented it for our site (next to FB login) and we are really happy with it.
Could you explain why? When I last looked, a crucial component wasn't specced, meaning you had to rely on Mozilla for part of the handshake. Have things change?
Why what? Why we are happy with it? It is easy to implement and the people creating it are smart. They've done a good job so far, I see no reason why it won't be successful in the future.
The browser integration will be amazing when its ready, but until then, it is the closest thing to FB auth without requiring FB or people to give up their friends list or other information they are concerned about.
I'm not sure what 'crucial component' you are talking about, but we are just using browserid.org.
Re: We're turning off Clickpass March 15. How to keep your HN account.
#56I am one of the co-founders of Clickpass and I think this is a great move. I wrote the HN code in about 2 days and I was learning lisp/arc so it was awful code (RTM did the openID part) and literally no one has touched Clickpass code for 2.5 years. The fact that it still works is always surprising to me :). Also I think Oauth beat OpenID hands down.
Did you mean "no one has touched the code in 2.5 years?" If so, then that is indeed, surprising.
And yes, OAuth did beat OpenID, but they're not really the same kind of thing.
Re: We're turning off Clickpass March 15. How to keep your HN account.
#57Are there any plans for BrowserID auth, perhaps?
Yes! Please please please implement BrowserId. This is the one authentication/login system that actually has a real fighting chance. We've implemented it for our site (next to FB login) and we are really happy with it.
How are your conversions?
I'm looking at implementing this for a new site...
Re: We're turning off Clickpass March 15. How to keep your HN account.
#58I am one of the co-founders of Clickpass and I think this is a great move. I wrote the HN code in about 2 days and I was learning lisp/arc so it was awful code (RTM did the openID part) and literally no one has touched Clickpass code for 2.5 years. The fact that it still works is always surprising to me :). Also I think Oauth beat OpenID hands down.
Did you mean "no one has touched the code in 2.5 years?" If so, then that is indeed, surprising. And yes, OAuth did beat OpenID, but they're not really the same kind of thing.
I know, but for all intents and purposes OAuth ended up being a super set of OpenID.
--- corrected years
Re: We're turning off Clickpass March 15. How to keep your HN account.
#59It might be a good idea to make this a "sticky post", and keep it in the top 10 until March 15 (or 16th). Maybe even automagically move it up the closer we get to March 15th.
Re: We're turning off Clickpass March 15. How to keep your HN account.
#60Earlier quoted context omitted.
I always thought that the problem with openID is they didn't use email addresses instead of URLs. e.g. use john@example.com and require a certain url template for the endpoint e.g. example.com/openid/john That way I don't have to remember another identifier and we already trust at least part of our identity to our email provider. Not perhaps as open, but much more approachable as a user.
Hate that idea. I don't want to have to share my email address, in fact that's a primary reason why I always use my open ID (which is unrelated) when possible. Providing email as a credential creates an implicit, if not explicit, invitation "Here, spam me." This is why I'm generally against using email as an identifier. Other examples that all suck for this reason: Apple IDs. Windows Live ID. Jabber.
I've got like 15 email addresses. I keep some of them private. There's no reason to give out your primary email address to every site that asks for it, just an email address.