What Tumblr Should Do: #1 Follow Outsiders
I am inaugurating a new series here: What Tumblr Should Do. I am simply going to offer suggestions of things that the folks behind Tumblr should implement or change.
#1 Follow Outsiders
Tumblr has a large and growing community of users, but it doesn’t include everybody, and probably never will. There are many folks out there that I would like to follow, but since they aren’t using Tumblr I can’t just click a follow button to start having their posts magically appear in my Tumblr dashboard. But I would like to.
Yes, I know I can follow their RSS feed, or go back to their site periodically, or use any of a dozen other approaches. However, that’s annoying, since I want to experience these folks as if they were posting in Tumblr. I like the Tumblr experience as an active reader and curator: I want to be able to easily follow their insights in the Tumblr stream, and not have to wander around the web. It makes reposting easier and liking possible. And I deeply dislike the sterility of RSS readers: I don’t want to be an RSS readerer, I want to tumble.
Of course there are a list of issues that arise, but at the very least Tumblr could implement a first version by allowing me to add the RSS feed of an outside blog to a list of outsiders I want to follow. Tumblr could instrument things so that when those outsiders post and their RSS feeds are updated, the stories would be parsed and placed into my dashboard.
I think the most sensible way to do this — technically — would be to create a ‘ghost’ account for any outsider that any Tumblr user follows. If multiple Tumblr users want to follow the same outsider, there would be only a single update going on. And then all the reblogs, likes and follows could be associated with the ghost account.
At some point, someone with such a ghost account might opt to switch over, and claim the account, and perhaps abandoning their outside blog. Who knows? But I know I would benefit from this feature and so would other Tumblr users, even if it doesn’t necessarily swell the ranks at Tumblr.
Shouldn’t we open the doors and pull the wider world into Tumblr?
Update: 9:20am — @kthread answered ‘+1 I would definitely use this, and would in fact pay for it as a premium Tumblr service’
Update: 9:47am — @lelapin points out that Tumblr has a feature designed to allow import of RSS feeds. I recently tested that approach, and it just doesn’t work (see Fossilized Tumblr Feature: Importing Via RSS). Besides, if it did, it wouldn’t work as I wanted. And of course there is no economy of scale: if you and I and a 1000 others all import Umair Haque this way it would be 1002 separate RSS imports, and there would be no convergence of reblogs, likes, etc. No, it should be implemented inside Tumblr in an intentional way.
Google pulls the rug out from under web service API developers, nixes Google Translate and 17 others | ZDNet
Two on this list of Google APIs that are ‘deprecated’ — meaning that they will be shut off in the not-too-distant-future — caught my eye: Feedburner API and Wave API.
Wave has proven to be such a one-eyed goat that Google announced its shutdown back in December 2010.
But this series of events in the history of Feedburner is the sort of thing that makes me scratch my head (via Wikipedia):
On June 3, 2007, FeedBurner was acquired by Google Inc., for a rumored price of $100 million.[7] One month later, two of their popular “PRO” services (MyBrand and TotalStats) were made free to all users.[8]
On August 15, 2008, Google completed migration of FeedBurner into its group of services.[citation needed] Publishers who have completed migration will access FeedBurner via feedburner.google.com.
On May 26, 2011, Google announced that the FeedBurner APIs would be deprecated, leaving the long-term availability of an API for FeedBurner uncertain.[9]
Perhaps there’s no better example of how quickly we have caromed past a social web based on RSS to one based on streams. And there’s Dick Costolo, a founder of Feedburner and now CEO of Twitter, the canary in the coal mine.
(via Chartier)
Messiness At Scale
I stumbled onto a hilarious but unenlightening Twitter flame war instigated by Dave Winer — the Godfather of RSS — in response to MG Siegler’s ‘RSS is dead’ wisecrack.
At the risk of putting my fingers in the sausage machine, let me add a touch of nuance:
- RSS has declined in use, as web heads shift their source of ‘things to read’ away from RSS readers — like Google Reader — to tools like Twitter and Flipboard.
- The role of RSS in web infrastructure is being threatened by non-RSS based architectures, like Flipboard’s. That product ignores RSS and fetches through the URL to get directly at images, text, and other content.
Winer is ideologically opposed to closed, proprietary approaches like that of Twitter (or, by extension, of Flipboard):
Dave Winer, What I mean by “the open web”
Anyway, here’s what I meant by “open web.”
I meant not in a corporate blogging silo.
If I put stuff in Twitter, the only way to get it out is through a heavily regulated and always-changing API. It will change a lot in the coming months and years. It will certainly narrow more than it expands. I feel very confident in predicting this, because I understand where Twitter is going.
If you put stuff in Facebook, it’s even more silo’d than it is in Twitter.
However, if you put stuff in WordPress, even on wordpress.com, you have full fluidity. You are not silo’d. You can get data in and out using widely-supported APIs that are implemented by Drupal, Movable Type, TypePad, etc etc. At least there’s some compatibility. And in a pinch you could probably move your content to a static website and have it be useful.
If you write in static HTML and RSS, you’re very portable, there will be no lock-in at all.
So to the extent you’re locked in, that’s the extent you are not on the open web. The perfectly open web has zero lock-in. The silos are totally locked-in and therefore not on the open web.
Winer’s complaints are about control of our content: that we should be able to easily manage what we write. It’s a political argument.
But his points fly in the face of innovation, where a Twitter or Quora or Facebook create very different — and not solitary — models of open social discourse, which need to be managed in ways that are different from old school blogging. It’s not every man for himself, anymore. Time is a shared resource on today’s web: our time is not our own, anymore. And that’s largely good.
I liken this problem to the trade offs inherent in living in large cities versus towns or the country. There’s more noise, bigger crowds, and longer lines at the DMV: more things that we can’t control, or where our control is restricted, relative to folks living in bucolic Des Moines.
Only in cities we get superlinear scaling, as Geoffrey West and his colleagues have shown:
Jonah Lehrer, A Physicist Turns the City Into an Equation
When a superlinear equation is graphed, it looks like the start of a roller coaster, climbing into the sky. The steep slope emerges from the positive feedback loop of urban life — a growing city makes everyone in that city more productive, which encourages more people to move to the city, and so on. According to West, these superlinear patterns demonstrate why cities are one of the single most important inventions in human history. They are the idea, he says, that enabled our economic potential and unleashed our ingenuity. “When we started living in cities, we did something that had never happened before in the history of life,” West says. “We broke away from the equations of biology, all of which are sublinear. Every other creature gets slower as it gets bigger. That’s why the elephant plods along. But in cities, the opposite happens. As cities get bigger, everything starts accelerating. There is no equivalent for this in nature. It would be like finding an elephant that’s proportionally faster than a mouse.
I maintain that Twitter, Facebook, and other ‘closed’ systems are really something else: they are dense and complex social systems, more like modern cities than Web 1.0 publishing platforms. And, like cities, there is more going on, less being controlled by specifications like RSS, and the food is better, the music is better, and there is more dangerous sex taking place.
Brian Eno uses the term ‘scenius’ to define the quality of the great cities, their ability to foster deep shared understanding and purpose for large networks of people. This collective intellect arises from messiness at scale, not carefully mediated and clearly defined standards.
Said differently, the best food comes from cities with the highest number of health code violations, and the best art is produced where the largest number of building code infractions are found.
So, if you are looking for clean bathrooms and no traffic jams, stay in Iowa. But it is in cities — dense, loud, unplanned, messy — where the breakthroughs emerge.
Getting back to the specific case, here, let’s look at Flipboard. Flipboard rejects the use of neat-and-tidy RSS, and reaches through the URLs it finds in Twitter to directly paw the text, images, and links placed into articles and posts, and then it chooses what to display based on a proprietary algorithm inside the guts of the app, not based on the publisher’s RSS specification.
Flipboard, Twitter, and other dense, complex social tools create a messier world, one that has superlinear scale. The tradeoff between complete ‘openness’ (or individual control of information and its experience) and superlinear social density is one I am willing to make. And so are all the users of these tools, or should I say, residents of these cities?
The Defection Of RSS Reader Readers
Everyone is stressing the wrong part of the dynamic about Bloglines being shut down. It’s not that RSS is dead, or that RSS readers are dead, it’s the defection of RSS Reader readers — we, the edglings — from those tools to other ones:
[…] people no longer seem to be abandoning certain readers for others—or for other ways to access those same feeds. Instead, they appear to be abandoning RSS readers as a way to read the news altogether. Hitwise, for instance, tells us that visits to Google Reader are down 27 percent year-over-year, while visits to Bloglines are down 71 percent year-over-year. comScore (NSDQ: SCOR) figures show that traffic to Bloglines has largely stagnated:
Likely to blame is that people are increasingly turning to services like Facebook and Twitter to manage what they read instead instead of RSS readers. As Hitwise’s Heather Hopkins wrote last February, Facebook accounted for about 3.52 percent of all visits to news and media sites. Google Reader’s (shrinking) total back then stood at 0.01 percent.
Indeed, in its announcement, Bloglines similarly blames broader trends for its demise, saying, “As Steve Gillmor pointed out in TechCrunch last year, being locked in an RSS reader makes less and less sense to people as Twitter and Facebook dominate real-time information flow. Today RSS is the enabling technology – the infrastructure, the delivery system. RSS is a means to an end, not a consumer experience in and of itself. As a result, RSS aggregator usage has slowed significantly, and Bloglines isn’t the only service to feel the impact. The writing is on the wall.”
I don’t like the Pez dispenser feel, where all posts are like another, and you assume the role of a pigeon in a Skinner box, hitting the button to make the pellets roll out.
I have seen this coming for a long long time. In December 2005 I wrote a post, RSS Readering: Why RSS Readers Are No Good For Me (And You, Too, I Bet), where I spelled out reasons that RSS readers were the wrong way to handle streams of information, and where I coined the term ‘RSS Readering’. I wanted to break out of the inbox-based metaphor, and I was struggling to express my hopes for something stream-based:
I tried them for a time, and then dropped out. These annoy me for similar reasons: I don’t like the Pez dispenser feel, where all posts are like another, and you assume the role of a pigeon in a Skinner box, hitting the button to make the pellets roll out.
I have been lusting for something, a new solution, that actually parallels my most rewarding reading experiences. The way this generally works is like so:
- I stumble across some link, or reference — perhaps in an email, or in the midst of reading a post in a browser — and I decide that I would like to invest some attention to this concept, or meme. Note: I am not just deciding to click a link and go to a specific page — which is all typical browsers do. I am deciding to investigate the theme, thread, meme, or whatever, and assimilate and collate information about it.
- I might click on tags embedded in the post, that take me to Technorati, or I might simply decide to search at Technorati or Del.icio.us for references to the piece or for tags to the topic or the names of individuals writing about it.
- I might follow backlinks, from the post back to earlier sources: other posts, or articles.
- I might ask specific contacts of mine what they know about the object of my interest.
- I might write a post, summarizing what I have uncovered, and offering some thoughts on the subject.
[…]
What I would rather have is what I imagined Flock might be (and well might be, in later incarnations): a browser-based solution, perhaps a suite of plugins, that augment the browser-based “readering” experience. One part of that might be a buddylist-ish sort of minimal RSS tool that would simply remind me that people I like have posted something somewhere.
[…]
The rest of the browser modules might include these:
- A tag browser: given a tag, or a boolean expression involving tags, present an ordered list of sources (both authors and blogs). This could be a Technorati plug-in, perhaps.
- A backward link and forward link sniffer: give the current webpage, collate other pages pointing to that page, and a list of the pages referenced. This I envision as something like the radar widget found in video games, in a way. But instead of being displayed in a circle, two ordered lists would be fine.
- A Del.icio.us module: given the current page, who of my friends has bookmarked the page, and what have they said? And I would like to get away from the javascript contraption that I use for Del.icio.us now, where bookmarking a page moves me to Del.icio.us, and creates a problem with use of the back command.
- A journaling module: I would like to drop an anchor in my clickstream when I decide to start some exploration and to drop a second one when I stop, and be able to retrace my steps at some later point, or to pick up the thread again, and add more stuff to it later on. I have written a bunch about “search as a shared space” vis-a-vis various services like Jeteye, but I would really rather have something embedded in the browser experience that I could also publish in some way, to allow it to be shared with others.
- A IM presence module: I’d like to be able to share the location I am currently browsing as my iChat/AIM presence, and I would like to have my circle of friends do the same. Of course, people would like to turn this off when they are reading Fleshbot (not me, but others might), but in general it would be a simple source of new sources of clueful information.
There’s more modules that could be conceived, but I think I have waved my hands enough to get across what is profoundly off about RSS readers: they don’t work the way I read. I need support for active reading, or “readering” as I dubbed it, which is a very social activity, not a solitary one. I am no pigeon in no cage.
I was starting to anticipate the way that future dynamic social tools would supplant the inbox, static model, and it has happened. And now the old RSS tools are being left behind as we defect to better ways to share online.
Better Social Plumbing For The Social Web
My recent talk from the Web 2.0 Expo in Berlin, which I retitled “Better Social Plumbing For The Social Web” instead of ‘Better Media Plumbing…”. I include the notes that I prepared, with minor tweaks.

My topic is not new — in the sense that I started writing about it a year ago. But I think it is of growing importance.
The basic premises that underlie social media — the fundamental relationships that link authors to the community of readers — are changing in the face of new and different social tools. In a sense, I am chasing the elusive question about where community resides, once again.
In this presentation, I plan to explore the root causes of today’s social media plumbling — the stuff that makes it social — and to outline the stresses that new social metaphors are creating. Lastly, I wave my hand at where it might all be headed.

I am best known these days for my writing (and the thinking behind it) at /Message and other blogs at www.stoweboyd.com. I have been involved with the development of various interesting ideas, like social tools, flow applications, workstreaming, web culture, edglings, microblogging, and new localism. I have spoken at dozens of conferences in the past ten years, like Lift, Reboot, Web 2.0, Enterprise 2.0, Defrag, Supernova, Under The Radar, Mesh, Next, and many, many others.
I work with a lot of start-ups building social tools, and larger companies trying to make sense of them.
Apologies. It was blogging that did this to me. No neat conclusions. A barrage of conjecture, wisecracks, and one-liners, disguised as a presentation.
My work is social tools, but my goals lie beyond.

We have inherited the Web 1.0 vision of the Web as a giant network of documents, linked to each other, where you can wander forever.
Where are the people? Oh. It’s the authors. They are people. They create links, but there are not in the immediate foreground. It’s documents, all the way down.
So in the Web of Pages — Web 1.0 — pages are more important than people.
And why are we here? “I must be here to read about things and follow links” since that’s what is the most natural thing to do, not to interact with people.

The Web of Pages wants us to be hunter/gatherers. We search, find a link, click it, see if it’s want we want, if not, we keep following leads.
It exploits the spatial sense in our minds.
People create the links that connect pages, asserting relationships between the info on the pages, and by extension, relationships between the people reading and writing the various pages. But it all seems pretty far away from human conversation. You write something, I find it, and write my own thing, and point at yours…. Its more like sending letters than conversing.
Yes, Google builds its page rank based on people’s actions — creating links and the identity of who created them — but all that seems way down in the subbasement, far far away.

Links are obliquely social, but direct conversation — through chat, social networking messages, and (most central to our subject today) blog comments — is where web media really become social media.
Asynchronous in nature, but can be near real time.
A blog is a long-lived repository of discourse, a place to ask questions, contend, agree, make suggestions, enlist support, and offer counterpoint. Nearly every possible sort of conversational interaction can be shoehorned into the lowly comment thread.
This is one of the reasons that the blogosphere has gone from a fringe phenomenon in 1999 to mainstream in 2009, where the leading print media outlets of the pre-web world have embraced the blogging paradigm at a fundamental level.

Social media is distinct from pre-social media in many ways — web based, individual voice dominates, etc. — but it is the social dimension that defines the difference. Social media is contrived (at least the best instances are) around the premises of open discourse between individuals.
While the publishers of blogs retain (in general) the ability to moderate comments, largely the model seems open. And the authorship — based on the identities of the bloggers and the commenters — makes the relationships that seemed so oblique in web 1.0 much more obvious and direct.
The heart of social tools is the individual, which is why I say social = me first. In the world of blogging that translates — not too well, actually — into ‘bloggers first, commenters second.’

The current baseline of blog technology puts very strong controls into the hands of the blogger, and hardly any in the hands of the commenters.
What sort of sociality is going on in a comment exchange? It’s a strangely unequal forum, where the blogger has nearly absolute controls, and the commenters — even in some sort of collective fashion — have no power. The blogger can delete any comment, or mark it as spam, while the commenters can’t change a single comma in the blog posts they comment on. (Of course, some commenters become bloggers themselves, and then the comment exchange becomes slower and distant, cross-linked by trackbacks or URLs, but pulled out of the comment stream.)
This asymmetry in control and ownership — who gets the revenue from the blog ads? — has ramifications throughout the web. For example, the page rank for a blog is attributed to the writing skills of the blogger, but it is the links that make the rank, not what is on the page. What is on the blog — the posts and the comments — are what lead to strong reputation for a blog, and that is due to the commenting — the sociality at the blog — but the author claims all the benefits, including all the revenue.
It’s interesting that social media is often heralded as proof that companies have lost control of their ‘message’ but at the same time that blogging keeps so much control in the hands of the blog publisher.
And there is the ‘comment dispersal’ problem, where very active commenters wind up with their participation spread all over the web, and no collation of their contributions.
This is one of the reasons that solutions like Co-comment and Disqus have been making ground, because an individual’s stream of contributions can be pulled together somewhere, and in a sense ‘owned’ by the participants and not just the blog publisher.

The seed for the change in the blogosphere was a seemingly small advance.
RSS feeds are a way to receive the posts from blogs without visiting them. Instead, using an RSS reader, a webhead can instead have posts from any number of blogs deposited into an RSS tool, like Google reader. This is a sort of out of body experience, since the user doesn’t hunt and gather anymore, wandering around looking for new information by search and following links. Instead, a steady diet of bite sized morsels simply appear. And generally without the comments.
So the shift to RSS by the most technically hip websters meant that
- they were seeing posts out of social context, without the conversational interaction that made the blogosphere a third place, and not just forty million people standing on soapboxes, and
- over in the RSS reader the former participant — now a reader — is at least one and maybe more clicks away from adding comments. And of course there is a subtle devaluation of comments because they are read less often and harder to get to.
So, people find it easier to take other actions using tools outside the blogs, rather than comment. For example, creating shared bookmarks a la Delicious may seem of higher value for the individual and that individual’s network of friends than writing blog comments.
And right on the heels of RSS feeds, we began to see the rise of other social tools where conversation was the centerpiece, not the sidebar.
And these tools rely on our sense of timing, not a spatial sense. We are not wandering around looking for things to read: instead, things to read just show up in some regular timeframe.

Tools like Digg and Techmeme share a few key characteristics, and define two ends of a continuum. There is a stream of new information that finds its way to the pages of the website: in the case of Digg this arises from individuals recommending pages for others’ attention, and in the case of Techmeme an algorithm looks are the clustering of a short list of A list bloggers to see what is getting the attention of many. In both cases, the user is presented a stream of information, ordered by the observed actions of others.
Here we find the key attribute of all important social tools going forward: the collective actions of some group of people shape — order, filter, embellish — a stream of information. One sort of embellishment is a comment, like the comments traditionally left on blog posts or in bookmarks. But these comments never find their way back to the blogs, if they were sparked there.
Also, the way the sites work feature emergent properties from the community, collectively, that can’t happen on a single blog all alone. On Digg things rise (or fall) relative to others; and on Techmeme stories rise and fall by clustering of authors. In this regard, the evaluation of the value of a single blog post is one of the outputs of Digg and Techmeme.
As a result, participants’ behavior can change when exposed to these tools. It becomes more fun to Digg a blog post than to comment on it. As a reader of Techmeme, you find it unprofitable to comment on blog posts — even of posts currently active on Techmeme — since a/ comments don’t show there, and b/ the comments have no influence on the Techmeme algorithm.

So, there are now dozens of streaming applications — Digg, Facebook, Jaiku, Pownce, Twitter, Social|Media, Threads, Friendfeed, and more — where the social dimension is people interaction in (potentially large scale) open discourse via the ‘follower|following’ model, and without recourse necessarily to blogs.
Once a person begins to experience the dissociation of blogs and commentary — once commentary moves to these streams away from blog comments — it seems odd to go back. Like using a computer that is not connected to the web.
My hypothesis is that people will find it most natural to have the most active conversation where the flow feels fastest: meaning, where there are many people so that any given topic or link creates a great deal of commentary in relatively short order. However, this is an added incentive to comment directly in the streaming app like Digg, friendfeed or Twitter.
There is a cost to leaving behind the community of commenters on a blog, but if a core group defect en masse to some flow app, that community can remain largely entact, with even the blogger coming along.
For example, someone I follow on Twitter posts a Tweet with a link “someone Wrote a new post on XYZ topic. See www.tinyurl.com/y78YD889Ww.” My natural reaction is to click it, and then write a comment in Twitter to @someone, like ‘@someone have you considered the writing of Borges?”
And from the point of view of Twitter use, I am keeping the covenant: I received the message there, so I respond there. But from the blog-centric view, I am breaking faith, since I read the post that was published there, but I am merely treating the blog as a repository for posts, not a centerpoint for community.
So we are seeing a second wave of defection that defines a new era in social media. We defected from traditional mainstream media, where they broadcasted to us as passive members of an audience. And now we are defecting from the Web 1.0 model of social media, where the blog publisher hold all the power, and the world is a feudal patchwork of blog-based communities. We are moving into a era of flow, where blog posts will just another bit of conversation streaming in the flow.

Since there are dozens — and perhaps soon hundreds — of these streaming apps, each with different although overlapping communities, what can we expect in the near, medium and long term?
Near term — tower of Babel as more people find value in one or more streaming conversational tools, the conversation — the third space — will be subdivided ten times over. And less and less conversation will happen on blogs.
Medium term — Comment tools — like Disqus and IntenseDebate — provide a way to pull the commentary from streaming apps back onto the blog posts. I write a blog post, and a handful of people comment on it at Social|Medium (for example), and my future commenting solution would display those comments as if they had been made on my blog, along with comments from other streaming tools and native one from my blog. This fills a gap in the plumbing, but doesn’t really change the experience of people in each of the streams, since they will only see a subset of the total comments.
How does this feel from the perspective of the individual at the micro level?
Once you adopt the flow attention model, things change.
Here’s my desktop, or one part of it. I usually work with my laptop plugged into a 30” monitor, and I do my ‘work’ — blog posts, email, writing, reading — on the 30” monitor. I keep the laptop screen for flow apps. Here, from left to right I have Snackr (an RSS newsticker app), Twhirl (a twitter client), Friendfeed’s RealTime Beta, and Flickr’s new Activity Stream. Another stream I use is Backpack’s Journal.
I am not saying that everyone is going to become me, but the flow model — where pertinent information is filtered by my contacts and finds its way to me instead of me finding it — is simply better, simpler, and less time consuming, so long as you can make the shift from manual to automatic transmission.

In the long term the static inequalities in blogging make it hard to fit into the coming web of flow. We need a world in which comments, posts, bookmarks, and recommendations are really different aspects of the same thing. Why have we devised a web where posts and comments are so different? Or so different from a bookmark?
All of these ideas share core principles: a person authors a post, comment or bookmark. It is created in some context, probably represented by other open windows on the screen or selections on those screens. (For example, a ‘bookmark’ is the storing of a URL for a page, plus a title, a note, and some tags. The same information could be created as a blog post, right? Or a comment is based on some open post or comment, and has a link to the post or comment. And so on.)
In today’s world, the URL associated with anything created on the web is in effect it’s unique ID, but it is a physical location not just a logical handle. Imagine a web in which the physical location of things was simply an archive, a place to access the definitive data and metadata, but otherwise was used principally as a unique identifier. Imagine all these sorts of conversational particles bouncing around the world through a gazillion streaming apps that use various sorts of social and algorithmic models to order, filter, and aggregate the particles in various ways. These bits could flit from one streaming app to another, or users could create a post in one, a comment in another, and see them come together in a post+comment form in a third. In this world, the bits float around and are experienced in the flow apps, and people might never go back to the original URL associated with the bits.
Also in this world, the bits might be owned by the author, no matter where they are streamed. So if I want to, I can put an ad in every post, bookmark, and comment I make. Likewise, when a service creates new value from aggregation, algorithm, or emergent property of some social sling, they should be able to have their own ads in that context, but they should also honor the ads embedded in the bits. Basically, it’s a fractal world, where ownership is associated with the smallest bits, and larger aggregates. But these can travel — even the aggregates — from one streaming context to another. We will need standards for this, of course, but they will arise to meet demands.
So imagine the following scenario: I post an observation about, say, the future of Web 2.0. A few others see this floating past in various streams and create comments linking to my post, or Digg it — which means it shows up in the Digg stream and several others, like a future friendfeed or social|medium. All of these people add their own ads, and when Digg streams voting results (with associated comments) that has Digg ads embedded. A future version of Techmeme notices that my post is collecting a lot of heat, so it creates a story ‘cluster’ around my post and other posts and comments linking to my post (including in the future, the digg object pointing at my post), and Techmeme drops that into its stream, with an embedded ad, too.
While it might be possible to go down, down, down to the URLs associated with these objects, who ever would? Why leave the flow, where the live things are, to look at the river bottom, where all the dead things fall?

“The Internet doesn’t know what it is doing” - Clay Shirky. It isn’t build to push just one sort of thing around, but all sorts of things.
I think this generation of flow apps will move past a static and deterministic model of what sorts of conversational particles exist, how they should be related to each other, and what apps can show which ones — to a much more fluid model, where all sorts of new associations can be made.
We need to agree on the metaphor of the web of flow — of the bloodstream — and then people can create all sorts of particles that can be streamed through it, and we can get to a more egalitarian social medium that we have now, one that is firmly in the Web of Flow, past the Web of Pages.
There have been a few posts by various folks who heard the talk (here, here, and here), and I think a recording will be posted at http://dogearnation.com/ on Monday or Tuesday. The slideshare.net version can be accessed, and the comments at the Web 2.0 Expo site, too.

Steve Gillmor on Idiot Wind
Steve Gillmor says I was way off with my recent post about RSS (Reads, Not Feeds). (In fact, he titled his post, Idiot Wind, which might be his characterization of my speaking voice, but I doubt it.)
Stowe Boyd’s post about RSS is flawed. Flawed in that it is totally wrong. Scoble is right. Stowe is not. RSS will continue to dominate and eventually suck all the oxygen out of the glorious Web as we currently adore it. We as in Stowe. What possibly leads Stowe to the conclusion that RSS will not absorb all of the wonderful (sic) Web characteristics like blogrolls, whirling beanies, and other smoke and awe? RSS is the Web, Stowe. It’s the Web on steroids. It saves time. It wins.
It’s a wonder that you still know how to breathe.
Hmm. As I recall the context was Dave Winer trying to rally support so that RSS would “bust through” if certain fundamental changes take place in the Web, including fairly major ones, like centralization of all subscriptions. Dave was responding to Fred Wilson’s opinion that RSS is not “brain-dead simple” enough for everyone to get.
My argument is simple: I don’t like RSS readers, and unless someone comes up with a set of appliances (which could certainly exploit RSS, note) that match the way I like to wander around on the web, I don’t think they will come to replace the foraging mode that I have found to be most productive. I am holding out for something closely allied with instant messaging, where RSS feeds related to buddies would alert me to new posts, and then I could click-through to read them in situ (this is the fabled Nerdvana client I have been wishing for out loud for so long).
And, no, Steve, I haven’t forgotten how to breathe just because I think this first generation of RSS tools are inadequate, even if Robert Scoble’s use of them has become as natural as breathing for him.
Steve Boyd on RSS “breaking through”
Dave Winer is poking at an important issue — How RSS can bust through — building on Fred Wilson’s statement that “RSS has to become brain-dead simple to use.” Fred was writing about RSS as a replacement for many sorts of commercial email — newsletters and the like. Dave is making a case for helping RSS to “break through”, meaning a more widespread adoption, I guess. But, ultimately, I think he’s on the wrong track, based on these points:
- It must be easy to find relevant feeds. Too much hunt and peck is involved. The reason My.Yahoo and iTunes have been successful is that they centralize a lot of the discovery, they make it easy to find stuff you might be interested in. But not easy enough to qualify for brain-dead simplicity. That’s why we’re working on reading lists, trying to drive adoption of the new practice by the industry. If, when you get started using an aggregator, it gives you some interesting feeds, and then as time goes by gives you more, without you having to do anything, that’s going to make the finding of relevant feeds a passive thing. Until you’re ready to take over, you can ride the bus without learning to drive. I think this is going to get us another 15 or 20 percent of web users into the RSS world.
- Subscription has to be centralized. When Microsoft invited me in, in April of last year, to hear their RSS strategy, I think they expected me to object to their centralizing subscription for Windows users; they were surprised when I didn’t. I had already come to the conclusion that subscription had to be handled in the browser, because that’s where the impulse to subscribe happens. We knew this back in 2001, when we implemented the Radio coffee mug that made subscription a one-click operation. The problem of course is that our method only worked for Radio. Any of these techniques is going to work with only one destination, that’s why there has to be just one destination, why subscription needs to be centralized.
Microsoft didn’t go far enough. They only solved the problem for Windows. In 2006 that’s not even a very large part of the world, because a large number of people who subscribe, do it through web-based services like Bloglines or My.Yahoo, and more will over time. The Microsoft approach doesn’t work for them. If I subscribe to something using their desktop service, it only registers with software that runs on my desktop. It doesn’t inform My.Yahoo, for example. Now, Microsoft argues that Yahoo can install a toolbar that runs on the desktop, but come on, we don’t want a proliferation new stuff loading into the OS. That’s how we got in all the malware trouble. We don’t need to open that kind of Pandora’s Box. What we need is a centralized subscription public service. It’s not a technological problem, it’s a political and economic problem. In order for RSS to grow to the next level, tech companies have to stop seeking lock-in on subscriptions.
I’ve suggested to Yahoo that they run this service. Of the top three net companies (the others being Google and Microsoft) they’re the least controversial, imho. All that would be required is that they support OPML export for My.Yahoo subscription lists, and commit to keeping it open for perpetuity. The last part is the hard part of course. Now perhaps we could get a university involved, they have politics too, but people seem to trust universities more than they trust for-profit businesses. Something to think about.
Now once we have a single place for subscriptions, which is a real tall order, then all kinds of services can be built off that. It’s like the domain name system again, and perhaps that’s the way to implement it. We’re lucky that RSS is still a fairly close-knit community, and there is leadership that works, somewhat. The small tech companies and at least two of the large ones (Apple, Google) don’t participate, they blaze their own trails, but the publishing industry and most of the large tech companies are still in the mode of cooperating. So now may be a time it can work. And reading lists buy us some time.
Yikes. Where to begin?
First of all, the problem of finding ‘relevant feeds’ — Dave seems to implicitly believe this is an area that has matured, and that the current notion of Yahoo directories or iTunes music distribution should simply be repurposed. I don’t think so. Just take the example of music and iTunes. iTunes is a great service if you know what you want to buy, but if you are trying to find new music, a solution like Last.fm or Pandora is a lot more useful. Last.fm is a social solution, where the music playing habits of other, likeminded individuals can be used to inform you of music you might like to listen too. I have found my musical horizons greatly expanded in this way. Note that this from-the-edge solution has no center: while there is a giant directory of music at Last.fm, the most obvious way to get at music is through other people. The approach is totally socialized. So the very hard problem of finding stuff that’s good to read on subjects of interest is made somewhat easier: we seek to read what others we respect are reading. So the notion of reading lists has real merit, but why do they need to be centralized? If our writing is distributed, can’t our reading lists?
If Dave means that we are migrating to a My.Yahoo model, where we pull stuff we like onto a page, or into a reader, I opt out. I want to roam around, not be caged in, even if it is a cage of my own making.
If he is implicitly taking the stand that RSS readers are the best and only response to the “information overload” problem (a la Scott Karp’s “Focus on the User, Not the Technology”), I don’t buy it.
Secondly, the notion that subscription must be centralized — why, Dave? The experience of the web is managed a page at a time, as we drift around reading things and following links and searches. The RSS reader experience is a piss-poor way to experience the web, decoupling the sense of place associated with direct experience of blogs and other sites. There is an implicit assumption of efficiency, like Scoble’s contention that he would be unable to consume the amounts of writing that he does if he had to actually browse to the various locations. But that argument is something like asserting that a seven day tour of Europe that takes you to thirteen capitals is “better” than one that only involves two countries. Quantity has its points, but it is not the point.
I believe that we haven’t seen the killer app for RSS yet. It’s not RSS readers — which provide a layer of mediation into the Web that is patently bad. I don’t want all meals pre-cut into bite-sized portions. I want to see the stuff in author’s sidebars, their blogrolls, read the comments, look at the pictures. I want to feel the road, spend the extra day in Paris, check out the blog design. It’s a total experience, and the ersatz, deskinned environment inside of RSS readers is sterile by comparison.
The killer app will be the appliance — or set of appliances — that embody the metaphor of travel on the web: that will allow me to more easily stay up to date on ‘places’ and people of interest, to plan and execute ‘travel’ to those ‘places’ on the web, keep notes on my travels, and find new places to travel to.
If efficiencies are the issue, how about precacheing all the places I like to visit, based on RSS notification? Then I can still get out of the RSS reader box, but cut the time involved.
So I think RSS will play a big role in ‘active reading’ but it will not be the experience itself: it will support the experience, in various ways, but not subsume it.
I am really arguing for an esthetic appreciation of the experience of being what I have been calling the “active reader” while Dave’s focus is on the more-or-less industrial scaling of RSS as the foundation of a new model of communication. But I don’t think the centralization of subscription is needed, or even attractive. On the contrary, initiatives like memeorandum show the promise of new forms of aggregation — leveraging RSS under the hood — that reveal social connections and distributed conversation across groups of people. Memeorandum is an example of an experience made much less rich when presented in the RSS readerized format: a stream of chunks with no apparent relationships.
The web is not a pipe, streaming bits onto our eyeballs. It is a world of people, and the social aspects are the most interesting. It is people that are the best source of guidance, advice, and pointers to things worth reading. Throw away your readers, and let’s beg the app makers to come up with tools that make the experience of roaming and reading the web richer, not homogenized.
Attensa Meets Performancing: Something Has To Go
I got a demo of the brand spanking new Attensa RSS products — one integrated into Outlook (which I don’t have, being a Machead), and an online version — and immediately after trying some of the apparently cool features, ran into some stumbling blocks.
Here’s a screenshot of the Outlook version (click for fullsize):

Here’s a screenshot of the Online version (click for fullsize):
The problems I had?
- First, the Firefox plugin that would allow me to automagically discover RSS feeds on pages I am viewing doesn’t come with the free Online version. Apparently you have to have/buy the Outlook version. So I guess you have to manually find and insert the RSS feeds. I have learned that Attensa plans to unbundle this, but at the moment, you’re stuck.
- So, I did add some feeds manually, including importing an OPML file. Seems to work, but creating folders (“categories”) is very counter-intuitive. Apparently the only way to do this is to move feeds to a new “category”?
- And then, the headaches started. I was using the neato web view, which displays the post being looked at in the native HTML, not the RSS stream. I saw a piece I wanted to post about, selected some text, and cnrl-clicked on it — this brings up the Performancing blog editor (which despite its bugs and flaws, I still use all the time). However, the link pasted into the new post in Performancing was to the Attensa Online Reader, not the post being displayed in Web view.
Here’s that screenshot (click for fullsize):
I am a bad test subject, though, since I really don’t want a reader, anyway. That’s a rude approximation of what I really do, which is wandering around, as a forager. But if new tools don’t play nice with the ones I am already comfortable with, they never find a place in my world. I will suspend judgment on Attensa’a attempts, here, until I can see what the toolbar for Firefox holds.
RSS Readering: Why RSS Readers Are No Good For Me (And You, Too, I Bet)
I am constantly fiddling around with RSS readers and various strategies for “RSS readering” — William James remarked that you coin a new word at your own peril, so verbing “RSS reader” may be dangerous for me, but I do so with a plan.
I want to be an RSS reader: by which I mean to say that I would certainly rather (in theory) receive alerts about posts and — perhaps even the posts themselves — within some some window of time of their being posted. However, I haven’t generally liked the various RSS readers I have tried. And I have tried gazillions.
I tried NewsGator integrated with Outlook when I was still (hiss) living on a Windows laptop. Yes, in principle I keep my email client open all day, and, yes, in some way getting email is similar to RSS-transmitted posts. But the email metaphor, of folders and messages doesn’t quite jibe with my experience of browser mediated blog reading. So, ultimately, I dropped it.
The same is true of standalone RSS reader tools, like NetNewsWire and Fire. I tried them for a time, and then dropped out. These annoy me for similar reasons: I don’t like the Pez dispenser feel, where all posts are like another, and you assume the role of a pigeon in a Skinner box, hitting the button to make the pellets roll out.
I have been lusting for something, a new solution, that actually parallels my most rewarding reading experiences. The way this generally works is like so:
- I stumble across some link, or reference — perhaps in an email, or in the midst of reading a post in a browser — and I decide that I would like to invest some attention to this concept, or meme. Note: I am not just deciding to click a link and go to a specific page — which is all typical browsers do. I am deciding to investigate the theme, thread, meme, or whatever, and assimilate and collate information about it.
- I might click on tags embedded in the post, that take me to Technorati, or I might simply decide to search at Technorati or Del.icio.us for references to the piece or for tags to the topic or the names of individuals writing about it.
- I might follow backlinks, from the post back to earlier sources: other posts, or articles.
- I might ask specific contacts of mine what they know about the object of my interest.
- I might write a post, summarizing what I have uncovered, and offering some thoughts on the subject
I then use a variety of techniques to uncover what I am interested in:
But what I seldom do is just sit there reading a stream of posts, based on their chronology, or other intrinsic factors. No, I am on a hunt, skipping from place to place, and these tools constrain me more than they free me.
What I would rather have is what I imagined Flock might be (and well might be, in later incarnations): a browser-based solution, perhaps a suite of plugins, that augment the browser-based “readering” experience. One part of that might be a buddylist-ish sort of minimal RSS tool that would simply remind me that people I like have posted something somewhere. I have a strong bias that this should be implemented along the lines of what the geniuses at 2entwine implemented in Gush, about which I have written a lot in the past, including various posts this year about the Nerdvana client. I have stopped using Gush because I find the Mac version painfully slow, but I loved having a multi-headed instant messaging client that included an RSS reader. I had tried to persude them to strip down the RSS reader to be just an alerting tool, and to conflate the IM buddylist and the RSS alerts into a single list, rather than two separate worlds, but, alas, the Brothers Carr never did get around to those tweaks.
So, when I recently was alerted to RSS reader doings at Yahoo, my mind filled in all the gaps, and I dreamed that dream again. However, while the new Yahoo Mail Beta does in fact include a now conventional RSS reader integrated with it — and it appears to work as it should, given the email metaphor — it won’t actually fit in with the model of readering I am chasing after. However, Yahoo is rolling out feed alerts, as part of Yahoo Alerts (although I didn’t see it running, yet), which may implement part of what I’d like, since these alerts can be sent through IM. But Yahoo and the other major IM players don’t want to provide IM capabilities as Firefox plugins: they want us to use their proprietary clients.
The rest of the browser modules might include these:
- A tag browser: given a tag, or a boolean expression involving tags, present an ordered list of sources (both authors and blogs). This could be a Technorati plug-in, perhaps.
- A backward link and forward link sniffer: give the current webpage, collate other pages pointing to that page, and a list of the pages referenced. This I envision as something like the radar widget found in video games, in a way. But instead of being displayed in a circle, two ordered lists would be fine.
- A Del.icio.us module: given the current page, who of my friends has bookmarked the page, and what have they said? And I would like to get away from the javascript contraption that I use for Del.icio.us now, where bookmarking a page moves me to Del.icio.us, and creates a problem with use of the back command.
- A journaling module: I would like to drop an anchor in my clickstream when I decide to start some exploration and to drop a second one when I stop, and be able to retrace my steps at some later point, or to pick up the thread again, and add more stuff to it later on. I have written a bunch about “search as a shared space” vis-a-vis various services like Jeteye, but I would really rather have something embedded in the browser experience that I could also publish in some way, to allow it to be shared with others.
- A IM presence module: I’d like to be able to share the location I am currently browsing as my iChat/AIM presence, and I would like to have my circle of friends do the same. Of course, people would like to turn this off when they are reading Fleshbot (not me, but others might), but in general it would be a simple source of new sources of clueful information.
There’s more modules that could be conceived, but I think I have waved my hands enough to get across what is profoundly off about RSS readers: they don’t work the way I read. I need support for active reading, or “readering” as I dubbed it, which is a very social activity, not a solitary one. I am no pigeon in no cage.
It could be argued that my needs or wants are wildly atypical — I am a blogger, I have more time on my hands than others, blah blah blah. I maintain that because I am a blogger, and heavily invested in it, I am willing to do manually what others don’t have time or patience to do, even though in the final analysis it leads to a much richer experience of the web.
Now all I need is for inventive souls out there to start building the bits and pieces of my dream world. It shouldn’t be hard for someone to build an RSS alert plugin for Firefox, should it? Maybe someone already has done that. But I suspect that the other pieces of the puzzle have yet to be built. I can dream, can’t I?
