Loading Profile...
How about support for OpenID in Satisfaction Unlimited?
I'd love to be able to point users at Satisfaction Unlimited but don't want to force them to create yet-another-account. Supporting OpenID on my site and on Satisfaction Unlimited would be great because I'd just tell my users "hey, head over here and start engaging".
Or am I just plain crazy?
Or am I just plain crazy?
I’m sad
11 people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answers from the company
-
Hi Earle, and all. We admit it has taken us a really long time -- we're a small team with a lot of product to build. However, we are genuinely working on it NOW. Thank you for your patience!
I’m confident it is next in the pipeline.
The company and 2 other people say
this answers the question
-
nice!
fwiw, OAuth took precedence over OpenID for our initial implementation (OAuth's already implemented!) but OpenID is following shortly behind...
The company says
this answers the question
-
i would actually say our approach is three-pronged, and we're going to do all three eventually.
first off is one you already experienced -- the "cupcake" posts. that's our one-time post feature, which allows you to post a new topic without actually getting an account, though we do require an email address. so a user coming from your site wouldn't actually need an account to get real utility out of our system. based on the name you posted this under, i'm guessing you're already familar with this feature. :)
down the line, the plan is to make is so that if you later sign up for an account with the same email address you used for your cupcake posts, it will bundle all your one-time posts together and re-ID them with your actual username, so that you don't lose the value you've accumulated across multiple posts when you, say, visit your dashboard. in the case above, once you created your user account, "cupcake1541" would have magically morphed into "kveton." we're working on that ASAP.
second is openID. it's something we want to do, both because it has real utility and because it's a cause we'd like to support. of course, not everybody "gets" openID, and it's still too technical a spec for normal humans (in many cases it makes logging in more, not less, cumbersome.) and while we have some nifty ideas for how to simplify the openID experience, we still think in some cases people will need a completely separate account, so...
third is an authentication token system, so that you can link a user account from your site with your section of our site. while this will still require two separate accounts, there will be a single join and then you can pass people right over from your site to ours.
openID and authentication will of course play nicely with each other. we want the whole login experience coming from another site to be easy and seamless, and we've been thinking about that since the very beginning. linking accounts is tricky, but we're committed to making the entire experience as painless as it can be given all the limitations we're facing.
honestly, most people just don't have to think about it, because who cares about logging in? nobody. you just want your answers. that's what we're here for.
I’m excited
The company and 3 other people say
this answers the question
-
Inappropriate?Umm ... you can blame me for this post ... Cupcake 1541 is my new pen name ... :-) -
Inappropriate?the general request--some way to avoid multiple logins--is fast becoming one of our top requests. We have at least two ways of accomplishing this, and we may ultimately do both because they serve slightly different purposes. Option 1 is to do what you suggest and implement open ID. We've always planned this, but we've been waiting to gauge user demand. This option seems particularly good in the case you mention, where the referring org is an openid provider themselves. As with so many technical solutions the biggest issues are how to implement it in a truly elegant way.
The other approach is an authentication token system, similar to how Flickr grants opt in access to referring applications. We'll be talking more about this later.
I’m thankful
1 person says
this answers the question
-
Inappropriate?i would actually say our approach is three-pronged, and we're going to do all three eventually.
first off is one you already experienced -- the "cupcake" posts. that's our one-time post feature, which allows you to post a new topic without actually getting an account, though we do require an email address. so a user coming from your site wouldn't actually need an account to get real utility out of our system. based on the name you posted this under, i'm guessing you're already familar with this feature. :)
down the line, the plan is to make is so that if you later sign up for an account with the same email address you used for your cupcake posts, it will bundle all your one-time posts together and re-ID them with your actual username, so that you don't lose the value you've accumulated across multiple posts when you, say, visit your dashboard. in the case above, once you created your user account, "cupcake1541" would have magically morphed into "kveton." we're working on that ASAP.
second is openID. it's something we want to do, both because it has real utility and because it's a cause we'd like to support. of course, not everybody "gets" openID, and it's still too technical a spec for normal humans (in many cases it makes logging in more, not less, cumbersome.) and while we have some nifty ideas for how to simplify the openID experience, we still think in some cases people will need a completely separate account, so...
third is an authentication token system, so that you can link a user account from your site with your section of our site. while this will still require two separate accounts, there will be a single join and then you can pass people right over from your site to ours.
openID and authentication will of course play nicely with each other. we want the whole login experience coming from another site to be easy and seamless, and we've been thinking about that since the very beginning. linking accounts is tricky, but we're committed to making the entire experience as painless as it can be given all the limitations we're facing.
honestly, most people just don't have to think about it, because who cares about logging in? nobody. you just want your answers. that's what we're here for.
I’m excited
The company and 3 other people say
this answers the question
-
Inappropriate?I'd just like to add that while we're not currently supporting openID, we absolutely share this mentality of not wanting to create "yet-another-account." We're trying other new ways of simplifying the registration process.
By creating a nifty hCard microformat profile importer we allow users to register using their existing hCard supporting profiles.
We have a lot of ideas around this and would love to hear yours. Maybe we should start a new conversation around this?
I’m excited
-
Inappropriate?Yeah, do it! Start a new topic to solicit input.
-
Inappropriate?The hCard importer didn't -quiiiite- work for me. No matter. When you do add OpenID, please add it in such a way that I can associate my existing OpenID with my existing Satisfaction ID.
2 people say
this answers the question
-
Inappropriate?apage43, how did it break? which one didn't work for you? let us know and we'll do what we can to fix it for the next person.
I’m curious
-
Inappropriate?@apage:
With regards to combining an OpenID with an existing account, I don't think I would have it any other way. I'm even angered that we haven't yet implemented attaching multiple emails to one account.
We're working on that too :)
I’m happy others share our vision
-
Inappropriate?Ooooo. This make me very happy that Satisfaction "gets it" re user signup. We are all inherently lazy and want to minimize such tasks. I can say that my experience with Spock is marred by the fact that my signup experience was fraught with HTTP 500 errors as well other badness.
Allowing people to tie responses to user names when they convert is a stroke of genius IMO.
I like openID but I'll wait and see how far that goes. Ultimately everyone should be able to own their identity and content.
One feature that I find useful is the grok your addressbook functionality that I think every social site should have. It's a quick way to build/rebuild a network.
I’m excited
-
Inappropriate?Ok, it's time for you guys to add support for OpenID and OAuth. Time's up!
I’m pthhbbbbb!
-
Inappropriate?done! scott's starting work on both this very week. seriously. he got started this weekend.
I’m openly identified and authenticated
1 person says
this answers the question
-
-
-
Inappropriate?we're in the middle of getting OpenID (and OAuth!) implemented, in line with our public API. all of which we plan to release Real Soon Now. Stay tuned!
I’m excited
-
-
Inappropriate?I like OpenID, but remembering the long address to my Technorati page isn't very convenient. What other ways are there to log in?
I’m not seeing the benefits yet.
-
Inappropriate?There are a lot of options... you can actually use your own domain if you want, using what's called "delegation"... or you can use other OpenID Providers like AOL, ClaimID, wordpress.com and so on.
Technorati URLs are pretty long, it's true. But since any URL you control could become your OpenID, it's up to you to choose which one to use!
I’m empathethic
2 people say
this answers the question
-
Inappropriate?WOW! ClaimID is great. I can't believe I haven't played with this before. Thanks for your help!
I’m satisfied
-
Inappropriate?WANT -
EMPLOYEE
EMPLOYEE
EMPLOYEE
EMPLOYEE
EMPLOYEE