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.

Namespaces for Tags

I've been thinking about "namespaces" for tags lately. Sometimes tags become too random, disorganized, or numerous to be relevant or useful. One way of cutting through the clutter is to create more than one set of tags. I've seen this on at least one website, sprig.org, which offers "togs" or an alternative set of tags to classify posts by. The difference is these tags are restricted to a particular concept, types of ecology-related terms, such as "organic." What this secondary set of tags produces is in reality a set of tags under another namespace "Ecology."

It is possible to organize tags into namespaces, each representing a concept. This would not be imposing hierarchy on tags, but creating nodes representing concepts. So that Ecology might contain organic, carbon free, sustainable, etc. and Mathematics might contain number, equation, factor, etc.

I organize my photographs in Photoshop Elements using tags. I chose to avoid using tags like categories and instead only create tags for qualities of the image. I try to create tags that describe the image the way an art historian might classify works by their elements or an archivist might classify images according to social use. An image depicting people at work is an "occupational" for example. A painting might be "abstract" and "nature" and "patterns."

Here is a partial list of my tags. I try to create tags for

a) Qualities of art, such as Landscape or Pictorialist
b) Things that can be seen in photographs, concrete like Aircraft or abstract like Patterns
c) Subjects, categories of subjects, concrete like Nature, Sky or abstract like Time


Abstract
Aircraft
Automobile
Birds
Butterflies
Concrete
Flowers
Impressionist
Landscape
Leaves
Nature
Patterns
Photos
Pictorialist
Plants
Rain
Shadows
Sky
Snow
Time
Trees
Urban

I can see some benefit in putting these in a namespace, limiting the tags in this space to reduce clutter. For example, tags on Buddhism would not be found in great number in this set (unless a) you have a lot of Buddhist photography or b) you attach tags from a Buddhist namespace and then they wouldn't be in the set). I don't know how successful namespaces might be for tagging. Programmers love namespaces, but ordinary people find them confusing. I like the idea of tying namespaces to concepts.

I think namespaces would come in handy when choosing tags from a list, like when you show all labels in Blogger's interface. You get one long unreadable list of every tag you've used. Sometimes I love tags when I can just enter the key words that are in my mind while writing a post, but sometimes I hate them when what I really want are categories. I read an article the other day by a graphic artist who designs for the web who continued to use the web safe palette long after it was not technically necessary. He argued that artists tend to choose colors from a comprehensible and memorable palette of colors, such as the Pantone set or the set of colors defined by the various oil pigments. With 16 million colors there are far more colors than anyone could recall or discern. For every "olive green" there are hundreds of colors in between that and the next discernible color moving in either direction on the color wheel. It helps to have a standard color when envisioning or communicating "olive green" to others. I think tags are afflicted with this problem.

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.

SpeakUp: A Transcript Markup Language

What is SpeakUp?

A simple text markup language for transcripts of moving pictures or video including a markup language for annotation.

Overview

When the Folkstreams project required a way for filmmakers and academic contributors to create and maintain transcripts for films archived and presented through the Folkstreams website, I decided a simple text markup language would be the best way to store and edit transcripts.

A transcript markup language defines a series of conventions for formatting text (like wiki text) that is translated into HTML for display. SpeakUp was designed to contain as much content as possible and preserve meaning for possible later conversion into XML or database form.

Speakup is implemented as a module extending the PEAR Text_Wiki library text translation module and is a requirement for use.

Although development and documentation of Speakup is not complete, it is in use on the Folkstreams website.

Speakup, including all markup, code and documentation is open source and released under a GPL license. I apologize for the brevity of this document, but the best way to learn SpeakUp is to download the package and experiment with it. Download.

Some Background

Some background on why transcripts are important. As the Folkstreams project was developed, project director Tom Davenport and developer Steve Knoblock, in a series of discussions, arrived at the conclusion that transcripts are essential to searching, finding and understanding films online. Two points emerged: that transcripts are a rich source of indexable text that help make media searchable and that more importantly, transcripts are a rich source of conversation and debate.

Frequently notes are more informative and interesting than the work they annotate. We discovered this was true for film transcripts (see Sadobabies for an example of a conversation going on in the notes about the nature of folklore). Although there are sophisticated means to capture the dialog of a moving picture and render it to text, these transcripts are inadequate. They lack annotation. They lack expressive quality of a transcript edited by a knowledgeable person. They are in a sense, a travesty, like an OCR'ed copy of Dickens left uncorrected.

Open Flash Charts

I recently discovered a wonderful new open source project for creating Flash charts. It is open source, non-proprietary and best of all for a non-profit on a tight budge, it is free. In the last week I deployed Open Flash Charts after integrating the package into our Folkstreams content management system. For users of our system (through their personalized area My Folkstreams), this will be a great improvement in the quality of charts. We make the statistics on visitors and video views available to filmmakers, and the Flash charts are simply beautiful compared to our old ones based on phplot.

You can download the code for OFC (Open Flash Charts) from their homepage. It is the work of John Glazebrook and he must be a designer, because the default charts in the tutorial are beautiful and take advantage of the interactive features of Flash. I discovered a few kinks that need working out, but overall, this is an excellent addition to the open source code making up the Folkstreams platform.

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).

A Good Introduction to Yahoo Pipes

A good introduction to what Yahoo Pipes are and the possibilities they offer posted to Read/WriteWeb. Also, a simple, clear, concise explanation of emergence:

It is this automagical process through which elements of a system give rise to a higher order system. Emergence is how physics becomes chemistry and chemistry becomes biology.

Quick-slow: A way to give meaning to media?

I develop the platform for the folkstreams.net website, which is a non-profit archive for rare folklore documentary films. We transfer the films to video and then stream them to the web so they are not lost, molding in some archive never to be seen. Many of our films have not been seen for twenty years or more, one was rescued from a barn. As such, we are strong advocates of open access to archives (and I am happy to learn many other institutions in the folklore world also understand how important access is to a sustainable archive and are using the web in wonderful ways).

To the point. It has always been important for our films to be presented in context. I have always believed that media without context is meaningless, whether that is a family photograph or a documentary film. A photographic image is merely an interesting composition without the information necessary to understand it, to interpret it. All images must be read...oddly enough, since they are the seeming opposite of text, which everyone acknowledges must be read. We teach literacy, but we don't teach the equivalent for images. (What would that be imagacy, photoacy, videocy? That last one sounds too much like idiocy to be comfortable.). A photographic image may affect us as a work of art, or it may present an attractive composition, but beyond that it requires context. The same is true for moving pictures. This is why each film on our website is nestled in a set of contextual materials. I sometimes doubt that many people read them, or read the transcript, but they are there to give meaning to the films, to place them in context so that people may better understand the subjects and ideas presented in the film.

I've wanted for some to build a small content management system where

* Media is on an equal footing with text, but also where media is the centerpiece.
* Media is as easy to work with and place in context as working with text in a wiki.

There is a form, a mashup you might call it, between a Blog and a Wiki, called a Bliki. I had not paid too much attention to this development until I read on one of the advocate's websites that the idea of a Bliki involved a "quick-slow" process. The blog enables a user to quickly write a blog entry, something quick, potentially ephemeral and tied to time; At that moment or any time later, the user may also create a wiki page connected to the blog entry, for slower moving, more thoughtful and persistent content.

I think this would apply perfectly to such a media application, which would be useful in personal publishing and could help small archives (local history and genealogy societies, libraries and archives) manage and create access to their image collections. As volunteers scan images, they could upload them with descriptions as blog entries, then they or others could provide context through wiki pages associated with the image meta data in the blog entries. It would be upload, give a title and description, later come back, drop a wikiname in the description and then create a page. It could encourage local people to contribute memories to photographs, for example.

Today, I actually came across the first example in the wild of someone doing this, someone using the Bliki "quick-slow" philosophy to give meaning to images. "I added Wikipedia links to my Flickr photos..." (http://instones.org/archives/61 2007) This is exactly the kind of behavior I would like a web application to enable and encourage, which would facilitate quick image upload and meta data, but would also enable and encourage placing media in context, as well as supporting tagging for folksonomy. It's more a philosophy than a technology.

Yahoo Pipes

I made my first pipe today at Yahoo Pipes, which takes our Folkstreams recently additions feed and finds Flickr images that correspond to the folkloric subject categories associated with each entry, rolls them into the feed. I'm not sure if I constructed it properly of if it's useful, but it works, the Flickr images do show up in an element of the RSS item for each film.

It's a fascinating concept, although a feed mashup is not a new concept, Pipes is very broad, powerful and slick. It borrows from several novel websites, shades of Ning where users build technology using Lego-brick-like software components. Of course, it's like Unix, a set of simple tools with standard input and output that can be endlessly combined into new, useful tools. It also draws upon open source software development, since others can see how you constructed a pipe, copy it and make it their own to study or build their own tools on.

Pipes is a social network version of a RSS feed mashup service. The idea of mashing up RSS feeds to create a new feed, combined from other filtered feeds is nothing new. But sharing the feeds and the construction of feeds with other users in a social network environment like social bookmarking, etc. is novel. You can do the normal social networking things, aggregate most popular pipes. Any kind of content item can be social networked and then the aggregates derived from that usage data.

It definitely has shades of open source since you can see how any pipe is made; shades of wiki in that you anyone can study, edit and build the application from within the application through a language. It is similar to emacs or even Blender (which exposes its interface and engine to Python, so new interface elements and functionality can be added by users). Users becoming software builders is a growing phenomena, just as wiki showed readers could become authors, all part of a general trend toward what is called professional-amateurism.