Boo, give me OpenID back! Or at least don't do password reset via HTTP.
> Or at least don't do password reset via HTTP. Huh?
Use HTTPS for password reset, not (unencrypted) HTTP.
We're turning off Clickpass March 15. How to keep your HN account.
61–68 of 68 posts
Re: We're turning off Clickpass March 15. How to keep your HN account.
#62https link would be nice, unless I misunderstood what was happening there, my password went out in the clear.
https://news.ycombinator.com/changepw works just fine actually, even though pg apparently forgot to put the 's' in the link.
Re: We're turning off Clickpass March 15. How to keep your HN account.
#63Earlier quoted context omitted.
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.
> Other examples that all suck for this reason: Apple IDs. Windows Live ID. Jabber. Erm, to clarify, Jabber isn't an authentication system. It's a decentralized IM network, structured similarly to email. A user is identified by their username on a given host, just like email. It (sensibly, in my opinion) re-uses the same format for that, user@host (I don't think user!host would be quite as intuitive...). This does no…
>This does not mean a Jabber ID is an email address.
Though on many mail providers these days, it's the other way round that's true. A lot of people use GMail, but few realize that this means they also have a JID (Jabber ID) and can use XMPP, since Google opens their servers.
It's a shame, really. Google seriously missed a chance to kill all of the mess of a thousand and one IM providers (each with their own, proprietary protocol) and replace it with the open and partially decentralized XMPP protocol, which anybody can implement and run.
Re: We're turning off Clickpass March 15. How to keep your HN account.
#64Earlier quoted context omitted.
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.
I use throwaway email providers on most websites, like 10minutemail.com or fakeinbox.com. Works wonders against spam. My real email(s) are only used when it's really required.
Re: We're turning off Clickpass March 15. How to keep your HN account.
#65Something in line of clickpass is good. It saves people from making hundreds of accounts and same passwords for many sites.
Re: We're turning off Clickpass March 15. How to keep your HN account.
#66I 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.
It's a credit to your code Immad that it is still working.
Re: We're turning off Clickpass March 15. How to keep your HN account.
#67Immad's already weighed in on this but as the other Clickpass co-founder I also support this decision.
OAuth has definitely trumped OpenID as a protocol but turning off Clickpass shouldn't be seen as a reflection on either protocol and is simply removing a dependency on unsupported and remotely hosted code.
Immad did an incredible job of writing code that has run and run however since acquisition there is minimal and subsequently no support behind the codebase.
I would like to thank both PG and the users of Clickpass here who have been such ardent supporters of it over the years. We tried hard to make it attractive to developers and we received a lot of support for that - thank you.
Re: We're turning off Clickpass March 15. How to keep your HN account.
#68I 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.
It's a credit to your code Immad that it is still working.
[deleted]