3 ms·
>Also, with openid I don't get to pick who I trust to do their job correctly. That's probably where we're disagreeing. This is precisely why I like OpenID: it
by Groxx 16y ago
>Also, with openid I don't get to pick who I trust to do their job correctly.
That's probably where we're disagreeing. This is precisely why I like OpenID: it takes logins out of your / site owners' hands, where it's always been, and where it's been abused to no end, and puts it in mine, where I can actually make a few decisions.
- awj 16y agoI can understand that opinion, but having the user's ability to access your site be in anyone else's hands is a scary thing. Especially when it can create even nastier customer service issues than a lost password. I'm not really sure what the solution here is, because as a developer I would like to see openid work. Right now it's just hard to argue for.
- Groxx 16y agoI honestly doubt there can be one. A system has to favor one or the other, as giving both equal access opens it to all possible abuse from both sides, rather than just one. As to the customer service issues, if they're having a problem on your site, they're having a problem on every site if they're using OpenID, because their ID has changed everywhere. It's far easier to diagnose the problem there, as it lies wholly (and provably) with their provider, and not with you. More of a headache for you, potentially, people are nuts when they don't get what they want. But at least you have a provable "out" and they have a single place to go for a solution (if there can be one).
- wvenable 16y agoWhat advantage does that provide? I'm not following the whole "takes logins out of site owners hands" logic. It seems like, yes, the site owner doesn't get to see your password but that's about it. On the otherhand, you're sharing a huge amount of information with your OpenID provider about who you are and where you go.
- Groxx 16y agoUnless your OpenID provider is you. Which it can be. Which is not possible with username+password. It's also about not having to trust the site owner to not misuse your password or release it or get hacked, which has happened before (though not to me). Loads of people use the same password on their email as they do on website-X, however stupid that may be. This is essentially giving website-X access to your entire identity, as nearly everything is keyed around your email account. Identity theft, here we come; already a tens-of-billions-of-dollars industry in USA alone. Instead, you choose who you want to trust with that information. Your OpenID provider. And you restrict your logins to 1, instead of N, making it far simpler to use a more secure login for even the most computer-inept.
- wvenable 16y ago> Unless your OpenID provider is you... which is not possible with username+password. Actually, with the username+password I'm always the provider. I can give whatever information I want. I don't disagree with what you say about website and identity -- but I think OpenID is the wrong solution to the problem. This should be embedded into the browser with strong cryptography between you and the website and no 3rd party should ever need to be involved. If I want to invent a new throw-away identity, it should be a simple click away. Being secure with a username+password is pretty much as easy or as difficult as using OpenID. If the goal is to secure the computer-inept, requiring them to associate a url with their identity is a failure even before you get through the rest of the process.