This post can also be viewed on Storify.com.
[Update: My new post addresses the idea that this mashup was an example of “Real-Time Web.”]
I used storytlr to gather feeds from Twitter, Flickr, YouTube and Vimeo to create this aggregated “story” about yesterday’s crash of US Airways Flight 1549 into the Hudson river. Click on the image below to watch the story. The links are “hot”, so click when you see blue.
Storytlr calls itself a “platform to build the centralized you.” Although intended to tell one person’s story, it does a fine job of pulling together bits of information from various “citizens” to create one story.
To make the presentation, I used Twitter Search to find comments with the word “Hudson” from people within 50 miles of New York City. I waded through those comments to find a handful of people whose comments, pictures and video might work to tell a story.
I imported the content from each of the sources into storytlr by simply providing their usernames.
The hard part was editing, or what Tim Windsor calls curating, the approximately 700 bits of information into some semblance of a disjointed story.
Storytlr orders content strictly by chronology. There is no chance to move one piece of information up or down a little to improve the flow of the story.
The result is a stream of moments captured by individual storytellers, the “lifestream” not of a person, but an event.
This particular story says a whole lot about the power of “citizen journalism” while showing how active mainstream media has become in social spaces. (That analysis really needs another post altogether.)
Unfortunately, storytlr does not credit each piece of content. Remember, it wasn’t meant to be used to tell the story of multiple lives.
So here is a list of the sources I tapped to create this presentation. Check them out and follow them if their content fits your interests.
Linked to from this post: