Clay Shirky's (as ever) excellent essay, "
A Group Is Its Own Worst Enemy," explains how online groups go bad and what can be done to rescue them from the start. It's tough to do justice to the first half of his piece in a summary, but his recommendations can be briefed:
1. Handles (nicknames, usernames, etc.) have to have meaning in the sense that they're reliably and visibly connected with a real person whose reputation can be monitored. Without keeping a handle on handles, trust within the group fails.
2. Reputation has to be attached so "good works get recognized."
There's an interesting pattern I'm seeing among the music-sharing group that operates between Tokyo and Hong Kong. They operate on a mailing list, which they set up for themselves. But when they're trading music, what they're doing is, they're FedExing one another 180-gig hard-drives. So you're getting .wav files and not MP3s, and you're getting them in bulk.
Now, you can imagine that such a system might be a target for organizations that would frown on this activity. So when you join that group, your user name is appended with the user name of the person who is your sponsor. You can't get in without your name being linked to someone else. You can see immediately the reputational effects going on there, just from linking two handles.
So in that system, you become a member in good standing when your sponsor link goes away and you're there on your own report. If, on the other hand, you defect, not only are you booted, but your sponsor is booted. There are lots and lots of lightweight ways to accept and work with the idea of member in good standing.
Like
Slashdot's karma system, for instance.
3. Users must be segmented in terms of authority deriving from their participation in the system.
It has to be hard to do at least some things on the system for some users, or the core group will not have the tools that they need to defend themselves.
Now, this pulls against the cardinal virtue of ease of use. But ease of use is wrong. Ease of use is the wrong way to look at the situation, because you've got the Necker cube flipped in the wrong direction. The user of social software is the group, not the individual.
4. Plan for scale in advance. "The value is inverse to the size of the group. And you have to find some way to protect the group within the context of those effects." Take the Live Journal approach of "soft forking," where average-size groups have 12 members and the median group membership is five, but each small group is connected with others through individual users' personal networks. Or take the IRC channel and mailing list approach, where "as the signal to noise ratio gets worse, people start to drop off, until it gets better, so people join, and so it gets worse." Or just make it hard to sign up, like MetaFilter: "When we start seeing effects of scale, we shut off the new user page. 'Someone mentions us in the press and how great we are? Bye!' "
That's a way of raising the bar, that's creating a threshold of participation. And anyone who bookmarks that page and says "You know, I really want to be in there; maybe I'll go back later," that's the kind of user MeFi wants to have.