3, 2, 1… Contacts!

contacts1.png

If you’ve spent any amount of time on social networking web sites, you’ve probably experienced a moment like this:

Hey, this site is pretty cool. Invite my friends? Okay. I know that my buddy Jimmy Pop will dig it, for sure. Let’s see, just enter your e-mail address. There’s the Submit button — Wait a second! Did I just spam everyone in my GMail???

Whether by accident or by design, many social networking sites have a confusing way of getting people to invite other people into the system. As we’ve been working on adding Contacts — other customers in the Get Satisfaction system who you may want to follow or refer to on a regular basis — we’ve made it our goal to avoid the pitfalls that many other sites have fallen into. We want to make sure you know what each “next step” in an invite process will be before you click that button.

So, give it a shot. Add some Contacts from your dashboard.

Tip: If you’re a Twitter or Flickr member, start by importing those. It’s lickety-split fast.

Feedback: We think we’ve gotten pretty close to what we envisioned when we started designing this new feature, but if you have any advice, kudos, or complaints, share them with us.

Web 2.0: Sharing Slides

Last week’s Web 2.0 conference here in San Francisco was stimulating. I know I learned a thing or three.

In case you missed it — or wouldn’t throw down the cash for entrance to the full convention — we’ve collected the slides from our two biggest presentations of the week.

First, here are the slides from Lane and Thor’s presentation, Customer Service is the New Marketing:

And here are the slides from Scott’s talk, The How of OAuth, about that scrappy up-and-coming OAuth protocol:

Thanks to everyone who showed up and asked all those great questions.

Plus, thanks to everyone who attended Cameron’s OAuth Hackathon on Saturday. We had a huge turnout, especially considering it was such a stunningly sunny Spring day. Thanks for spending it indoors with us!

OAuth Hackathon

Get Satisfaction is organizing a meet-up — next Saturday — to help app developers wrap their heads around and implement the OAuth protocol. If you haven’t heard of it, OAuth is how users can give access to their information on one application on a second app without sharing all of their identity. If you’ve ever used an app that requested permission to access your Flickr account you know what it’s all about. Get Satisfaction is excited to provide OAuth support in its API.

Maybe you’ll be fired up about OAuth after attending the Web 2.0 conference next week. Maybe you’ve been meaning to figure out OAuth for awhile now. Maybe you started an OAuth project but didn’t get very far. Either way you should join us.

Here are some reasons to add OAuth to your app:

  • You want to link to a third-party app (like Get Satisfaction!) but you don’t want your users to have to create a wholly new account. With OAuth you can pass-through their credentials for a seamless, single sign-in experience
  • You want your app to be able to access user accounts on third-party OAuth-enabled apps. Use OAuth if you want to give users access to their existing Get Satisfaction accounts and functionality from within your app.
  • You want to give third-party developers the same benefits we mention above. It will increase your accessibility in the broader ecosystem of other apps.

Cameron will be emceeing this hackathon, from 2 p.m. - 8 p.m., next Saturday, April 26th, and there’ll be numerous OAuth experts on hand to help you make quick work of your implementation. Since we don’t have a massive office here at Get Satisfaction (you’d probably also get distracted by our Rock Band set-up), the folks at Six Apart have generously donated their space for this event.

You can RSVP and find out all the details here.

Web 2.0 Conference: We’re Speaking

Web 2.0 is next week. We will be there. You bet we will. In fact, we’ve got a bunch of speaking engagements lined up. Come visit us as we expound on these topics:

Start-up funding: Thor speaks in a workshop setting with Rob Hayes (First Round Capital), Jeff Clavier (Softtech VC), and Ted Rheingold (Dogster/Catster) about getting early funding for your start-up venture. The official title: Starting Up: Strategies for Financing & Growing Your Web 2.0 Startup. Topics will include financing, marketing, team, revenue models, and managing all the other hats every startup entrepreneur needs to wear. Start it up on Tuesday! 9 a.m. (Moscone West 2022)

Data portability: Leslie will be talking about user interface and data portability. In an as-yet-untitled roundtable, the focus will be on hopping from one social network to another. What can we do to make that easier? How should these kinds of interfaces be designed so that users can clearly understand how all this passing-through and jumping over works? Get on that UI on Wednesday! 10:50 a.m.

Community Management: Amy will be whispering into the ears of trolls. Not the kind that you may have read about in fairy-tale books, but the more destructive kind who try to disrupt, grief, and kill online communites. Come learn some strategies for dealing with that guy on your Web site who seems to have a wealth of time on his hands and a whole lot of ire to share with the world. Trolls on Wednesday! 1:30 - 2:20 p.m. [Note: This one is part of Web 2.0pen — a free event (you can register for a free pass).]

Customer Service: Thor and Lane’s Customer Service is the New Marketing presentation is for those folks who are into fanatical devotion. No, not the religious kind; the kind that people feel toward their favorite companies and products. If your organization needs to get religion and fix your customer service problems, get thee to a seat early for this one. Customer Care Thursday! 2:40 - 3:30 p.m.

OAuth: Scott’s The How of OAuth will get you up and running with OAuth. What is it? How does it work? How do you get started? Scott shows you why it’s not the big wrestling match you might think, provided you take a simple, measured, Zen-like approach. OAuth on Friday! 2:40 - 3:30 p.m.

… More Web 2.0 news as it happens.

The Get Satisfaction API is here!

Our shiny, shiny API, previously announced and much-discussed and anticipated, is ready for the prime time! Check out the extensive documentation for it on our brand spankin’ new developer’s site, powered by our pals over at Mashery.

Our goal with the API is to expose every part of the Get Satisfaction service, so that companies and customers alike who have clever ideas about how to integrate, build on top of, and/or extend the Get Satisfaction service can just do that. All sorts of possibilities await: Recreate your company’s area in Get Satisfaction entirely on your own site. Or recreate Get Satisfaction for more than just one company — do it for a whole class of products and services, and prove your expertise across an entire category. Maybe you don’t like the way our posting or topic listing page works? Make your own! Dig in deep and integrate relevant topics right into your online product catalog, or mash our topics up with your already existing discussion or comment groups. Built a couple of widgets to show off your answers on your own blog. Or create some clever visualizations that help you better understand what your customers are saying (I hear Google can help with that.)

In other words, do whatever seems like it’ll be fun, interesting, stunning, and/or useful. And while you’re doing that, we’re going to keep working to make it better, faster, and easier to use our API. To that end, we’ve got a couple of things going on:

  • We’ve put together both Ruby and PHP libraries for the API, to help you get up and running quicker.
  • We’ve fully embraced OAuth as our third party identification protocol of choice, to ensure seamless, user-friendly, and secure account integration between Get Satisfaction and all the companies that choose to work with us. No need to create Yet Another Account to use Get Satisfaction — now you can pass your customers directly into our system and auto-create/link accounts together (with their permission, of course.) You can read more about how to work with our OAuth implementation, and we’ll be talking more about the benefits of OAuth right on this here blog in the next couple of days.
  • And just to be coy and teasing: we’ve got a few more API-related tricks up our sleeve in the coming weeks and months, so keep an eye out for those.

Of course, we’re ready to discuss all your API-related questions, problems, ideas, likes, and dislikes right here in Get Satisfaction. I may have said this before, but it bears repeating: We can’t wait to see what you come up with! So once your creation has made it out into the world, please be sure to let everybody know.

Close
E-mail It