OpenID Is Why I Hate The Internet
teddziuba.com
teddziuba.com
1) Phishing? 10x Easier if everyone used Open ID. Masquerade as a provider, phish happy.
2) If someone has their password stolen...there goes every account they have. Albeit, without open id, this is sadly often the case anyway. (Not for me, but for most people.)
3) How hard is it, really, to register for a freaking website? Name, address, mailinator email. Done, no hassle.
IF Open ID is to be useful, it has to be able to log people in with extreme ease, otherwise the time-saved benefit of not entering these reg forms will be eradicated by the complexity of the system itself. And obviously...openid is NOT extremely easy. In fact, its quite the opposite. Even for a power user...unless you're signing up for many many many many accounts, its not helpful.
That's the translation of "maybe it will be awesome in five years". In web terms, five years is practically as far away as the heat death of the universe.
When we're trying to be polite, we geeks adopt the legendary phrasing techniques of the Japanese: We almost never use the word no. Instead we say "it's really quite difficult".
I think this guy would dislike e-mail if Facebook messaging had been invented before it. "Everyone with their own domains? That's too confusing. How will we ever explain it? Everyone except me is too dumb to understand!"
(As an aside, why is everyone so obsessed with making things "easy" for "users" they've never met? People aren't as dumb as you expect. Make it work for yourself first -- at least it will be good for one person that way. Your unresearched assumptions are harmful.)
You're right--they are about 10 times dumber. Have you been on Facebook or MySpace, or read YouTube comments lately?
Even taking the youtube commenters I suspect, most of them, would be able to grasp openid if it stood between them and the next ROFLMAO-able video.
I actually think that most people are not dumb ... they just behave that way because it makes them look cool, or because they lived in a cave all their lives and don't know any better.
Instead of being arrogant, treat them the same as you would a smart and educated individual, and I think you will have quite a few surprises.
In fact I rarely meet dumb people, and I'm not living in Silicon Valey, but in a third world country with a corrupted government, and a shameful school system.
Heck, that's how I signed up for Hacker News. You wouldn't be reading this wonderful prose right now if not for OpenID.
The problem is not the underlying mechanism but rather the way it's been presented on most sites. Remembering an openid url is counterintuitive for most people - you have to explain too much to all but the most technical users in order for them to know what's going on.
But now there has been some progress: Yahoo became an openid provider a while back, and they allow you to log in with their openid by simply entering "Yahoo.com," you don't even have to remember your openid URL.
I also used JanRain's ID Selector Javascript widget to make the signup form a little more intuitive:
So really I think openid is getting much better as it matures and its developer community tweaks it and the tools around it. If Google and Microsoft fully get on board (which they are promising) I think it will see pretty widespread adoption.
Those that know about OpenID can use their own providers, but those that don't care won't have to think about it; they'll just use the one I pick (which is no worse than trusting me with their made-up-on-the-spot credentials, which is what they'd be doing otherwise anyways.) If they start caring, they can make a new ID with a provider they choose--I fully allow for account URI changes; it's not that hard to implement. In fact, the whole OpenID set-up for me was two library calls (discounting the fact that I had to hack the library itself to add in Simple Registration support, so I could automatically set users' nicknames to their OpenID accounts' nicknames on each login. It's discountable because I submitted a patch, so no one else will have to worry about it.)
1. I don't have an account with this site. They say that if I have an account with (any of these other OpenID-supporting sites), though, that that one would work instead. Neato, but I don't use any of those, so:
2. I'll click on the register link here. Ah, here's a registration page. It doesn't have the site's logo on it, but they said that would happen--they've outsourced this part.
3. Registered. They gave me a link, and said "just treat it as your username." OK; I'll try to remember it, then. "It'll also work on all those other sites we mentioned, and more every day." Neato again; I might check some of those out.
4. I'm back on the site I started at, and I've already been logged in. They got my nickname right and everything.
(days pass)
5. "You've been logged out of the site due to inactivity." Oh, well, what was my username again? That link thing? Oh, here it is in the autocomplete.
6. Hey, it didn't ask me for my password! What the heck? I'm just logged in all of the sudden. I guess that's good, then.
(weeks pass)
7. "You've been", "inactivity", blah blah blah. Autocomplete.
8. Oh, I'm back on that site that did the registration. They're asking me for my password. Makes sense--they're the only ones that I told that particular detail. Put that in...
9. Ah, I'm back on track and logged in again. Nice.
They know how standard registration/login works. They have a browser that remembers passwords for them. They don't need OpenID.
Why is this confusing but e-mail isn't? If I want to send and receive e-mail, I have to find my own provider. I also have to remember this weird string, "me@example.com". THAT'S TOO HARD FOR THE AVERAGE USER!!11!
I tried using openID once. It directed me to google or yahoo or something to log in... So then I had to decide if it was really google or yahoo, or if it was some phishing site.
It's a terrible idea, which is sure to fail. There is no compelling reason for people to use it.
The only problem at this point is the URL username. To answer that, think about what, for example, gmail does: when you have a gmail.com address, you can drop that part and just use the username part of it. Likewise, I'd allow my users to strip off the domain part of whatever my "preferred provider" was, and just say that the "foreign IDs" basically need a "passport stamp" to get in--an attached domain name.
Still too confusing?
OpenID is just a weak idea that needs a LOT and LOT of pushing to make it accepted. Look at the iPhone - nobody pushes you to use it, you see it, like it and use it.
With OpenID people have to be forced to use it, because it's cumbersome and does not offer any clear advantage.
Like I've said earlier, the real auth solution is the one where you simply stick your USB stick into a machine, type a 4 letter pin and everything on that machine is authenticated till you take it out.
A weak concept pushed by technologists and people who want to give talks and earn money off this technology.
This is doable now with client side certificates. No body supports getting user creds from client site certs though. Would they be easier to understand than OpenID? Would they be easier to understand than username and passwords?
There are occasional glitches and annoyances (my pet peeve is that so many of the sites in the world don't actually support long passwords containing symbols). But you can fix the problems, because it's pretty obvious what 1password is doing and the whole thing is right there on your machine.
I'm sure there are similar programs for Windows, though I can't recommend one.
It's especially true in the case of Yahoo users. All they have to do is type in "yahoo.com" and they're in. Try and explain to me how it's easier to remember a bunch of usernames and passwords than "yahoo.com"
And remember: There are no overarching guidelines on usernames and passwords, so the whole "use the same one every time" almost works...but not quite. One site requires a 6-letter password, another requires 9 with one uppercase letter and a number, while another has no requirements whatsoever. That crap gets frustrating as hell for me and there are several sites that I have to re-request my password every freaking time I go.
As more and more big sites come on as providers, like MySpace and Yahoo, it will only get better. I agree that there are issues with presenting and explaining it to users, but the underlying premise is a good one.
Plus, since you never give a password, you don't have to worry about how they're storing it. Plain text in the database? passwords.txt file in the webroot? Doesn't matter because they don't have it.
This is what I do...except that every once in a while, I try creating an account on a new site and discover that someone else has taken "sethg". Or the site has some rules about what characters are mandatory/forbidden in a password, and I can't use my default password. Or the site stores passwords in the clear and gets hacked, and I have to remember everywhere I used that default password and go change the password.
In the grand scheme of things this is only a minor irritation, but whenever I go to a site that I only expect to visit once every six months and discover that I have to create yet another site-specific account, I think, "I wish they supported OpenID."
What I did was register my own domain (callna.me) and install Drupal 6 with the OpenID Provider module. Instant OpenID.
Anyway, his post makes him sound like an idiot. It's a good thing comments are turned off on his post.
So simple your grandma could do it eh?
All public OpenID providers should be using valid SSL certificates. For some reason that is terribly, terribly wrong, some providers don't (like https://alwaysknownas.com, https://openid4u.net and https://openid.es).
Sure, easy.
Better an early-adopter developer forum than GMail.
"instead of just the "qualified" people who used to get to publish their opinions in the print era" => upmodded for humour. Have you ever read anything in a newspaper owned by Conrad Black? Or anyone else, really? Print media may employ professional journalists.
But their "research" is flawed, they have a habit of regurgitating press releases from their advertisers and the political parties their owners support, and they pander to the prejudices of their readers.
Freedom of the press belongs to everyone who can afford a printing press. The internet is the cheapest, most unencumbered and uncensored printing press in history.
There is also a lack of best practices for consumers. When UI conventions are established and users become accustomed to them, it won't seem so confusing. Ideally, the creation of an OpenID associated "account" with a consumer would happen transparently the first time the OpenID is used, if it even needs to happen at all.
As for developers, OpenID may be more complicated to implement than conventional user/pass but it is also more uniform. Once there are mature libraries for common platforms, programmers will save a lot of time versus implementing user/pass from scratch. (I would not consider many current ones to be mature). Anyway, I'm not so sure OpenID is more complicated than a proper auth system with email verification and recovery.
"Unable to login with your OpenID provider: The remote name could not be resolved: 'blog.lexoft.eu'"
And after some time it starts working again. I suspect this is a DNS problem, but using OpenID means a dependence on an external system over which you have no control.
So I like the concept, but a site like StackOverflow should give the option of using normal user accounts as a fallback.
OpenID is cluttered. It takes longer to use it than it does to just reregister every single time. Even Clickpass doesn't speed things up. It's hailed as brilliant because it's open, but it's poorly implemented to a fault.
I argued in another thread that Facebook Connect was the technology to bet on. It's closed, but it actually offers a one-click login. The people in the comments thread, it seemed at the time, were evenly split into two camps: people who had used both and agreed, and people who disagreed because FConnect wasn't an open format.
Ted's swearing also comes across well to me (and, it would seem, to a lot of other people). I like that he gets worked up over this. It cuts out a lot of bullshit and sounds like he genuinely cares about the things he writes about.
That said, it works best when the receiving site uses the ClickPass button: without that, the login still takes longer than it ought to. With the button, it's as fast as Facebook Connect, but it has the downside that fewer users are using it, and that it offers no service BESIDE login. Facebook has an edge there, too, in that it offers functionality that users want to actively use, so FConnect is a logical extension rather than a brand-new concept.
Sure, some of his posts are extreme, but even those posts appeal to the same part of my brain that Valleywag appeals to.