231–240 of 279 posts
I find no problem with OpenID. There are many free OpenId providers out there, and if you really don't want to use one, you can create your own fairly easily.
I just came off of a project where we built the entire auth system on facebook. No other regi options - just facebook. I will never do that again. If that was to become the standard, facebook shot themselves in the foot with their crappy APIs anyhow (see http://news.ycombinator.com/item?id=1731427 ) And I have a facebook account, and I'm really hesitiant to like or authorize anything for fear of the author (or hacker…
Earlier quoted context omitted.
Lots and lots and lots of sites fail because they depend on jquery hosted by google.
Interesting, that makes their altruistic (CDN) hosting seem slightly more strategic.
It's also very frustrating for everyone behind the great firewall of China.
Earlier quoted context omitted.
Define "something good." You haven't given any reasons on why it sucks.
Something that lets me use my email address as my ID. I can remember my email address. I can't even remember which openID provider I used to sign up for StackOverflow, let alone how they expect me to form the URL that I use for my login. So once a month, when my cookie expires, I get to perform a forgot-password-like action, where I dig through my email to find my username, then try several combinations of it and cla…
I use my own page and use the OpenId delegate meta-tag to point to the domain that I also don't remember: http://openid.net/specs/openid-authentication-1_1.html#deleg...
This way you only have to remember your own URL like: http://openid.mydomain.com and the password that you've chosen.
Earlier quoted context omitted.
Email is better because you are not locked into using some third party website to log in. You can set up an email server of you own if you wanted to.
Sure - but that wasn't what he said. He said that requiring facebook makes him think that the website owner shouldn't be trusted with data. Which has nothing to do w/ lock-in on 3rd party websites. It has to do w/ the relative security competence of those who choose to use FB Connect vs. those who choose email.
Surely it's easier to write your own authentication system than plug in to Facebooks?
No. It's actually very hard (to do correctly). Especially if your cloud provider (AppEngine in my case) makes it even harder.
Earlier quoted context omitted.
Something that lets me use my email address as my ID. I can remember my email address. I can't even remember which openID provider I used to sign up for StackOverflow, let alone how they expect me to form the URL that I use for my login. So once a month, when my cookie expires, I get to perform a forgot-password-like action, where I dig through my email to find my username, then try several combinations of it and cla…
Just put a delegate on a web page URL you'll remember. Like on your personal website. I use my own page and use the OpenId delegate meta-tag to point to the domain that I also don't remember: http://openid.net/specs/openid-authentication-1_1.html#deleg... This way you only have to remember your own URL like: http://openid.mydomain.com and the password that you've chosen.
Sentences that start with the word "just" should describe something easy to do. Like, you know, using your existing email address as your unique ID.
We have two separate clients that spend big $$$ on AdSense driving new customer acquisition that used single fb connect for login. After the API issue last week both saw their 8+ LP scores dive down to 1! Lost commerce for both over the past few days equals multiple tens of thousands, still not seeing the scores recover.