SocialStartups.com

In the last 2 years, a few different sites have implemented some very successful social designs. I’ll lay out 5 social design patterns here and then follow up with case studies in subsequent posts. These apply to sites with user-generated content where the content is the primary object.

Public Timeline

I’m starting with the public timeline because, while it’s not the sexiest thing on this list, it’s critical for new users as a solution to the cold start problem. The public timeline is the first place new users will look for new content. It’s also how they will determine if they wish to join your community – the size, the tone, the cultural-norms, and the freshness of your community is easily communicated via the public timeline. And, of course, it’s also where new users can find other interesting users, which leads me to my next pattern.

Asymmetrical Follow

This has been written about before, so I won’t say much. Asymmetrical follow means I can follow the updates of a user without their permission. They, in turn, could follow me back but it’s not required. This allows for the kind of preferential attachment characteristic of scale-free networks, and it’s scale-free networks that are primed for viral propagation. When the goal is content distribution powered by network effects, it just doesn’t matter if you actually know the person or not. All that matters is if the person if a reliable source for interesting content. This is why social networks have failed to become anything more than social networks. Remember this graph from Brad Horowitz?

Only 1% of a community are content creators

Most people’s social networks aren’t large enough to contain more than a handful of super-star content creators. I believe the average Facebook account has 300 users. 1% of that is 3 – not enough to be a valuable source of content. If you think Dunbar’s number is a more accurate group size – which I do not with regard to online communities – then you’re only left with 1 or 2 people (1% of 150 = 1.5). Yes, you can argue that Facebook has done very well for itself living off of soap-opera like content – who is dating whom, who got drunk at what party, what was she wearing?!?) but there are natural limits to that growth. Their commenting feature will help drive page views, but there isn’t a whole lot of new value being created there.

Newsfeed

Nothing shocking about this. Now that your users have gone out and followed their friends and other interesting users, their homepage should now be the newsfeed that aggregates all of that content into one place. But it’s not sufficient just to include the stream of content. You need to also show who contributed that content (and, in the case of re-blogging, the other hands it passed through). Why? Because that’s how you can evaluate the people you are following (and, with re-blogging, discover new people to follow).

Re-blogging

I’m a huge re-blogging fan. It’s the engine that drives the content diffusion through the network. The concept is simple: if someone I’m following shares something interesting, I can easily push that same interesting piece of content out to everyone who is following me while providing proper attribution. Someone who follows me can do the same, and again, and again. This is really powerful, as the people who follow me are most likely not the same as the people I follow. Re-blogging provides a transport device for great interesting content to travel through connected components of the network (which are generally much larger than your immediate social network).

Social Proof

While judging the content someone shares is a decent proxy for evaluating whether or not to follow that person, social proof can help. Show how many followers the person has. Better yet, calculate their influence (like PageRank does for websites). Or, show how many favorites their posts have accrued or re-blogs their posts have had. It’s a quick and easy way for users to ascertain the reputation of a user in the context of your site.

Bonus: APIs and RSS

I promised five, but here’s an extra. Use APIs and RSS to amplify your power. Provide APIs so that others can build tools that extend your reach. Publish RSS feeds so that users can incorporate your interesting content into their existing routines. Make use of other companies’ APIs to publish your content out to them (like publishing to Twitter). It’s very difficult to create new habits, but it’s much easier to go where your users already are (Facebook, Twitter, Google Reader in my case).

Like I said at the start, I’ll be back soon with some commentary on how well (or not) various sites are implementing these ideas. Off the top of my head, I’m thinking about Blip.fm, bit.ly, and Soup.io. I’d love to talk about Etsy, but I feel like it wouldn’t be appropriate.

Om Malik wrote an interesting post about twitter pricing yesterday, but I think he’s a little off. I don’t blame him, considering his background is not computer science. And besides, it started a really interesting conversation. Before we start talking about Twitter pricing plans, we need to come to an agreement about what technically is hurting Twitter. Ideally, scaling issues should be orthogonal to your business plan; if you are successful, lots of people use your product, and that’s a good problem to have. Generally, you don’t want to tax your best users.

So on to the technology. Here’s the clue that we’ll start with:

Twitter is, fundamentally, a messaging system. Twitter was not architected as a messaging system, however. For expediency’s sake, Twitter was built with technologies and practices that are more appropriate to a content management system.

From Twitter’s post on architecture and the problems they are facing 

When I read “content management system”, I’m thinking “blogging platform”. My guess is that Twitter is built to be a massively multi-user blogging and blog reading system – every user gets a blog to publish posts with and a blog reader to aggregate the posts of their friends. Considering Evan Williams was the founder of Blogger, I think it’s pretty reasonable.

So if you think of it that way, then the obvious way to architect the system is publishing via RSS and aggregating via RSS. When you write a new tweet, your message gets stored in the database. (Yes, shoving all of that data into a database is a really difficult engineering problem in itself. Assuredly they will partition across multiple databases if they don’t already.) The massive pain comes in when pulling in what your friends’ tweets are. Let’s talk through how it works. Your twitter homepage is acting like an RSS reader, so first it will lookup all of the feeds it needs to check – all of the people you follow. Then, for every person you follow, an RSS feed will be read or generated. The resulting set of RSS feeds will be merged back together and sorted chronologically. The result is your Twitter homepage.

Notice here that this is what is called a “pull” or “poll” model – you are checking for new posts whether there are new posts or not. This can generate a ton of unnecessary load on servers and databases, not to mention network traffic costs. With the advent of Twitter applications, these applications are constantly polling Twitter to see if there is anything new to publish. Ping, ping, ping. All to see if there is something new afoot.

Which brings us around to pricing. It is not, as Om suggested, Scoble’s fault for having 25,000 people following him. The cost is not sending one of his messages 25,000 times. No, actually it’s Scoble’s fault for following 21,000 people and constantly checking for new tweets from those people. It’s also the fault of power users like him using applications that aggressively use the Twitter API to check for new tweets – most likely the same people who use those applications are following large numbers of people.

As with all scaling problems, the first idea is “cache more!”. And sure, you can cache the heavy Twitter producers. But Scoble isn’t following just the big twitter users – he’s following everyone he can, because that’s how he believes he can get an edge on news and trends. Can the long tail be cached? Doubtful – there are too many users who fall into that category. Can you charge those who follow more than, say, 1000 people? Maybe $10 a month for every thousand people you follow, with the first 1,000 free? That could work, but it’s risky. Would Scoble, in the face of paying $210 a month, permanently switch to Pownce? Or Friendfeed if they built a twitter clone? How many would follow?

The solution, of course, is to do exactly what Twitter says they are doing – switch to a different model and scale horizontally (“throw more machines at it”). I’m interested to see how it turns out for them.

First, read this.

The Opaque Value Problem (or, Why do people use Twitter?)

Thanks. This is important, and most people over the age of 25 don’t understand this. (Uh oh, I’m not bringing up the age question again, am I?)

Let’s start from a simple statement.

How compelling you find content is directly proportional to how relevant it is to you. The more relevant to you, the more you care.

OK, how about one more simple statment.

The people in your social network are relevant to you compared to those who are outside your social network. For more on that, read this.

Let’s mash the last two statements together.

Given that your social network is relevant to you, content generated from your social network is going to be compelling to you. The more content generated from your social network you get, the better.

It’s going to be boring nonsense to everyone else. So what.

Sites need to realize that if they want customers to visit at least once a day, there needs to be a lot of content available for consumption generated from their social network. This is what Facebook does. This is what Twitter does.

How well does your site integrate with my life?

Google Reader – David’s shared items

Since I’m subscribed to 30-some feeds and read hundreds of articles every day, I’ve decided to start sharing the articles that I think are worth reading with all of you. You can read the web (HTML) version of it by clicking the link above, or subscribe to my RSS feed here. It’s all about the kinds of topics my socialstartups.com blog is about – technology and community and startups. Enjoy!

Wow, never going back now. I used the Google Personalized home page forever (or, since it launched), but now that I’ve got so many blogs to keep up with, it was time to give Google Reader a chance. And you know what? Keyboard shortcuts are severely underrated. You just don’t know how great they are until you try it. Makes reading so much faster.