Twitter and Facebook

When I went to Twitter today, it displayed a dialog

We were hoping you could help us make it easier for people to discover
their friends and colleagues on Twitter. Review your settings below to
make sure the people you care about can easily find you.

asking me to update my name, bio, location and email fields.

This suggests that both Twitter and Facebook are insecure about each other, seeing strengths in the other and weaknesses in their own service. Twitter feels threatened by Facebook's focus on a true circle of friends and colleagues. Facebook feels threatened by Twitter's capacity for marketing and building followers in public.

It suggests they may eventually become very similar in the features they offer, with Twitter integrating photos, video, circles of friends and Facebook making their content more public (which they are doing). Perhaps both sites will give users more control about who can see what content.

Labels: , , , ,

"Tyler Cowen: I don't think it's a useful description to say autistics are only focused on on thing, but I would say there's a lot of tasks you can give autistics, like picking out small details in locked patterns, or picking out different musical pitches, where autistics seem especially good at attention to small detail. So if you think of the web as giving us small bits, like a tweet or a blog post is shorter than a novel, if you think of that as the overall trend, like an iPod, a song is shorter than an album. It seems that we're now all living in a world where we manipulate small bits effectively, it doesn't mean any of us is just interested in one thing, but we manipulate these small bits to create bigger ideas that we're interested in, and those bigger ideas are synthetic, and I think it's another way in which we are using information technology to mirror or mimic capabilities of autistics without usually people knowing it. "

http://www.wrongplanet.net/article380.html

This is what I suspected when I envisioned Strands in the late 90s, before Twitter existed. That shortening the length of information might be another instance of the medium being the message, that it might broaden the number of people writing by lowering the barrier (less memory, organization required to write), and that there might be some way of using the "many small pieces loosely joined" to create some kind of better, large paradigm of writing than the book. And perhaps we could give to writing the same kind of flexibility we give to data in relational databases, for combining, recombining in novel ways, mining and analyzing.

What if we could create a Twitter Query Language? Enabling virtual documents consisting of projections and selections of real time status streams?

Labels: , , , , , , , , , , ,

A useful poke

I am trying to use Facebook more. I do not have a lot of use for the "poke" tool, which seems a bit childish. I wonder if it would be good to use the Poke method for content? What if you sent someone a book you thought they should read or you wanted to discuss. Sent a link to an ebook? Then they didn't reply. You might poke them about that post of content, not just generally?

Labels: , , ,

Mixing Conversation and Story

I realize now the real problem I have been working on and off for ten years now is 'conversation' versus 'story', but particularly applicable to journalism. In a way, conversation and story are like oil and water, they do not like to mix. Yet, stories are filled with dialog, or conversations, so why is that journalistic stories cannot contain dialog? Well, when it is an interview, they do. So what we need is a network tool that seamlessly integrates conversation (interview, written dialog, transcript) with story (narrative, reportage, essay and analysis). It looks like Google Wave has the closest technology to achieving this flexible confluence of conversation and story, even the potential for our conversations and stories to be both mobile and distributed. If every smart phone adopted Google Wave, and given that it works similar to email, which mobile computing already provides and is a robust and well-known commodity service, it promises quick adoption avoiding any centralized monopoly.

I envision the same tool could be used by a reporter to do an interview (dialog) and for personal self-expression (dialog, like Twitter, only sharing little bits of information, such as links). An interview consists of dialog, little snippets of information associated by place and time. This has the form of Twitter messages, but a chat application is much better for doing an interview than Twitter, so some new mechanism must be created to accommodate flexible use, moving between story and conversation, between longer and shorter length posts, between collaborative and authored posts.

Labels: , , , , ,

Is Your Life Poetry or Nihilism?

ReadWriteWeb asks this question. Poetry is reflective. Journalism also should be reflective (if all journalism were like C-SPAN, we would be better off for it). I am sure we could and perhaps will find ways to mine activity feeds for patterns and other useful information. It may find uses in many fields and places in life, perhaps even in medicine. But the real reason why there is so little reflection on the web is simply because the structures and tools of the web encourage shallow interaction, quick posts, short content, quick reads, quick writes. This is an area I've given some thought to and posted to the blog about it.

What is required is not some new gizmo for finding patterns in bits of trivial data, but tools that encourage people to slow down, to be reflective and create meaningful content. My idea presented here has been of a "quick-slow" system. This system would recognize the importance of brief, concise posts when things are happening (like you've just landed safely in an aircraft with the landing gear stuck and want to tell your friends or the world) and longer, slower, more reflective posts. This system would allow users to post concise messages like Twitter does, but those messages could be expanded on, by expanding the text or by associating longer texts with them. The idea is not entirely new. About ten years ago, I played with a prototype application trying to combine blog and wiki elements. Later, I discovered a more successful project to combine blog and wiki, and an application exists called a bliki.

What I propose is a system like Twitter, which retains its immediacy through a connection to text messaging (cell phones) and the "stream of concise posts" format, yet also provides a way to extend those posts in a meaningful way. Perhaps a user's followers could be allowed to edit the extended content, creating a community of editors and contributors.

What we really need is to encourage people who grew up "network native" to slow down and think before the write, or at the very least, if they have to capture an event or thought with quick, impressionist strokes, they or others should be able to return later after reflection to revise. A kind of "slow news" for journalism, akin to the slow foods movement, asking people to sit down and think a while before they write. This may be asking too much for journalism, but a quick-slow approach could support both quick impressions (what's new) and reflection (analysis). Moreover, this could support a collaborative approach that mixes reportage (the initial concise post, possibly with a picture) and analysis (the associated post, perhaps by an analyst).

The poet Basho revised his haiku many times over the years, sometimes refining the wording and other times he would write a new poem, depicting the same experience from a different aspect. This kind of revision and reflection should be encouraged and supported by technology. Haiku are an ideal model. Brief, concise, experiential, yet through juxtaposition and the many hours of careful writing, they convey higher truths.

I see a number of people writing on Twitter in haiku form, quite a few who are just arranging prose in haiku form and really have no understanding of haiku as an art form (poetry has to say something to be poetry, and say it in a way that affects us). I want to be clear, there is a new form of haiku practice emerging on Twitter, which is akin to the the impressionist movement in painting, where haiku are written on the spot and posted to Twitter from a cell phone. This is a new development in haiku, since most haiku are written down long after the poet has left the place of experience (not always, Basho sometimes wrote haiku and left them behind, but nearly all the haiku that reach us were probably revised many times long after he had visited the location). It bears watching.

Labels: , , , , ,

Where are we going?

The issue of whether people should pay for forums or not came up on dpreview. With the current economy, I expect how to pay the bills will be a growing question for many web services.

The problem is with forums there is perfect competition. Anyone can setup a forum and run it for next to nothing. If one forum decides to charge a fee, the users can flee to another forum. The only reason they might stay is because of the audience. For example, photographers pay for to host their photographs on Flickr primarily because it provides a rich audience of people who love to look at still photographs. Flickr is the Life and Look magazine of our time, it is the revival of the great picture magazines, not because of its technology (that helped orient the site in the right direction to succeed, just look at the abject failure of Picasa to be social---too little too late). Flickr just happened to be where most people who like to look at pictures gathered, mostly because of its blog-like streams of every changing pictures and social tools. It is easier to pay a small fee to use Flickr (perhaps even to "read" it) than it would be to overcome the "capital" costs of changing sites. Flickr users have a lot invested in Flickr and it might just cost less to stay and pay than to move elsewhere. Besides, there is no where else to move. The closest thing I could see to Flickr would be for every photographer to put up their own photo blog software and then join photoblogs.org, which would become the "magazine" and "social hub." This is a distributed vision of photo sharing online. I used to wonder which would be successful. But it really was simple, Flickr did it all for you, some for free, a little more for pay, well worth it to promote your photography.

Despite the somewhat juvenile and absurd environment of Flickr with regard to art photography (you know, the dozens of people giving out "Great Photograph" awards to pedestrian, derivative and mediocre images mostly to promote themselves or because they are too young to know what a derivative image is), it is useful to professional photographers and art photographers because Flickr is where the eyeballs are. It attracts people who still love still photography, which in this age of video, is a bit of a miracle that anyone takes an interest in photography. However, photographs can make the world sit still long enough for people to pay attention, and that is a very similar experience to poetry, which at least in part, is there to draw attention to things. I've heard from professional photographers they get an order of magnitude more requests or work through Flickr than through one of the professional portfolio sites.

One reason, perhaps the principal one, Henri Cartier Bresson and other great photographers became well known, was through their images being published in the great picture magazines. When television came along, the picture magazines went into decline. Photojournalism began its long decline at this time, for the simple reason people could learn about their world visually through television, a more attention grabbing (the barrier to entry for television was lower, you didn't have to be intelligent to watch it, a good example where low barrier of entry is destructive to society) and free medium. Without the picture magazines it was no longer possible for a photographer of acknowledged artistic merit to become known and their images have significance in society. The audience was gone. Flickr reestablishes this audience.

So the question still stands. Will people in the future pay for their online content. Pay to create it. Pay to consume it. What is happening now? People are already paying to create content. They pay for a Flickr account with better tools. They pay for services to create graphics, three dee art, property in virtual communities. A few sites charge for reading content, but not many. But given human history and the recent past, when most content was paid for, in newspapers, books and magazines (except for tv), it seems reasonable to assume the free ride will be over someday.

There may be a tipping point when a non-pay site is no longer competitive. When most good content has gone to pay sites and the community of interest for that content willing to pay is consuming all they can (this is what happens with books and magazines today), the other sources will be driven out in a kind of perfect competition. The free sites will be filled with garbage and what passes for content on local cable access.

The network is not the old traditional world of libraries and publishers. It will be different. Project Gutenberg. Open source projects. The collections of enthusiasts sick and tired of the crap shoveled out by the traditional content and software businesses have taken it on their own to produce quality products where the marketplace would not or could not. This is an order of magnitude different than the pre-networked world, where people could not work together, providing little bits of effort or expertise to collaboratively create a cultural artifact. This is entirely new and we don't know where its going.

As an aside, the idea of tipping or donation comes up. Frustrated with no way to fund my original website, I considered taking a modern high tech variation on the PBS approach. I considered (in the 1990s) creating a content management system where each article would have a countdown timer displayed like a reverse donation thermometer. If you didn't contribute something to the article, it would count down, when it reached zero, the page would be pulled from the site. Of course, the ability to cache networked content presents a threat to such schemes, the wayback machine can regurgitate considerable missing content and so can the Google search cache. What about caching? If the Wikipedia were to dry up funding and blow away today, would its content still remain available in a myriad of niches around the network? On people's computers, disks, servers here and there, in caches? Would it evolve another life in a peer to peer environment? Will all information become distributed over billions of cell phones and have no location at all?

Labels: , , , , , , , , , , ,

Twitter is a 'starfish' enabler

Twitter is a 'starfish' enabler. It's what makes Twitter powerful and empowers those who use Twitter. It puts individuals at the center of the star.

Twitter friends (followers) are more like information flows you choose, organizing the flow of information for yourself and others, curating, editing, creating than other social network friends, which are more passive, something you collect or at most create a space to explore. This is because friends/followers bring content to you automatically. It is the flows of information resulting from following that make Twitter different from other social networks.

I didn't know much about Twitter when we started designing Farmfoody.org and thought it was something to do with short text messages on cell phones. I am currently integrating Twitter into farmfoody.org, after having considered a Facebook social feed model and finding it overly complex and confusing. We need as low a barrier to participation as possible. Farmers don't have time for complex systems, blogging, social feeds with posts and comments and threads and six dfferent types of publishing and bold and italic.

Neither do people standing at a farm stand with a bag of white corn tucked in their arm have time for complexity. It turns out that the social bulletin system we were envisioning two years ago exactly describes the information flows in Twitter. The way your friends (followers) tweets (messages) aggregate on the Twitter homepage is identical to how we envisioned messages from our users collecting on the user's profile page. In our bulletin system, all the friends of a user receive a bulletin, similar to the "homepage" on Twitter, creating an information flow. The only difference is bulletins are like craigslist ads and expire. That original requirement for bulletings to operate as classified ads with an expiration date, similar to craigslist, held us back. I should have looked into Twitter integration then, since we would not have needed to develop one of our own.

Labels: , , , , , ,

User Curation of the Archive

We need to enable people to curate collections. This means blogging the contents of an archive, which can be as simple as a blogger selecting certain items (by surrogate, typically a picture but also 3D rotatable image or video) and posting them to the blog along with any caption available through the collection's online database. They don't have to say anything original to be useful. The basic requirement is that archives places their collections online, giving access to potential curators outside the archive. Curating is anything a user does to create context for the cultural artifact, commenting, annotating, writing that contextualizes the artifact (like wiki pages).

User curation of the archive helps people feel connected with the archive and its contents. Involving non-academics in the archives is important for the continued existence of an instituation and the collection, the value of which exists partly in the memories of people and in the objects themselves. I learned from genealogy that people only preserve what they care about, and that people care about things when they have meaning, and stories give artifacts meaning.

The context becomes a bigger and bigger net as it grows, bringing in more people from search engines. The effect of this net can be powerful, as I learned soon after getting on the web in 1995. I put a collection of family photographs from the middle 19th century online and within a few months several relatives of the people in the photographs had found them and made contact with me. After over 120 years of separation. This was when the web was very small, the users a very small percentage of the population. My idea to cast a net with the pictures and captions had brought in the catch I desired, helping to identify individuals in the images and reconstruct the family history, both photographic and genealogical.

I was intrigued by a project Social Media Classroom. It shares features with ones we envision for Folkstreams, as a platform for creating access to archives, but we also recognize that our site is mostly used in the classroom and that features of our site are shared with features of a classroom, such as the "contexts" accompanying our films, including transcripts.

Archives will, through online access, become an integral extension of the classroom. There will be less of a distinction between archives and classroom (and the public).

Labels: , , , , , , , ,

Content is the person

In discussions about farmfoody.org, the idea came up that recipes represent people in a way similar to the way avatars represent people, only much richer because they contain search engine friendly content. The recipe becomes a way for people to explore farms by navigating to the profile the recipes belongs to, then exploring the connections between users (producers and consumers who are friends).

Content is the person. I think we will see more of this as social media continues to expand an evolve. This can be seen, again on Twitter, where the person is represented by the content. When you go to a person's Twitter page, you see mainly their content. The "profile" is in the background. This allows Twitter to prominently display information about the content stream, because they do not have to deal with ten different kinds of content under ten different categories. Tweet streams have following friends, followers and the number of updates counted. If there were ten types of content on the page, if each time personal information was updated, what would constitute an update? It is clear updates mean the number of posts. Following, followers, post stats. That's it. Clear and concise.

Twitter succeeds by not being all things. It is a tool. Putting the profile in the background the content on the page. We can speak of a "Twitter page" because we know what is on it, unlike a Facebook page, which has almost anything on it. People know what you mean when you say "go to my Twitter page."

Our thinking about the direction farmfoody's features should go in are being directed by these concerns.

Labels: , ,

Thoughts on Twitter

I've been thinking about why Twitter is successful. And why some other services that attempted to compete with Twitter by offering "improved" features, like Jaiku, were not. Twitter had the first mover advantage. In the last month or so the buzz about Twitter has spread to average people through use on cable television networks and by cases where people reported on news events through Twitter by cell phone. Those are well and good, but there are other reasons for Twitter's success.

One is the simplicity of its presentation. The real estate devoted to profile and "friends" or user to user relationships is compact. The profile is brief and concise. The friends (following) and followers are represented by badge-like elements showing the number of following and follower users, with the numbers linked to listings. The followers are displayed as compactly as possible, represented by tiny icons arranged in rows and columns. The various kinds of posts are filtered by clicking a navigation menu item in the sidebar.

Twitter reverses the idea of a profile. The content is the profile and the profile becomes background to the content. When someone visits a person's Twitter page, they want to read the latest posts. The user goes straight to the posts. Most sites make you go to a profile and then to the content. If they like the content and want to know something more about who is posting, they can look at the little profile box containing the name and brief bio or click the link to visit their website. This difference contributes significantly to the usability and attractiveness of the site compared to other social networking sites. Twitter is a tool, not a "Swiss army knife" like Facebook, so it can take this approach. It should be a lesson to any designer or developer, even of more complex, layered sites.

The typical jumble of posts in the Twitter message stream explains why the developers of competing sites saw room for improvement. When replies enter into the message stream, it becomes a single-threaded discussion. It seems reasonable to let users reply directly to a message, creating a threaded discussion. Twitter might look similar to Facebook's Wall, where certain posts may have comments posted to them, creating a limited kind of threaded discussion. I believe this misunderstands how people use Twitter and why they use it. If Twitter users were looking for a simple, online threaded discussion forum, there are plenty of free microforum services to be found.

I believe Twitter users do not want a threaded discussion because they value the immediacy of tweets. There may be a way to capture conversations going between cell phone users in an intuitive and simple way, but I'm not sure what that is. Activity posts, like "What is Steve doing now?" are unlikely to elicit conversation, but as I've seen on Facebook, they sometimes do burst into conversation. I believe friends use the posting of completely uninteresting and unimportant information about their activities as a way to touch base, through a brief conversation. It's like talking about the weather. It may be possible, if the interface is sufficiently transparent, to support threaded discussions. Facebook does a good job implementing the thread as a collapsible series of posts below the post.

One thing in passing, it is clever how Twitter enables linking to other user's Twitter pages through a Wiki-like notation for Twitter-name on replies (using the @ symbol, @twittername). It helps solidify the username as not just a name used for authentication, but as a symbol representing a person. In a way, wikis have had this from the beginning, since it was traditional to create a page using your own name, which could be linked to in "talk page" discussions, and the like.

Labels: , ,

Friendship Rot

I may not be the first, but I have noticed something on social networks that hadn't occurred to me, although it should have, if we have link rot, why not rot in the relationships between friends? I've noticed on our farmfoody.org site there are some lapsed users, since their email addresses are bouncing. It occurred to me that they still have friends but no longer participate in the site. These are ghost relationships suffering from what could be called friendship rot. I suppose Facebook must have millions of people who no longer participate but have accounts and friends. It must have a terrible friendship rot problem. I suppose this form of relationship rot extends to LinkedIn and other sites that depend on navigating networks of relationships between people.

Labels: , ,

Blogging the Archives

A vital interest of mine is access to archives. I've been interested in the possibilities inherent in the web and network for increasing access to archives and enabling a greater number of non-academics to browse, organize and surface archive holdings. One of the most significant ways of exposing the holdings of an archives is blogging the contents.

We really haven't got there yet, but I've noticed a small trend, which I hope signifies the beginning of exponential growth, of people blogging artifacts. I do not remember the first site I came across where a blogger was posting pictures of artifacts, usually photographs from an online catalog of a museum, but here are some recent finds.

Illustration Art

All Edges Gilt

If we could just get every artifact in the world's museums and archives photographed or scanned and online, give the tools to blog the contents to millions of ordinary people interested in telling the stories of these cultural objects, think of how rich that would be. I don't know if people will do this, but I do know that ordinary people have a lot to contribute. Academics cannot know everything, they are an isolated individual, no matter how expert they are, and there is a very Long Tail out there of family members, amateur historians, hobbyists and who knows who that know something about cultural and historic artifacts. Maybe they will be willing to contribute. It will likely be only two percent, like Wikipedia authors, but that small percentage can do a lot of good.

As an aside, author and developer Liam Quin has a site, fromoldbooks.org which has great potential to provide fodder for bloggers. The interface to this digital archive of old book scans is easier to use and better than ones I've seen institutions deploy.

I wonder, also, if this phenomena is not somehow similar to the Cinematheque, not just an archive, but concerned that people actually view or interact with the artifacts.

Update: Shorpy is a commercial site, which shows  how successful blogging the archives can be. The site appears to have developed a following, with, I imagine, readers checking in each day to see what new photographs are posted. The blogger acts as curator by selecting images that will be of interest to the readers. Arranging them into albums, possibly by narrative (using Tabloo would be a good way to achieve this).

This fits exactly with the idea of people being able to easily find images of their local area in the past and the idea of "blogging the archives" at its most simplest and effective. The power of simply posting images and their captions, without any commentary, is surprising. It is encouraging to see people are interested and willing to participate in the interpreation and "unpuzzling" of old photographs. One of the pleasures of old photographs is rediscovering what lies behind the mysteries the images present.

Labels: , , , , , , , , , , , , , , , , ,

Why Tag Clouds are Beating a Dead Horse

Tag clouds are dead. I don't want to mince words. I've been waiting for a long time for someone to say so, to let everyone see the elephant in the living room. What interests me is why tag clouds are dead.

About ten years ago I was working on a prototype web application. It never saw the light of day. But it was called Strands and consisted of a wiki-like content management system that allowed anyone (it was based on SoftSecurity) to create pages, to post and edit content. Any author could include single keywords in the text. These would be automatically scooped up and entered into an index. You could display the posts associated with (containing) any keyword listed on a page like search results. The idea was that content could be navigated in any number of ways according to keywords added by users. It's wasn't social. It didn't know the user who contributed the keyword. The idea was to destroy hierarchy and create a user centered order to information, something close to the folksonomy (but not quite because it didn't care about who submitted a keyword). One version did not allow linking between pages, no "wikiword" links, the idea being that all navigation was by keyword links, either in content or on the "strand" pages listing all content belonging to a keyword.

One of the other ways of navigating considered was by popularity of keyword. The system could generate a list of keywords based on how many posts contained or were associated with them. You may start to find the elements of this system familiar. "Strands" are posts listed by tag. Keywords are tags. Navigating by popular keywords is a tag cloud. The ideas for this system partly developed out of work I'd seen on the web where posts were ordered by single keyword. The other reason was I have a terrible time categorizing anything, I can't decide which category something could go in. I am incredibly bad at and hate categorizing anything, so I decided the wiki element would let visitors to my site categorize my junk for me.

If this were not a blog, I'd spare you all this personal history, but it does show you why I am interested in the question of why tag clouds suck.

When I visit a website with a tag cloud, I tend to pay close attention to it. I noticed that I never bothered clicking on them, never used them. When I thought about why, one of the things I noticed was that nearly every tag cloud consisted of a number of large tags I could count on my hand, and the rest were undifferntiated in size. One of the solutions that came to mind was displaying tags by popularity on a logarithmic scale, which could help increase the difference between the less popular tags. I'm not that great at math, so I would need to leave it to someone else to work this out. But the idea is to create greater differentiation visually among the less differentiated tags.

The other problem with this is there are only so many font sizes that are easily usable on the web. This worsens the differentiation problem.

The other concern I had devevloping the keyword based application was that chaos would ensue. People tend to prefer order. Would it help or hurt for people to be navigating by tag? Tags don't always apply to the subject. Their strength is freedom, freedom from controlled vocabularies and rigid meanings, but without those restrictions tag-chaos can reign. Wikis always had a kind of randomness to them and so do tag structured and navigated content.

I almost never click on tags in Wordpress blogs for this reason. It usually produces a result that widens not narrows my search. Nielson observed that clicking on a link has a penalty, and the trouble with tags is they have an uncertantity penalty.

The closest I've ever seen to a realization of the keyword based navigation idea is a photo gallery developed by Alex Wilson some years ago. You can see it still in operation here. It's a great idea and an excellent implementation, I don't know why I didn't go ahead with my own version instead of abandoning it (doubly, since the eventual goal was for organizing photographs). It makes the homepage a tag cloud and each detail page with a photograph displays a vertical row of thumbnails to photographs linked by tags, which is very similar to the way the Strands pages listed posts according to tag (like Flickr pages with the tags next to the image). Alex recently switched to a standard gallery system for this exact reason, that visitors and customers apparently found the tag-navigated album confusing.

I love tags. I use them like I feel they were supposed to be in this blog, I just write any significant word that comes into my head about the subject. I don't care that they create long lists of tags, since I only use them as a memory aid. They are terrible for people navigating the site and categories would probably be better. Tags aid memory, they aid discovery and exploration, but I'm uncertain that they are good finding aids.

I'm sure others have observed this before, but I've kept quiet about it, so I may be late the party, but still, it's a useful discussion, to dissect why tags ultimately fail to live up to the (strange to me) hype they received. Every new web technology seems to be annoucned like the second coming.

So, yes, tag clouds are beating a dead horse. Even the little sets of tags next to blog posts don't really do much for me, not even on my own site, or they don't seem to do much for visitors in my view.

The other thing that tortured me developing the keyword based navigation was whether to allow spaces in keywords, which would prevent combining keywords like chicken+soup and create confusion (sepearte keyword threads of navigation) between "farmers market" and "farmers_market." I worried a bit about misspellings, but not too much since I didn't like controlled vocabularies.

References: Tag Clouds_Rip and ZigTag supposed to solve these problems.

Labels: , , , , , , ,

Transforming Conversations to Knowledge

This problem of how to transition ephemeral, but timely, information found in forums, Q and A sessions, all the forum-like forms on the network from Usenet to Twitter is one that fascinates me. I've thought about this for a long time without really coming up with any good mechanism for capturing the knowledge and experience of the forum, the group, from scattered individual, unrefined forms, to coherent, refined forms maintained by the community. I think that the idea of automatically transitioning content created by an individual into community property is a great idea. It may meet with some resistance from individuals. But I think it is a good solution to this problem, since anyone can start a conversation that does not just spin out into the oblivion of old forum posts, but can become a seed that grows into a well maintained, coherent, concise source of information.

Where does my interest in this issue come from?

As soon as I got my first website up and running, I wanted an email discussion group. It wasn't long until I was using Smartlist to maintain my own email discussion list. The discussions provided a wealth of information that was otherwise lost or scattered among messages---high signal to noise. One of my tasks was to glean the best information from the list and edit it to create a concise summary of the conclusions drawn in the conversation, which went into a single web page.

While working as a tech support person about ten years ago, it was my practice to glean solutions from our customer forums and distill them into concise answers I could repeat to future customers who experienced the same problem.

I thought there must be some way to automate or smooth this process of collecting the knowledge contained in conversations into a concise article form. It would be necessary to create some kind of bridge from forum to wiki. I thought about this on and off over the years, and tried creating a few tools to help with the processing of forum threads into articles, but until I stumbled across this idea of automatic promotion from individual post to wiki page, I could not see a way to do this that people would actually use.

It really seems this would work well with the quick-slow rhythm of a bliki, to automatically promote "blog" posts to "wiki pages" according to some criteria. I'll have to think about this some more.

In any event, there is another mechanism for easily capturing knowledge from users. We are seeing entire sites developed around a question, like Facebook's "What are you doing now?" or Yammer's "What are you working on?" or Whrrl's "What are you doing and where are you doing it?" with a threaded discussion or map being the result, which is then shared with friends. Sites like del.icio.us use self-interest to capture knowledge from users without their realizing they are doing the sites work for them. For social bookmarking, by giving users the opportunity to store and organize their own bookmarks, they provide the material for communal organization (or discussion, etc. if you take it further).

Labels: , ,

Capturing and Refining User Expertise

One of my longtime interests has been how to create a system that captures the knowledge of experts and refines it into a single resource. I was attracted to wikis early on by their communal authorship, but found the lack of structure unsuitable for my needs. What I wanted, for two of my early efforts, one a site intended to help family photography historians answer questions about old photographs and the other a site for programmers to find help with coding questions, was a way to let users engage in a Q and A and then somehow capture and distill the expertise into a more traditional article format (like a wiki page), which could be maintained by everyone. I wanted to capture the expertise emerging from the group discussion through some mechanism.

I ended up developing a content management system for the coding site, which had the ability to "fold" a comment thread attached to an article back into the article for editing. I also developed a tool, which could take a forum thread and turn it into an article text for editing. These solutions required a lot of manual effort to whip the unruly comments into a coherent article.

All along I wanted to introduce the communal editing feature of a wiki to this process, but I faced the obstacle of how to overcome the distinction between communal content and content owned by the user posting it. I racked my brains to design the system to somehow enable a transition from personal content to communal content, so that question and answer sessions centered around a code example or problem, could be "folded" into a more communal source of information, refined and with conclusions. But never found a solution.

Originally, I had wanted to develop my coding help site as a Q and A site like Experts Exchange. This explains why I needed some way of converting the knowledge captured by the Q and A session, if there were a solution, into an article form. A QandA session usually results in exposing a lot of valuable knowledge from experts. I wanted a way to capture and refine this so people could learn to code better from it.

Stackoverflow.com a Q and A site for coders. It is simply excellent in design and execution. What fascinates me most is their concept of a "Community Post." When a post is edited by more than four users, it it promoted to a Community Post, which is editable by every user and no longer belongs to the original owner. Apparently, they use a wiki-like versioning system for their posts, so the original post is owned by the original posting user, subsequent versions I suppose are owned by their editors (the user who revised it), and after four unique edits becomes the property of the community.

This mechanism provides a smooth transition from traditional _authorship_ to the communal writing style of the wiki where the community is the author and authorship is anonymous. I wish I had thought of it, since the original idea for my site was a "code wiki" that would not just provide solutions to programming questions but help coders learn from the results and improve their skills. I don't want to rehash my failures with phphelp.com, but to highlight an innovative way of providing a smooth transition between individually owned and communal content.

One of the questions raised by this is authorship. People like attribution because it builds their reputation. So in a wiki environment, they lose their attribution. A user's post becomes a community post. So what happens to a user's credit? One solution is to create an indirect proxy for credit in a communal authorship environment, so that good authors get "badges" or "reputations" that they wear independently. Instead of a "byline" for your post, you get a badge representing the amount and effectiveness of your contributions.

Which is better? Everyone owning their own content or communal content? It really depends on the audience and goals of the site. Some people prefer to own their own content and share it. This is how most social media sharing sites work. You own your content and your friends own their content and the site provides a way of sharing it. Social bookmarking sites also enable users to keep their own content separate from others and then the content is mixed and matched through tag navigation. A wiki-style system generally views content as communal. Stackoverflow solved this problem with a novel mechanism for transitioning content from individual to communal status.

It occurred to me this mechanism might be valuable in a so-called bliki system, which is a blog and a wiki combined. In a bliki, users create quick, timely posts like blog entries connected to dates, but they can also edit the content of posts to create and reference wiki pages. This enables users to make quick sketchy entries like a blog, but then later, reflect on those entries with longer posts. This is called "quick-slow" in bliki terms. What if this process could be facilitated by automatically transitioning the "quick" blog post into a "slow" wiki page? Instead of making a blog post then creating a wiki page linked to it with extra information, the blog post would at some point transform itself into communal content, from blog post to wiki page. Authorship would still be retained because each post would still exist in the wiki history. Anyone could go back to the original blog post to see who posted it and what it was about.

Labels: , , , ,

Social Realms: Sharing and Publishing Become One

There is an increasing recognition of the importance of 'social realms' within the context of social networking. Some social sites started out as "walled gardens" where only friends could see social content a user posts. Other sites started out with all content posted being public like a graffiti wall. Social site builders are now recognize there should be many fine graduations of control over viewing and sharing social content. These social realms extend out from the user in concentric circles, from the being able to see their own content ("me"), to friends, to friends of friends, to networks or groups of friends, and finally to the public.

Blogging was always seen as a form of publishing. The new systems emerging now are centered around "social blogging" or "social news feeds" and are called by various names. Facebook merged their "wall" application and their "mini-feed" application in a single feature called The Wall, an example of one of these new forms for facilitating social interaction between small groups of friends in an asynchronous manner (as opposed to chat or telephony). Like Twitter and Jaiku, they enable "social peripheral vision" or seeing what your friends are doing and passing brief notes back and forth to keep in touch or coordinate activities. These posts are not publishing in the traditional sense and are not considered publishing, since in theory, the posts are intended for friends (although some sites offering these services create a kind of public feed everyone can see).

The Wall on facebook has all the elements of Jaiku or other similar sites, a series of blog-like posts limited to a brief snippet of text in reverse chronological order with the ability for users to comment on them. What makes them social is that the posts are seen by your _friends_ who are the only ones who can comment. So you could post about going to the farmer's market on Sunday and a friend could comment by asking you to pick up some tomatoes. Another friend could comment they will be at the same market and will meet you there. Comments are an important feature because they enable individualized topical conversations. If friends could only post to the "circle of friends" feed, the conversation would become disjointed. Social posts are the start of conversation.

This just emphasizes the need for social realms that determine the scope in which social content is accessible. Facebook offers several social realms for Wall posts, your own, your friends, your friends of friends, your network of friends, the public.

The last is interesting, because it brings us full circle. Most platforms were publishing platforms before the social networking craze, then there emerged platforms for social sharing but without any publishing. Now the two platforms are converging into a single platform for sharing with granular control over the social realms into which any piece of content goes, from sharing with a circle of friends to publishing to the whole world and every gradation in between.

Publishing has a completely different feel to it than social sharing. It requires different tools, ones which facilitate authorship, but have no need for defining the social realms in which the works of authorship will be consumed. I had watched the emergence of Twitter and Jaiku but failed to see their signficance, since their posts were so brief. I saw them as being limit blogs, and idea I had toyed with in the late 90s, but bloggers were more interested in longer and longer posts, being literary types. They were interested in publishing. It was finally understanding the social use of these short-message systems (it is no accident the popularity of SMS correponds with the popularity of these small message blog-like systems) to keep people in touch socially that I understood their usefulness. It makes little sense to critcise the inane or brief posts to Twitter as not contributing to human knowledge or letters, the purpose of these sites, as it is said of Jaiku, to maintain social peripheral vision (something I didn't even know I needed and still feels uncomfortable in the "buddylist 24/7" way it is presented). Maybe someone should start a site called "Tome" for long posts of intellectual brilliance contributing to the total of human knowledge, a mirror image of Twitter. Or perhaps that was what Blogger was supposed to be.

The convergence between sharing and publishing, which began with the original c2 wiki and the lowering of barriers to a read/write web, is emerging as a powerful new metaphor for interaction. Publishing will come to be seen as just sharing with everyone. All content, all media will be social and social realms determine the intended audience.

At farmfoody.org, we will be moving quickly to provide our users with this kind of close-knit interaction, which eschews the private message metaphor derived from email and the blog metaphor from publishing. A graffiti wall is too public and random to be of much use, private messages are stultifying and open to abuse since anyone can send a private message across social realms. The blog was intended for publishing, the feed for syndication, but this new format, the social feed or blog, converges sharing and publishing into a form easily digestible and controllable by users.

Labels: , , ,

Farm Food: A conversation connecting food to people

It occurred to me that farm food is about more than finding fresh vegetables. We don't just visit a farmer's market or roadside stand because of the fresh vegetables. We go there to experience a sense of community. At the market we get to relate to real people. To meet people. To talk to vendors who know what they sell, care about what they sell, and can answer our questions. A supermarket produce section is like a warehouse peopled by stock movers who know little or nothing about the produce they sell. You may find a knowledgeable individual here and there, but the system is designed to move produce like boxes at a warehouse. The produce guy at the supermarket is not there for conversation. The relationship gets very personal when you have the same grocer for many years, when you visit the same roadside stand, when you buy vegetables or eggs from a neighbor with a microfarm.

I always remember how refreshing it was as a child when my mother would take me to the grocery store to buy meat for hamburgers or roast. We would always ring for the butcher behind the mirrored wall of windows above the coolers. A real, live human being would come out from behind the supermarket slickness and suddenly the store seemed more real to me. Here was a real person we could talk to in a big empty store. There were employees in the store, here and there, to be seen occasionally stacking products on the shelves or moving boxes. There were the checkout people. There were customers pushing their carts about the aisles. But you didn't hold a conversation with these people, you couldn't ask anything of them or get anything from them. No relationship existed with them. But the butcher was someone, the last person in the supermarket you could engage in conversation with, interact directly with, to build a relationship, however small.

We would ask him to grind our selection of chuck for us. We didn't trust what went into the prepackaged ground beef and wanted to pick the piece of chuck with the marbling and amount of fat to meat we wanted (invariably, we wanted more fat than lean offered, but less than the real fatty stuff). He would grind our beef and return it to us in a white paper package, or later, in the same kind of Styrofoam and plastic wrap package the prepackaged meat came in. What I liked about going to the butcher was that we could participate in the making of our food. We could choose the cut of meat we wanted. Inspect it for the marbling, fat content, redness, etc. and then the butcher would grind our beef to order. There was something to seeing the cut of beef before it was ground, still whole, like a steak, which gave a feeling of satisfaction, knowing that it was a good cut and where the ground beef came from, unlike the prepackaged ground beef. It was a social interaction, requiring conversation between producer and consumer, which was very satisfying. Even a child could notice. We came away with ground beef we felt comfortable with, arrived at through a negotiation, had our say in the process, did not have to take what was offered to us. It felt good.

A farm is a lively place of growing things. It is more of a happening that never stops than a location. A farm is not a depot for food where we pick it up and move on. It is a center of activity, socializing and participation. The farm offers the same kind of interaction I enjoyed at the supermarket butcher's.

As the driving force and principal developer behind farmfoody.org, I am beginning to realize a social network connecting farm to garden embodies what I enjoyed as a child about going to the supermarket butcher. It is a model for why we enjoy visiting, shopping for produce at farm stands, farmer's markets and local farms.

Labels: , , , ,

Simplicity and Community

Community: From Little Things, Big Things Grow is a really good overview of how community grew on Flickr and some of the philosophy informing how social community works.

At Flickr, we’ve worked very hard to remain neutral while our members jostle and collide and talk and whisper to each other. Sharing photos is practically a side-effect. Our members have thrilled and challenged us—not just with their beautiful photography, but by showing us how to use our infrastructure in ways we could have never imagined.

This is the same principle that operated when the web was born. It was simple, open and flexible enough that people could put it to unintended uses. It wasn't overdesigned. The net itself enabled people who "shouldn't" or "wouldn't" want to connect to find each other. It enabled people to find information they "shouldn't" need or want to find it. It enabled people to find, and share, what was important to them.

As I just wrote, the content, the pictures, the things we share on a site like facebook have little to do with the success of a social utility, they have everything to do with keeping up with your friends, which involves photos, but it is people, keeping up with what friends are doing, whether gardening or photographing, engaging in activities, like who can create the best compost heap or who has the best fashion photograph, that sustain.

The sculpture demonstrated a fascinating idea: given fewer rules, people actually behaved in more creative, co-operative, and collaborative (or competitive, as the case may be) ways.

It should not be surprising, given that HTML was a simplification of rule heavy SGML. Given fewer rules, anyone could make web pages and share them. Every time the network or web has grown, information technology has grown, it has been through a simplifying moment. It is also why the Wiki has touched such a nerve online and been very inspiring to what became called "Web 2.0" applications. It reminds me of a cool new online note taking tool Luminotes. I find its overall simplicity refreshing (for example, its simplified set of text markup options set off in oversize buttons and the brilliant recasting of the one-page-at-a-time-wiki into a scrollable set of note cards). Is the ideal website a tabula rasa like wiki, like a blank page available to users without any structure? I doubt it. Since that would just be a whiteboard or "graffiti wall" there has to be some simple rules aimed at organizing the activity toward some basic interests, as Flickr does.

It is true, corporations think they can "add community" like adding new delivery routes or buying an aircraft to open up a new route. You don't add community, you grow it. At farmfoody.org, we have to keep lines of communication open to independent farmers, many of whom have a low opinion of the usefulness of anything online. It takes a lot of time, commitment and personal touch to grow this kind of community. You have to show why getting online is important, and be ready to answer the inevitable questions.

Labels: , ,

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.

Labels: , ,

Farm Foody: A Social Network Connecting Independent Farms to People

Over the last year, I have been working with Tom Davenport, and Matthew Davenport, of Hollin Farms, a small, independent but very internet-savvy family farm to start a social networking service Farm Foody (farmfoody.org), which uses the Internet to connect local farmers like you to their customers. I would like to summarize why we believe social networking is so important to the survival of the independent family farm, by posting a revised version of our flyer.

A social network is a group of people who become connected to each other through their activities and interests within an online community.

We believe a social network increases the economic leverage for the independent farm. A catalog of farms or an individual farm homepage does not change the economic leverage of a farm. A social network gives the small farm leverage in a big agriculture economy in two principle ways: by helping farmers manage their relationships with customers more efficiently and generating a more effective marketing presence through the social networking experience.

The independent farmer must create a close relationship with the customer, similar to the relationship an artisan baker or butcher has with their customers. This involves effort, which our website seeks to reduce to a manageable level and leverage for marketing effect. We hope by providing a means to relate directly with consumers as a “personal farmer” your farm can compete in a small farm economy becoming dominated by high end, specialty products.

We like to think of the social network as restoring the balance that once existed in small town America between the farmer and the customer.

A social network provides benefits to both farmer and consumer. When people are members of a social network, they automatically generate a marketing presence for you through normal activities they find beneficial. This presence is much larger than any standalone website, catalog or advertisement could provide, since it includes all of the people who are friends of your farm and their friends, and so on. These indirect effects are difficult to enumerate, just as the fertility of the soil is hard to explain, but the effects are there for all to see. We all recognize fertile soil when we see it by the vibrancy of the plants growing in it. The social network is like the soil a plant grows in.

People are encouraged by the social network to discover new farms by exploring the relationships between network members.

When people visit a social networking site, they will ordinarily explore the site through following relationships with “friends.” In a social network, anyone can be a friend of another member. In this manner, they often find other members to become friends with who they might never have found through searching. This process is similar to “word of mouth” in the real world, where people ask their friends where they bought their produce. This phenomena drives new customers to your farm without the farmer being required to do anything.

Think of how musical groups create elaborate websites to market their music, yet nearly all successful music groups today maintain a presence on a social networking website. They receive much more activity and feedback, much greater awareness among young people who buy their music, through the social network than the traditional website.

Unlike a catalog of farms, even with a locality search, the social network draws people in and keeps them there with an activity, it gives them a stake in the farm and in their own presence on the site, which benefits them and the farms they affiliate with. Your “profile” (presence) on the site becomes a place for customers to return to for the latest information on your farm. A customer's profile becomes a way to share their own interests (along with your farm) with others. When you post a bulletin (like a classified ad), it automatically flows out to friends of your farm. Non-farm members can even use the network to promote themselves.

Think of a chef joining the network, becoming a friend of several farms they purchase produce from promoting his own abilities through his network of friends and bulletins, leading new customers to your farm.

The social network involves people with the life of the farm. Interest in agriculture has never been greater. The farm is an exotic location for agricultural tourism. Organic food is an established product. Eating local has never been more attractive to the consumer. With books like Omnivore's Dilemma, and the recent anxiety and uncertainly about imported foods, people are more likely than ever to wonder where their food comes from. Farm Foody leverages this social change for you.

A site designed by farmers for farmers.

Our experience at Hollin Farms helped us to design an online service mindful of the needs of farmers. We understand the farmer does not have time to sit at the computer figuring out how to update their information. Our goal was to make using our site as simple and immediate as possible in order to reduce the time and effort you spend answering customer's questions, keeping your customers up to date on availability of produce, and the like. We believe the Internet can play a vital role in helping the independent farmer survive and prosper in the 21st century.


A website by Tom Davenport, Hollin Farms (hollinfarms.com) and Steve Knoblock (brandymorecastle.org)

Labels: , , , , , ,

A Trip Through The Minefield of Knowledge

I have frequently been the victim of an author who has a peculiar view on a subject, which turns out to be simply wrongheaded. Because there are so many books, many more than I could purchase, read and evaluate and because turning to book reviewers is frequently just as useless as getting the wrong view from the wrong authority, the value of books can be somewhat limited.

It is easy to assume that if a book is published on a subject that the author knows something about the subject, that they are well versed in he subject and

The problem is that authors have differing views on the same subject. They have different backgrounds and differ about what is important to them. Writers generally write what they know. This is a problem, for example, in music. Thirty years ago you could not find a book explaining harmonic theory behind blues harmony. Oh, there may have been a few academic or musicological works on the subject, but generally, if you wanted to learn blues harmony you had to listen to recordings or ask a blues musician.

This was because the cohort of music theory writers disdained or held blues music in contempt, did not listen to it and thought it base or childish. Blues, they thought, lacked the sophistication of Western classical music. It was all bump, bump, bump and grind. It musicologically wasn't worth the time of day to them.

Yet, blues music contains the most sophisticated polyrhythms outside of Polynesia and the most colorful expressions and sophisticated harmonies of any music, borrowing the Western harmony and mixing it with expressive melody moans and instrumental vocalizations and "harmony" bordering on chaos and dissonance. These writers could not see (or hear) this, because they didn't want to hear or see it. They were racists or elitists or just didn't like the music. My parents, who liked 50s rock and roll, never liked singers who "yelled" and where "you couldn't understand the words." So to them, at least some of the blues based music was inaccessible because of its affront to the senses.

I noticed that despite my love of various forms of hard edged music, that even after enjoying several hours of hard rocking music, that my ears would tire of the distortion. I loved cranking up the distortion when playing electric guitar, but have to admit that hours, maybe even minutes as I grew older, became grating on the ears compared to folk music, classical guitar or classical European music (my brother found he could not concentrate on his work while listening to classical music because the strong emotions it evoked were distracting).

However understandable the reluctance to write seriously about blues music was, it was incredibly damaging to the quality of description, transcription and writing of blues and blues based music in book or sheet music form for a long time. This did not deter people from learning blues by stumbling through poorly written books, slowing down records on tape recorders and asking friends how to play licks.

But it did make it terribly confusing and difficult to learn anything about blues from books. You might ask where is this all leading other than to the ran tings of a frustrated guitar player? It raises a profound question about information, whether the "Wiki" model of authorship, collective authority, is best or whether the traditional model of authorship as a single authority is best. With the wiki model wisdom becomes refined by becoming conventional. There is a tendency for collective authorship to become settled.

(A word about why this bothers me: One of the things I was taught (part of my miseducation -- a story for another time, but an important concept as an education, because everyone gets a miseducation as well as an education) when very young was that what separated us from both societies before the introduction of movable type and before literacy, was the capacity to record knowledge in book form, by which knowledge could be transmitted to future generations and distant persons with perfect accuracy. All that was necessary to learn something, was to find a book on it, and follow the instructions. This turns out to be impractical and bordering on the absurd. Although there are rivalries between "book learning" and "experience" nearly all crafts, professions, activities engaged in by people require more than "book learning" to achieve any results. Most professions, from computer programming to music, require "folk knowledge" such as "programmer lore" or ways of solving problems, common algorithms, etc. handed down from programmer to programmer by "word of mouth" and deemed to minor to put in books. Of course, this knowledge can be vital to success in the real world of programming.)

Collective authorship can create greater accuracy, given the weight conventional wisdom formed by this authorship is ordinarily correct, than from an author with a peculiar point of view. However, you are much less likely to encounter a disruptive point of view from a radical individual who takes on a false conventional wisdom. There seems to be no solution to this problem of authority in information, other than to say sometimes conventional wisdom is correct because it reflects the intelligence of mobs and sometimes a lone wolf is correct while the conventional wisdom mob rules with a pack of profitable, self-serving lies or delusions.

So will it be the Digg model where the mob tosses the good stuff up on the heap, the Wiki model where the mob through collective wisdom and weight of numbers creates a refined collective wisdom, the Google Knowl model of collectively peer-reviewed free form works with bylines, or will it be the social network that filters knowledge through a mob of friends and groups that works best?

Labels: , , ,

Social Networks as Walled Gardens

In an article, Facebook-Based Applications Can Now Run on Other Sites by Heather Havenstein, Computerworld, IDG, quoting Sean Aune, said

...Aune added that Facebook is looking to stem criticism for being like a
"walled garden in that things do go in but nothing comes out.
However, the social network is like a walled garden, which is part of its power to filter information through the social network instead of searching. This could balkanize the web, turn it inward, where people only see content posted by friends and their subscribed networks. But this is not too different from how people use email discussion groups, forums and other social media. The web could end up becoming a network of social networks and search engines might become either dinosaurs or searching the social networks instead of indexing random public web pages.

The social network empowers users to manage who can see their content instead of just loosing it on the web. This can reduce the power of serendipitous finds of information, which is one reason the web was so successful, but like the Creative Commons, it does empower users to control how their own content is used, by potentially allowing them to specify where their content is seen or distributed, whether kept private, shared with friends or with groups or other networks. We already see this model forming in Facebook, which allows users to say how and where their posts are distributed, to friends or selected groups.

I welcome the opening of the Facebook network and we hope to participate through our social networking site connecting independent farms to consumers, farmfoody.org.

Labels:

Social Networks Turn the World Upside Down

While developing Farmfoody.org over the last two years, we came up with a very similar idea independently. Most sites designed to help you connect with local organic farms require you to search for farms in your locality. We thought that people shouldn't have to search for stuff, it should come to them automatically. If you wanted some fresh locally grown tomatoes, instead of searching for for farms with tomatoes for sale in your area, you just check your own profile to see if any of the local farms you are friends with have tomatoes available. This might be through a map of local farms or through a farm you have become friends with that has put out a bulletin about their new tomato crop. We decided that a social network was the best way to direct and filter this information to the consumer and enable them to make unexpected connections with farms and foodies whose interests and connections mirror their own. People could explore the world of small independent farms and the people who love good food.

The strange thing about comparing Myspace to Facebook is that they are almost opposite worlds. One is completely open with everything literally hanging out all over the place and the other is completely closed without much showing, like an iceberg. Facebook is a set of private networks without any need for the public to be involved or view their content. This could also be true for Myspace. There is really no need for Myspace profiles to be public any more than Facebook. Except that people and musical groups for example use their profiles as public faces, as advertisements and ways to communicate with the public beyond their circle of friends. There really is no way to search Facebook for user criteria other than as a person. One Myspace there is nearly unlimited criteria about the person and their interests to search. Our site, Farmfoody.org will have to seek some balance between these two.

When I go to Digg, I am presented with stories that have been voted to the top. "Voted on by who?" I ask. Every Tom, Dick and Harry? I find sites like Digg (or kuro5hin, Slashdot and other pioneers) filled with content moderated by voting systems unsatisfactory because I do not know or trust who voted on them. What I think would be a better solution is to receive content other people belonging to the same group think is important. This is the facebook model, which could be extended to all kinds of information. I would be much more likely to use a Digg-style site that showed me all the feeds or stories my friends found interesting than a general news site. Why not use the Google Reader model within this context?

Why not take it further? Why not build a site where people read RSS feeds and then share them within a social network instead of the public? Then I could see what my friends think is worthy of sharing. They could vote on the "interestingness" of items in their own feeds and profile and these could be automatically displayed in my profile. Any content they contribute could be monitored from my profile. Any number of layers and methods could be used to "mashup" the content appearing in my profile, either for public or private consumption (depending on the orientation or facing of the site). The social network is a way of utilizing the implied stamp of approval friends give to filter content. Instead of randomly searching about the web or looking at content voted on by idiots. I believe we will see more of social networks being used to filter content.

Labels: , , ,

Social File Sharing

I recently received an email from a well known supplier of enterprise level file sharing systems. In the enterprise, one solution is called "Wide Area File Services." There are other ad hoc solutions. I am not very familiar with the details of these systems, but understand some of the problems they are trying to solve. A corporation wants fast, simple access to files from any location (anywhere their employees are) while ensuring users access a single version of the file. The are also concerned about the cost of bandwidth (which ensuring a single file helps, since users normally waste resources copying and forwarding a file or video by email, since they are really not aware of the consequences and generally do not understand they can just forward a link).

Although these issues are important, I think this perspective misunderstands the most important need today. Corporations are always concerned about meeting requirements, being defensive, controlling their population of employees more than they are about doing something new or finding new and better ways to do something. They are blinded to solving the problems of how to do more things better by the need to clean up the messes their productivity and growth creates. This is why they are so often blindsided by innovation.

What we really need is social file sharing. What good is sharing a file, a digital photo, video or spreadsheet without knowing who it came from and what group it belongs to? It starts with a simple idea:

Every piece of information should be accompanied by the identity of persons or group to which it belongs wherever it goes.

I've given this issue some thought before, but the email reminded me of it. By "belongs" I mean to include both the individual or the group to which the file is associated with in a given social network. For example, we already see an example of social content sharing through sites like Facebook. Of course, YouTube is also a kind of platform for social sharing of content, but there the concept of "file" or a package of information anyone can take with them and carry it onto their PC or laptop or cell phone or save on a CD is missing. And no, YouTube is not good enough. What we need is a way to retain a media object's social connections as it is transferred from system to system. To do otherwise would imprison files on their respective platforms.

When I upload an image to flickr, any social connections formed around the image is contained within the flickr ecosystem. If I download the image and then share it with someone, the social connections are lost. If I share the original image with someone by email, it lacks the social connections the version on flickr acquired. Why can't all these versions of the image somehow carry social connections the same way EXIF data carries meta data about the production and authorship of the image?

Maybe someone is working on this right now, perhaps a modification of existing RSS standards to allow social network information along with an attachment, creating a kind of "podcast" that could bring social data along with the file. Maybe Google's open social network framework is looking at this. But whoever does it, it is important that it gets done.

Labels: , , , , , ,

reFrame : Yet Another Photo Sharing Idea

Here is an idea I had recently for a new photo sharing application, which would make it easier for anyone to use photographs in their own context. A site is created where users can sign up. They submit the name of their Flickr photostream. The site pulls in any photos from their stream that have rights set to Creative Commons remix license. Any user of the site can select any image pulled from the users Flickr photostreams collectively. There could be a single photostream "lightbox" used to select images from, I'm not going into details here.

The idea is to let any user "reframe" any image contributed to a pool of images by other users. Reframe means to give the image another context. For example, an expert on historic photographic processes might frame an image with a text explaining the history and chemistry of the process that made the photograph and how to identify an example of this type of photographic image. A family historian might frame the same image with the biography and family history of the subjects in the photograph. A single image has a potentially unlimited number of contexts or "frames." The system would allow anyone, in the style of a wiki, to "reframe" any image.

Users of the site would have to agree that others can place their images in any possible context, possibly unintended or unflattering, which is why there is a requirement for the non-commercial remix license. Of course, you can do this already, but I do not think there exists and application that makes this easy and puts it all in one location.

This might be combined with my idea for a photo wiki system that encouraged the "quick-slow" process enabled by the so-called bliki, where the same contextual system could allow a quick caption when the image is posted and later more sophisticated commentary and use of the image would follow by creating "pages" associated with the image.

One might object, saying that anyone is free to combine images and text if there were a word processor style system that allowed images to be freely dropped into text anywhere. But the web has shown that it is better to provide a system that structures content and interaction as it being created (wiki allows this process to be continuous). This is where the quick and easy part comes in...it is not so easy to arrange photos and text with a word processor. You do not see many people using a word processor instead of a blog or photo sharing site, although they could create richer documents and post them to their own website using today's word processing applications.

I wish archives and institutions would catch on to the power of reframing images in their collections using contexts contributed freely by users. The academics, visitors, people on the web, anyone should be able to frame images of artifacts or media artifacts themselves, historic photos, old films, video, etc. to create the richest possible understanding of the holdings. And make both the artifacts and knowledge about them more accessible.

I'm thinking of grabbing phpflickr, Dojo and Codeigniter and putting this together, but with the work on Foody and Folkstreams, I really have limited time. Steal this idea, please.

Labels: , , , ,

The Folksnet: Folk Culture and Web 2.0

Although I am not a folklorist, through my work on the Follkstreams website, I have come to appreciate the study of folk culture and understand how expansive a field it represents. Folk culture is the culture people make for themselves and share with others. Web 2.0 is a folk culture, it even coined a phrase "folksonomy" to denote a system of categorization that replaces a vocabulary controlled by an authority or group of authorities with a vocabulary created ad hoc by the people involved in using the system of categorization. The media sharing sites like YouTube and MySpace and "mashup" systems like Yahoo Pipes and Microsoft Popfly enable a rich shared folk media culture to arise. Increasingly, as we head into the 21st century, it is a supreme irony that folklore is taking on greater importance as nearly everything is democratized and individualized, and is poised to become perhaps the most significant field of research in this century, after having for centuries remained an overlooked backwater in academia.

Folklore already possess the vocabulary and methods to comprehend and measure such a brave new world. It has the attitudes and assumptions, the knowledge frameworks ready at hand. As we understand how the mind works, as we democratize, we will realize the central role played by narrative in the workings of the mind and society, that society is a kind of virtual reality similar to the internet in which abstract things affect the real world, that narrative and oral tradition exist everywhere and explain how people know what they know and apply what they know to the world around them. This is a profound shift from the rationalist assumptions that have driven Western civilization since the beginning of the Enlightenment.

Labels: , , , , ,

Out of many, one: The acceptance of many views.

I've talked before about the need to accept the inconvenient existence of multiple of truths that exists in genealogy. Incomplete knowledge about the past is unavoidable. The past is gone and we are not getting back to put under a microscope. Even the present is difficult to pin down. We only know what we experience or someone tells us, which is pretty much what we know about the past, only through source material and what someone tells us. We are left frequently with only sketchy knowledge about family history. This leads to different families claiming the same individual, each with their own basket of evidence and story. I've learned to accept this as a reality and moreover, I've learned to accept this as being a Good Thing (or at least the best thing we can expect given the nature of reality).

The net it turns out is very good at handling incomplete information as it rapidly emerges and changes from multiple authorities. The applications emerging ont he web are gradually all taking on a similar shape. They all in one way or another incorporate the acceptance of many views. The wiki synthesizes a single view out of the many views of its authors. Social bookmarking (and other social networking) sites allow multiple "truths" to exist within the same space. The social network creates an ecology where authority can develop implicitly, without saying. Most of the social networks incorporate the many views or truths into some kind of aggregate view that is useful, a kind of single view out of many. This represents a democratizing of knowledge, but I hesitate to call it democracy since that is just one particular method for synthesizing a single truth out of many views. Democracy works in a very crude way by voting and we know that voting systems are subject to gaming by malicious people and other flaws. The kinds of systems, wikis, social networks, voting systems used by various collaborative news sites all represent vastly more sophisticated methods of synthesizing a single view out of many than democracy, which is relatively weak and produces a "tyranny of the majority" when not mediated by some system of individual rights.

I was explaining how social networking works to Tom Davenport today in regard to a farm website we are developing. I explained to him how if he had an account on a social bookmarking site, he would for his own benefit maintain and organize his bookmarks online. He would bookmark sites on pork and beef as he does now in Firefox. To do this he would create tags for Pork and Beef, organizing sites about pork and beef under those headings. Because the bookmarks are shared publicly and the tags exposed to to browse and search, a person can click on the Beef tag and discover his bookmarks (among others sharing their bookmarks). That person might click on his user profile to look to see what links he has on Beef. They might find his bookmarks are highly reliable and useful. Therefore, the user would be likely to turn to Tom's bookmarks when looking for accurate information on beef and cattle raising. They would not necessarily even know that Tom is a farmer, but they would discover him as an authority simply by observing the quality of his bookmarks on the topic. Tom Davenport implicitly becomes an authority. He implicitly shares his expertise with others. All without declaring himself a farmer or an expert on anything. Of course, he might mention in his profile he is a farmer; he might link to his farm site and you might have more reason to trust his bookmarks.

I tell this story because it illustrates the acceptance of many truths that lies behind the way the web works today. There may be ten thousand people on a social bookmarking site who think they know something about beef. Each may have a different idea of how to raise beef. Their bookmarks will implicitly reflect their knowledge, experiences and differences of opinion with others. The gestalt of the social network will reflect this diversity. The more accurate providers of bookmarks will become popular, the ones with less accurate bookmarks, reflecting radical, not very useful or very different views will remain less popular. One might object that this creates a kind of stagnation on popularity, but in reality it relates directly to the idea of the "Long Tail" where more people may be accessing the less popular bookmarks more than the popular. So the social network embodies two kinds of authority simultaneously. The authority of popularity and the authority derived from the long tail...the authority of individualism, of the disruptive idea, gives freedom to both kinds of authority and the freedom to move back and forth between the two kinds of authority...for the disruptive idea to start as a seed and grow to an oak, to move from being "indie" knowledge to "popular" knowledge all within the same framework.

It is fascinating that the web reflects this reality by its nature. That a concept coming from an obscure activity like genealogy is moving to the center of intellectual pursuits. That it can create a framework where out of many views a single truth can emerge without denying all the other views. It reminds me of the vast jumble of "junk genes" that we carry along in our DNA from our distant past, which are there because they might just come in handy some day. It reminds me of how organic the web is and utterly incomprehensible within the old framework of bell, book and schoolhouse knowledge it is becoming.

Only something organic can be becoming. And the web is always becoming. Always becoming something. A book is never becoming, it only was or is. Scholarship is locked into this model since the Enlightenment (oops, the E. slipped in there...was hoping not to mention it), what it means to posses knowledge, to share knowledge, to build knowledge and discover the truth is all changing now that we are connected to knowledge on the network. So strangely different than books. I've rambled enough for now and must retreat to the high tower of Brandymore again for the night.

Labels: , , , , , , , ,

Social Science and Folklore

The kind of social science work exemplified by Albion's Seed and the kind of work done by folklorists demonstrates the value of vernacular material, the potential usefulness of photographs of ordinary people and places. The scholarship of Albion is based upon two pillars, the first is social statistics and the second is anecdotal. The latter is used to confirm and explore the culture as it existed, such as Byrd's secret diary. The former is used to verify anecdotal and cultural evidence (from the diaries and art of the time). In the eighteenth century photography had yet to be invented. This means that now is the first time we are beginning to use photographic evidence, the documentary tradition, as scholars have used written documents, letters and journals.

The photograph, and recorded visual imagery in general, which includes photography, video and any new technologies in the future, such as 3d visualization, present us with both a documentary record useful collectively to social science and an individual record similar to the anecdotal one of journals. Photographs are both evidence and require interpretation. What is in a photograph we can measure and aggregate into social statistics, what is happening in a photograph is open to interpretation. This is where context becomes important, since we must rely upon the anecdotal written record, upon stories and recounting of events to understand the image. If we fail to record the social context of the photograph or reconstruct it through providing context, we fail to understand the image.

In any event, there is a connection and relationship between social science and folklore, the aggregate and the particular, the evidentiary and the anecdotal that are required and mix together to create a more accurate picture of the past.

Labels: , , ,

The Swicki: Collaborative Search

I've long thought that the fatal flaw of what library science calls "finding aids" is that they only organize information according to how it relates to other information. What I've always wanted is a search that relates information to what I care about, to my interests, to me. I've thought about "personalized searches" but the trouble with this approach is that it is time consuming to express to a computer exactly what it is you want. You must set up some kind of criteria and the the search returns results for you based upon it, such as the simple eBay search notification. If lots of people are going to use this with the efficiency they now get from Google, something else is needed. We don't have expert systems and artificial intelligence yet, so what is a possible solution?

Some are experimenting with attention. By tracking what you look at online, a profile of your interests can be built, which can then drive a personal search engine. People are really bad at expressing what they really want (as product developers and marketers have discovered) so the non-intrusive method of observing behavior may just work.

Another experiment takes a different approach. Why not let other people help refine your search? That is what the people behind Swicki seem to have done. If you could gather like minded individuals into one location where they could influence the accuracy of the search, the "search in a can" model could be improved. It goes farther than that. By becoming an aggregator of search results the system can ride on top of the web and use it as a database in a way similar to Yahoo Pipes. The most revolutionary aspect of Swicki is user created search engines. Instead of needing millions of dollars and massive servers, Swicki piggy backs on existing search results to enable anyone to create a web search engine. This kind of democratizing is a defining quality of web two point oh applications.

I see how the canned search model can be turned inside out, by allowing a group of users to collaboratively refine the canned search to improve it. Instead of empowering the computer to be smarter, it empowers people to create a smarter resource. It definitely becomes a kind of search-wiki. It competes in some ways with the idea of folksonomy. We have now user created taxonomies and now user created searches. What I like about both developments is how it democratizes the organization and finding of information. The folksonomy enables people to create their own vocabularies, perhaps multiple vocabularies for the same subject area. The wiki search enables people to create alternative search results for the same subject. My background is in a subject where unresolvable disagreement is commonplace. It's called genealogy, where there are no facts, only interpretations and sometimes two families claim the same individual. This is not something for concern in genealogy and I like the way more than one truth can exist within the same framework, it's much better than declaring one view right and all others wrong and working hard to keep your opponent's views out of view. Despite what some may claim, there can be more than one version of the truth. Let an idea gain mindshare on its own merits.

I've thought before about a search engine where you could search the web by creating predefined searches, but never thought of letting everyone edit your predefined searches, that is novel, just as with social bookmarking

You can see the Swicki I created in a few minutes in the sidebar of this site (as long as it's there).

Labels: , , , , ,