Twitter and A Flock of Seagulls, Publishing in a Networked World

I'm not going to name the site that got me starting writing this post. Its a sentiment I've seen on many sites with a traditional publishing orientation. They follow the old tradition from the age of print, where all submitted works are required to be "not published elsewhere," requiring "first print" rights and demanding every "reprint" (copy) should cite the publisher as place of first publication (what is this, vanity?).

These guidelines ignore the reality of the new age of immediacy, of information abundance, of venue abundance, the network. There is no scarcity in publication, there is no value in "first publication" or artificial scarcity on the network. The document is the conversation the conversation is the document. The old publishing world is gone, stop trying to hang on.

The attitude simply does not fit with a universe of networked information being shared and reshared by millions of people, winding its way in bits and pieces and fits and starts through the social network of friends, family, colleagues. The network is the world of social publishing.

Why? Because it is to difficult to find works online among billions of documents and uncounted trillions of ever expanding words. You just can search for things you do not know exist. The social network trades in attention, which is necessary to discover what exists, through your social contacts.

It just does not make sense to "publish" a work to a certain location (or a physical book), then try to get everyone to come read it through clever marketing. It makes no sense to prevent copying, since copies are the method by which information spreads through a social network. The idea of scarcity and exclusivity makes no sense at all in a socially networked world, unless by exclusive you mean being friends with the author.

The network, by the way, does not really need to worry about this issue of citation, since there is usually a trail back to the original author, through a 'retweet path' (if dutifully or automatically maintained) or through carrying authorship information with the work through the social network (as I've talked about here before).

As a poet, nearly every poem I write is immediately published to the social network, so I can't give anyone "first rights" to it, and moreover, that is meaningless. I noticed the Haiku Society of America states, at least for some submissions, " The appearance of poems in online discussion lists or personal Web sites is not considered publication." a much more adaptive policy.

What happens on Twitter is more like a flock of seagulls, making all references to publication, first publication, second publication utterly meaningless, as we tweet to others and they tweet back at us, retweeting and retweeting. I suppose the next thing, is they will want "first tweet" rights. I understand the goal is to keep your publication fresh, but that simply does not fit reality. It says something about a publishing world where the consumer needs to be reassured they are not being "cheated" by recieving old goods, which are turned over from elsewhere, similar to the way "shovelware" became a problem in the 1990s CDROM publishing era. I suppose the same problem exists with bloggers, twitterers, who merely repeat what others write, but I just don't see the problem. In a network world it costs nothing to unfollow or unfriend a source.

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

Koans, Cavaliers and Facebook

We are raised in a culture that teaches us to always look for answers or winners. We are taught to expect the purpose of a question is to find the answer. We expect the goal of a game is to win. In Zen practice, students are given questions to ponder in the form of stories, called koans. I was taken aback when I realized the purpose of the koan was not to find an answer to the question, but to measure the progress the student has made in understanding zen. It was a shock, for this rational and scientific minded person, to consider there might be some other purpose to a question than to find the correct answer. Although one can find cheat sheets with common answers to zen koans, there may be no correct answer to a koan. The answer, although interesting, is not the important point of practicing with a koan.

A koan is a measure, just as for those who believe in 'fortuna' culture (a common belief among Virginia cavaliers was that each person was born with a certain amount of forunta or good luck, which could be modified by charms), games of chance are measures of how much fortune one possess. The aim of games of chance, such as dice, is to discover how one's own fortune measures up to the other players, not to win. Sometimes a zen student will supply a stock answer to a koan, but the experience is missed if you get the answer to a koan from a cheat sheet. A koan is there to help understanding. When Helen Keller learned the meaning of "water," she experienced a profound moment of realization, which ordinary children might never experience when learning the name for water. If she had used a cheat sheet, she would have only learned that water is water and not that cold, liquid on her hands was water, her understanding, if you could call it that, would have been divorced from experience.

It was a new concept for me to absorb, how people are interested in tests telling them something about themselves, measures of who they are, yet I should not have been surprised, since such quizzes are popular on Facebook, such as what are your guilty pleasures, what would you do if you could go back in time, what superpowers would you choose, and the ultimate question is probably How Well do you Know Me?

Labels: , , , , , ,

Twitter outage creates panic

According to CNN, the twitter outage left users feeling as if they had lost a limb or left home without their cell phone. It is suggested Twitter needs competition to provide alternatives when an outage occurs, as they inevitably will. There were (or are?) a couple of alternative social microblog services available (is jaiku still running?). Of course, this won't help if multiple sites get attacked at once.

What would help is Google Wave. This outage is an incredible opportunity to demonstrate the potential for resiliency a "federated" or distributed social media system has. Content in the Google Wave universe is independent. Every user can have a copy of a bundle of posts, comments, content on their own device. Multiple copies can exist on different servers. It could be possible for a group to continue working, or at least work offline with their content, during an outage and then when connection is reestablished, the changes can be merged back into the conversation. This is what we can do with email now. We can read messages in our inbox (as long as it is not webmail) even when the network is unavailable. We can keep messages around as long as we want. We can write draft replies, take notes, resuse content through quoting or editing the text we recieve and at any time later, forward to others or send the revisions back to the sender.

What did I do during the panic? I just waited for Twitter to come back up. I only post once a day (if I am feeling up to it).

Labels: , , , ,

Twitter as Attention Machine

I am reading On the Origin of Stories, a new book by Brian Boyd, which to make a long story short, draws conclusions from recent research into the mind and evolutionary psychology, that status is essentially attention (or at the very least attention is the currency of status). I can see how this applies to Twitter. The ability to 'favorite' another twitter's content is yet another way of bestowing attention. Twitter is an attention machine. When visiting a twitter's profile, being mentioned or retweeted in the stream of updates or being favorited are ways of gaining attention. A twitterer gains when a user with high attention favorites one of their tweets and more so, when they retweet.

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: , , , , ,

By Twine or By Time?

I ran across an interesting answer in an interview about Twine:

[Nova Spivack] I think the above solution would work for this too. Basically you are asking for a new view of the content – not “by twine” or “by time” but “by popularity” or “by relevance to me”.

Notice the question being posed. What he is asking is, why don't you like the view our "intelligence" provided, why do you insist on these existing, simplistic views like by time or popularity?

The last is odd. "Relevance to me" is the primary criteria for all information I want to receive. Even if I don't yet know it is relevant, such as when a person I follow in Twitter shares something I've never seen before and would never have found on my own. Do you understand? Even that is relevant to me. Everything I want is relevant to me.

I understand what they mean though. They mean serendipity. Like overhearing a snatch of conversation in Twitter by seeing posts by friends of your followers, but who you do not follow. But it still is relevant to me, you're just increasing the chaos in my information feed. Perhaps what we need is a "volume control" on chaos in information filtering systems.

Moreover, I suspect that humans being humans, really want to order information in the ways they are familiar with, the way their brain was designed to process information through evolutionary psychology (hmm, this is a new kind of "design" process, contradictory to the meaning of design, but seems appropriate to say design, designed by evolution). The upshot of this is people still want to order things by time or popularity. What other measures are there than the one's we've known?

Authorship: When we buy a book because the author's name is on the spine or cover in 96pt type. We are buying authority.

Sharing. When we "hear it through the grapevine" from our friends. Another high trust information source.

Some finding aids are a form of recommendation, as when we used to go to the reference desk librarian and ask for a book on a subject. This is a kind of sharing.

Look at the role trust plays in gathering and accepting information. Yet, we trust the smartness of crowds (or at least the smartness of cliques) at Wikipedia. I use it all the time and find the information is always a good starting point, usually reliable for technical information.

With trust comes the opportunity for abuse of power. The power of authority to stifle innovation and knowledge, to be used for sustaining false views (think of how the view of the Amazon civilization by anthropologist maintained for a hundred years turned out to be completely wrong and opposite to reality, despite the application of the "scientific method" and mountains of "evidence" all chosen, selected by a reductionist process, which only knows what it measures, can only measure what it sees).

Labels: , , , ,

Trouble in dead trees and inky fingers land

Newspapers and thinking the unthinkable

An excellent analysis of the situation newspaper based journalism is in.

I like the idea of micro-payments for content, such as New York Times articles. The only problem I have with it and why I would be reluctant to use it, is simply that I have to pay for the article before I've read it. Even if I saw an excerpt, it might not be enough to determine whether it is worthwhile or not. A solution for this problem might be found in social networking. I usually read articles my friends share with me (by sending a link in email or chat). I would be much more willing to pay for an article they recommend. Keep the price low and integrate with a social sharing system and it might work as long as the payment is by an "easy button."

The greater problem is content and authorship is changing radically with digital content available through the network, given the unlimited perfect copying and access without distribution. What we are seeing is a working out of the many pieces loosely joined paradigm described a decade ago. The newspaper started as a handwritten piece of paper passed around coffee shops in Enlightened London. I see nothing sacred about its continued existence.

The problem of journalism online is of course that Twitter is the new journalism but the content is too brief, chaotic and frequently idiotic. Micro-blog formats do encourage conciseness and sharp thinking, but they also promote a hyperactive and fragmentary view of subjects. As I wrote in my blog, there needs to be a "slow thought" or "slow news" or such movement (like the Slow Food movement), which you might say is what blogs already give, but not really.

Labels: , , , , , , ,

Twitter and the Principles of Illusion

It is worth noting the two guiding principles of illusion are "suppressing context" and "preventing reflective analysis" (according to Tufte, in Visual Explanations). The first applies also to the ubiquitous photographic image, nearly all of which appear without context. A situation that apparently few people find troubling. A good example of the phenomena is the iconic image from the Vietnam war of the Viet Cong operative being summarily executed by a village officer. The photographer who took the picture often wished he hadn't because of the damage the image did when used out of context (as was the usual case). Several iconic images from the Vietnam war were frequently presented without context. It was left up to the viewer to interpret and may very well be people at the time did not want to know the context, enabling them to press the image into service of their political aspirations or personal, psychological needs. Visual media is inherently weak at providing context.

The emergence of email, web discussion forums, short messages, video sharing, all network native forms of communication create an environment hostile to reflective analysis. What is needed to alleviate this trend is a movement akin to the "slow foods" movement, perhaps a "slow media" movement, asking people to slow down, consider context and think reflectively within a network information ecosystem. The content of a Twitter stream can be informative, but it can also be trivial, and despite its benefits, it does not encourage reflective analysis. I personally find a tweets (Twitter messages) are frequently a touchstone for an innovative thought, connecting me to something I did not know and probably would not have had someone not passed on an interesting web link or thought out loud. But it would still be nice to pull wisdom from the ether by capturing tweets in some reflective and expandable form.

Although not yet a visual medium, these concise messaging and blogging systems are most attractive to television journalists. A quick turn Twitter before the commercial graces many newscasts. These context free nuggets are ideally suited to a medium described as a "wasteland" and it troubles me that networked content has been so eagerly adopted by television news shows. It points out the need for reflection and context in networked short message content.


I have explored this theme before (see Twitter Wiki, "quick-slow" bliki articles previously). The question is how to accommodate the fragmentary, context free units of networked content and encourage expressions of context and reflection to balance them. It is a daunting task because people often do not see a need for context or reflection and are often unwilling to bother with the story behind a photograph or take time to expand on a short message.

We need to accommodate the uses for which short messages are legitimate and when they are beneficial (such as the conciseness they encourage...concise writing requires reflective analysis before posting, you must know your subject well to pare it down to its essentials and wordiness often just adds confusion...we must be prepared for abuse of longer text forms connected to short text forms). But also we must make it possible for reflection to take place. The "quick-slow" approach to networked content systems encompasses this. We can then turn the two principles to our advantage, by encouraging their opposites context and reflection.

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: , , , , , ,

A Twitter Wiki

As the popularity of short, fragmentary messages grows, I have become concerned the public conversation may lose the capacity for thoughtfulness and reflection. At the same time, I would like to caution those who condemn Twitter or other systems based on micro content to not throw the baby out with the bath water. The long form newspaper article found in the New York Times or Washington Post contains a lot of material used to provide background for the reader, often at the end of the article. Not only is this text boring and redundant to the knowledgeable reader, it takes up previous space. The one thing the web is good at is connecting one piece of knowledge to a broader context of other pieces of knowledge. There is no sane reason to continue repeating background and further reading material in a long form newspaper article when on the web, a writer can simply link to the information.

The brief, concise texts of micro content can be connected to many other sources of information, some just as concise (a kind of "blizzard" of small pieces connected loosely) as well as to other longer, deeper and reflective sources. This loose, disjoint and connected type of writing is simply the network native way of writing and connecting information. It is beneficial, as long as both kinds of writing and forms of content are available and can be connected.

My concern is really with lowering the barrier of entry, enabling and encouraging those longer, deeper and reflective forms of writing. I recognize that there are benefits from shorter, more concise writing, which leaves redundant, expansive or source material hidden (properly) under a link or conntected through a network of tags or a network of people. Perhaps will will see fewer long texts divided up by headings and sections and more smaller texts connected together through search, tags and linkages into a variety of wholes, determined by the user's interests and needs.

About ten years ago, I was fascinated by the idea of a long text (article, book, etc.) entirely constructed of fragments, similar to the kind of texts you see posted on Twitter today, which could be freely rearranged similar to those magnets used to write poetry on refrigerator doors. I imagined that instead of writing a large text with a single coherent whole, they way books have always been written, the pieces of information on a topic could be combined to create a "book" in innumerable ways by rearranging those pieces.

It would be like taking all the paragraphs in a book, shaking them out on to the floor, and then allowing or enabling those pieces to be rearranged for each reader or interest. The pieces would be tied together by keyword or by search result and only lastly by links. I coded a small prototype application called Strands to test the idea, but work and life caught up with me and I shelved it. I was and am still surprised by the ease and rapidity with which people have adopted Twitter.

Not only are people using Twitter, despite the fragmentary nature of its texts, they are participating creatively in shaping the technology and usage of this kind of system based on fragmentary texts.

The use of tagging emerged spontaneously from the user base. Using "hashtags" brief texts can be connected to media, such as images and video, with the tag at the center of a network of content.

Also, I've noticed users are starting to fit the tag word into their text. Some examples are:

"Young Nebraska farmer explains how limiting direct payments would affect his #farm at www.nefb.org"
(Tweet from http://twitter.com/farmradio)

and

"farmanddairyGet four issues of #Farm and Dairy FREE! Click on the big promo on our home page: http://www.farmanddairy.com/"
(Tweet from http://twitter.com/farmanddairy)

At the heart of my Strands prototype were small texts connected by keywords. I wanted to create the lowest possible barrier of entry, so a user could create a keyword (essentially a tag, I called them "strand words") just by writing it into the text. In this system, what was essentially a tag was created by writing it (texts were scanned on post or edit for the presences of tags and any new ones added to an index), which is hauntingly similar to how people have started using tags on Twitter. They started out adding the tags to the end of a message, but have now begun incorporating them directly into the flow of text. I hesitated to continue working in this direction on Strands, partly because I expected people would find the tags sprinkled through the text troublesome.

My current interest is in providing tools or ideas that will encourage and enable a society addicted to short messages, however beneficial they may be, however native to the networked way of writing and reading in a connected fashion, to engage in greater contextualization and thoughtful reflection, to enable collecting some of the knowledge quickly flying by in the "Twitterverse" into slower, more reflective pools of knowledge, like eddies on the edges of a fast flowing stream.

The first tool I want to build is a "Twitter Wiki" enabling anyone to associate a text of any length with a Tweet and anyone to edit it. If I have the energy, I will post any experiments on my site or at least attempt to describe it.

Labels: , , , , , ,

Social Micro-blogging and bookmarking

It hadn't occurred to me until I saw it being done that social bookmarking and social microblogging are both popular in part because the create flows of information edited and curated by experts.

One good reason to follow the bookmarks of a user belonging to a social bookmarking site is simply it is a source of good information. The bookmarks ought to be high quality and relevant in the expert's topic area.

It makes sense to follow the tweets on the homepage of a user belonging to Twitter (or any microblog system), because they represent a selection, an inclusion, of edited and curated information for free, usually from an expert.

A Twitter homepage combines the posts from a user's followers, which amounts to multiple levels of curation. Suppose a number of people practicing organic farming create Twitter accounts and post information they feel is important. Suppose then an expert in organic farming, perhaps an editor of an organic farming and gardening magazine becomes a Twitter user and then follows the tweets of those practicing organic farming. Suddenly, this user's homepage becomes a fountain of curated knowledge on organic farming.

The same phenomena occurs (without the vertically integrated curation) on social bookmarking sites. A social bookmark system is an example of horizontally integrated curation, since many hands organize, but one result does not necessarily flow into another, progressively filtering content. What if you could follow another person's bookmarks and aggregate the bookmarks of all your followers onto your profile page?

The question presents itself: Where did I go wrong?

I had thought of bookmarking as bookmarking and blogging as blogging, each highly personal, one organizing content for an individual's own use and the other for publishing (in a mostly traditional way, I tended to scoff at the idea of blogs as conversations, but they are, just not as flexible and immediate as microblogs). What I missed about the social aspect was the flows of information they create, which are curated. I envisioned years ago the idea of users collaboratively organizing the content of a website, but that wasn't all that great an achievement, since that is essentially what wiki users have been doing from day one.

I thought about applying it to all the content, thinking perhaps I could Tom Sawyer-like, get others to organize my stuff, but my second thought was, who would want to do that? I think most efforts to get users to organize content will fail and I think most efforts have, except where the social ingredient is in the mix. Collaboratively edited social content sites for news, bookmarks, short messages, do work, but through self interest in the flows of information they create. They become platforms for self-promotion.

There is no incentive for you to come organize my site. Flickr allows users to tag other user's pictures, to essentially organize content for another user, just as I thought would be possible, but I see no evidence it is being used generally. Except for the Flickr Commons, where there exists an incentive to surround historically important images with context, to tell their stories so they will be preserved and meaningful for society, where local historians can demonstrate their knowledge and where self-promotion is possible through the organization of other people's stuff.

Despite seeing the social ingredient at work in wikis and despite seeing the essentially (and pioneering) social organization of the CPAN library, I missed its importance. It's importance comes from the curated flows of information created by the social organizing, editing, contextualizing with narrative, selecting and filtering, that occurs in social media systems.

Labels: , , ,

Twitter as curated news feed

When I follow another Twitter user, their posts (Tweets) are included on my homepage, which is public. This amounts to creating a kind of "newspaper" news feed of content "curated" (selected and managed by me). The problem with this, is for example, that with our farmfoody.org Twitter account (established primarily for communicating announcements to users) is that it could become a kind of "mashup" of farm-food related news by following Twitter users posting on those subjects. However, that would result in clutter and chaos, since there is no way to organize the flow of content onto my homepage.

What is needed, is a way to tag posts. It would be nice if posts could be tagged according to topic and each tag converted to a tab, which would separate the streams of information, so there could be a #farm and a #food tag (using the hashtags convention) and a Farm and Food tab would appear on my homepage, allowing readers to chose the topic they are interested in following. I suppose they could just follow the individual sources, but what is needed is a curated aggregation to enable Twitter users to follow an "edited" flow of information through Twitter (like Reader's Digest?, it might even be possible for Twitter users to give a thumbs up/dn vote on what content should appear in a particular flow or to collaboratively tag).

If I could categorize posts based on farm or food topics, it would be useful to me and my followers. If the users I am following could tag their posts, it would be very similar and I would be relieved of some work (of course, merely following does in a sense create the mix, but it is all jumbled together). It is not important who organizes the content as much as it gets organized with the least effort possible.

I don't know if anyone is working on something like this, but it seems rational that Twitter would be working on some internal mechanisms for organizing that flow. The hashtags solution appears to not be scalable, since it requires following their user account (in order to scan for tags), more of a prototype.

Labels: , , ,

The Social Book

Should books be a calm refuge from the hubbub of the network or should they be part of the flow with constantly updated social activity right in the book? As ebooks become social that is an important question. Do people want to curl up with a good book to get away from it all, or will they want to constantly stay in touch with the author and other readers? I do not have the answer to that question, but it is clear the next step in electronic books is to make them truly dynamic, with more than just the ability to search full text or submit HTML forms. The next step in ebooks will be the integration of the social network, bringing community inside the ebook. As we begin to read books on devices ranging from the iPhone to Kindle, the possibility for connecting the text to its context of authors and fans, of creating a social context for the work in the same way Twitter creates a social context, grows.

A thought occurred to me reading about Why is OpenOffice "profoundly sick"? http://news.cnet.com/8301-13505_3-10129764-16.html that development on an office suite is no longer challenging (and has not been for a decade) to most coders. I believe this is why there is so little interest in coders working on it. But making OO into a platform for ebook publishing and integrating the social network into document creation, sharing and reading,

This is already happening piecemeal. I've gleaned information from histories of chats I've participated in, collected postings from forums, email, to use in a document and I see others doing it as well. We already are writing in a social environment. Wikis are another existing socially networked writing environment and have been since day one.

If you look at the emergence of source control services like Assembla or Google code, online "forges" for producing software, I don't see why that can't happen with ebooks. It might be a better approach than creating a desktop application.

Think of how one could incorporate content from Twitter flows, Flickr photostreams, every fourm thread, QnA question answered well, everything gleaned from the flow of socially networked information directly into ebooks through some curation and publishing process. Anything can become an ebook, and ebooks can be small or large, read on the iphone or Kindle.

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: , , , , , , , ,

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: , , , , , , ,

Facilitating the Conversation

I was prompted by something Andrew Shafer of Reductive Labs said (on the FooCampers list, so I won't reproduce it here, since it was forwarded to me) about the quality of communication among software developers. He was talking about how communicating the overall design and intentions of the project is vital, so the developers are not left guessing about how the application will be used and what its architects think it should do. What is important is the existence of a conversation between the leaders of a project and the developers writing the code. This hits very close to home, because our farmfoody.org project is essentially there to improve the flow of information between producers and consumers of food, to enable a conversation.

It occurred to me the solution is to throw away the flash cards and bulleted design specifications and just facilitate the conversation. Why not use social networking tools for developers to communicate? (You can get a sense of another approach from his post Working Together… with Techology). This sounds like an amazing experience using software much like the "multiplayer" networked text editors (SubEthaEdit) that have cropped up in recent years that let a group of connected people edit a text document .

An equivalent of Twitter for programmers would be interesting. A social activity and message feed to keep everyone in the loop. Why not post messages about activity into a feed. This already happens with users signed up to version control services (like Assembla or Sourceforge), but through email. It needs to be through a unified social feed or "wall" some call them, where notifications about code commits, coding activities, etc. can be distributed to a group of "friends" or "followers" of the thread of development. Instead of each project posting a feed, each developer would post a feed. Or perhaps both, with users being able to "follow" a project and also keep up with "friend" developers, which could cut across projects. The latter would be useful because it would help developers keep an eye on allied projects or perhaps a mainstream of code their project fits into, merely by adding that project or an individual developer from the project to their friends (or perhaps they would be "fans" of the project to keep personal friends separate...the terminology doesn't matter).

It should be very possible to build a social "stack" on top of existing "pastebin" applications to achieve this.

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: , , , ,

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: , ,