Skip to main content

Some thoughts on social networking

I've been working on building a social networking site, but because of the angle we approached this (we sort of backed into it) it did not have many of the features of a "normal" social site. As we have developed the site, I've used more social networking services in order to study them and thought about some of the decisions we've made.

The essence of social networking is helping people keep up with what their social group is doing and sharing interesting things with them. It's not really about the content, the pictures, the classified, the video, the recipes. What keeps people coming back to the social network is curiosity about what their friends are doing. Or they are notified of some new content related to a friend's recent activity, photos from last night's great party or the new baby.

We gave ourself quite a task, since a core audience for our network consists of people who are very stubborn about getting online. Many do not even have or want an email address, let alone a website or a social network membership. We had to justify participation in the site through self-interest that was very different from the typical reasons people sign up for a social network. But I am beginning to think that the same principle applies, that the fundamental reason for belonging to a social network is keeping up with people. At least, it is what keeps people coming back.

The more public aspects, the posting of messages, the publishing of event information, these are all useful aspects of a social network, but they are more part of the "myspace" style network, which has a large public publishing (some might say exhibitionist) element compared to some of the "facebook" style sites, which are walled gardens of interaction.

The information that flows inside the social network is as important as the information that is accessible by the public. This is the rap on social networking, that much of the useful information user activity generates does not become part of the public web, which means others cannot learn from it, search it or preserve the conversation for future generations. However, using a "share" model, it may be possible to expose content to the public sphere when the user desires. So the information is by default within the walled garden of the network, but can easily be shared to another network or on the public web. These patterns are emerging on facebook and google reader's shared items.

The RSS reader is a private experience containing information that is an internal flow unavailable to the web. The syndication sphere is entirely separate from the web and opaque to web search, unless that content is already on the web. So the share function is essential to get that information back out into the public, or perhaps it was generated from an internal group working on some project with its own RSS feed, items of which could be shared with the public at the reader's discretion.

With the information generated within the social network, a person may share a link with their friends, one of whom may share it on their "page" to the public web. This is more a part of the keeping up with friends and sharing content with friends than it is putting something on your profile page for the world to see, whether it's the equivalent of a "high five" or a concert schedule, this is really external to the network and its social use.

A social network is about enabling friends to keep up with what each other is doing (social peripheral vision, it's been called) and share information with their friends. These are the two fundamental themes of the social network. This is why monetizing is so difficult. The only way to monetize this activity is if somehow the act of sharing information can create revenue or incoporate commerce.

What if when you share news about a music group with your friends, you get paid a small amount by the musical group, just like a Google Ad? This would monetize the social activity itself.

Comments

Popular posts from this blog

Minolta Lenses on a Four Thirds Camera

During the summer, I bought an Olympus E-510 digital single lens reflex camera. The 510 is a FourThirds camera and because of the of shallow flange of the 4/3 lens mount it is one of the most flexible cameras on the market when it comes to mounting legacy optics (lenses from traditional film SLRs). A 4/3 camera can mount "legacy optics" or lenses from several other manufacturers made before the DSLR era. Although unintended, this makes FourThirds a revolutionary mount. For the first time not only can a photographer mount lenses from different manufacturers who produce lenses to the "open" FourThirds standard, with inexpensive Chinese-made adapters lenses from nearly any manufacturer from the golden age of SLRs can be mounted as well. Third party adapters can be found for Olympus OM, Nikon, Pentax, Zeiss and Contax. The only one missing from the party was Minolta. I purchased an inexpensive OM to 4/3 adapter from ebay and mounted several OM lenses, a 50mm f/1.8, 50m...

Reading Tweets

I see a new kind of writing being created on Twitter, including hashtags, mixed into the text, in a variety of creative ways. In future, we should see a system that allows users to make these kind of connections, but without needing to include obscure computer-like commands in their text. I sometimes feel I'm reading a Linux command line or script when reading some tweets. Sometimes, it takes a moment to figure out what the tweet means.

Facilitating the Conversation

I was prompted by something Andrew Shafer of Reductive Labs said (on the FooCampers list, so I won't reproduce it here, since it was forwarded to me) about the quality of communication among software developers. He was talking about how communicating the overall design and intentions of the project is vital, so the developers are not left guessing about how the application will be used and what its architects think it should do. What is important is the existence of a conversation between the leaders of a project and the developers writing the code. This hits very close to home, because our farmfoody.or g project is essentially there to improve the flow of information between producers and consumers of food, to enable a conversation . It occurred to me the solution is to throw away the flash cards and bulleted design specifications and just facilitate the conversation. Why not use social networking tools for developers to communicate? (You can get a sense of another approach from ...