hanzel's dashboard

Hi Michael,

There isn't currently, no. To do something like that you would probably need to develop your own system to store topics. You would have to do quite a lot of hacking on the codebase, but it would be doable.

Another option would be to post all topics created by anonymous users under a pre-determined account. Sort of an "Anonymous coward" account :) Something like that would probably be on the verge of breaking our terms of service, but it might be something that my bosses would let slide if you show that it won't be an avenue for abuse (spam, trolls, and the like). I don't know though, I tend to stay away from anything involving legalese or pre-emptive restriction because it tends to make me sick that the world has come to that :)

Either way, you are looking at a good deal of development work on the helpcenter codebase. At one point we had anonymous user accounts for GSFN, and they were more hassle than they were worth. Part of what differentiates us is the human touch, and anonymity at that level kills it. IMO.

-Scott

Not sure if this is covered under this header...but is there any way to make GetSatisfaction registration optional when using HelpCenter? e.g., we want our users to be able to post questions without necessarily having or being linked to a GS account (though of course, we'd love for them to get on eventually)

Also, do you know if there are any sites out there currently using OAuth for GetSatisfaction single sign on? Or sites that are using the API to host things like posting/replying to topics? We would like to implement something similar and could benefit from an example of a site currently doing the same thing.

Thanks!

James

Hi Scott,

Thanks for the response. That helps a lot.

Quick question: I understand that username/password is never collected or transmitted by the *consuming* site, but I assume that at some point the user would have to enter username/password on the *producing* site?

James

James,

I'll answer your questions in order.

I don't have any ready made code examples on how to do this: each language is different.

What needs to be passed into the various requests are defined be the OAuth spec: you can read about it at http://oauth.net/core/1.0/#anchor7

You don't pass along an email or a password to generate the token. It's a pretty involved process if you aren't familiar with it: I recommend the following article: http://www.hueniverse.com/hueniverse/...
and the other articles about OAuth on that blog to get a feel for what the end user experience is like and what would need to be implemented.

The special url is just a properly signed request to http://getsatisfaction.com/session/fr...

Hope that helps,
Scott

Hi there, I'm confused about how to generate the token. Is there an example of how to do this? What needs to be passed in the request? just email and password? Once the token is retrieved how is the special url generated? Is there a list of OAuth variables that need to be passed along?

Yeah,

If you are willing to store user access tokens in your database, your users can authorize access to the Get Satisfaction accounts that will allow you to pass them through to our site without having them login.

You can read about some ideas on how to implement this on your own site here: http://developers.getsatisfaction.com... under the section, "Logging in a user using OAuth".