When Dave Shields returned from a recent “software sabbatical” (no blogging, tweeting, or Facebooking since 2009) he wondered: Where have all the bloggers gone?:

I suggest you visit Sam Ruby’s planet.intertwingly.net.

(A “planet” is just an aggregation of blogs. The planet hoster makes up a list of blogs, then puts together a simple program so that, whenever a new blog post is made by *anyone* on the list of bloggers, then the blog post is copied to the planet. In brief, readers of the planet see *all* the blogs posts in the list of chosen blogs.)

Now that I’m back blogging, I have found that if I write a post in the morning, and then write another later in the day, or the next morning, then there are only a handful of blog posts from all the other members of the planet in between.

I’m one of those listed at planet.intertwingly.com, and I’m guilty as charged:

Of course that’s a view of the tech blogosphere. But my wife Luann, who blogs in a very different sphere of interest, shows a similar pattern:

Perhaps a more interesting question than “Where have the bloggers gone?” is “What were they doing in the first place?” In my case, from 2003 through 2006, blogging was part of my gig at InfoWorld. For many of the others listed at planet.intertwingly.com it was a professional activity too. Collectively we were the tech industry thinking out loud. We spoke to one another through our blogs, and we monitored our RSS readers closely. That doesn’t happen these days.

Obviously Twitter, Facebook, and (for geeks particularly) Google+ have captured much of that conversational energy. Twitter is especially seductive. Architecturally it’s the same kind of pub/sub network as the RSS-mediated blogosphere. But its 140-character data packets radically lowered the threshold for interaction.

It’s not just about short-form versus long-form, though. Facebook and Google+ are now hosting conversations that would formerly have happened on — or across — blogs. Keystrokes that would have been routed to our personal clouds are instead landing in those other clouds.

I’d rather route all my output through my personal cloud and then, if/when/as appropriate, syndicate pieces of it to other clouds including Twitter, Facebook, and Google+. A few weeks back, WordPress’s Stephane Daury reminded me that I can:

@judell: since your blog is on (our very own) @wordpressdotcom, you can setup the publicize option to push your posts: http://wp.me/PEmnE-1ff.

I replied that I knew about that but preferred to crosspost manually. But I spoke too soon. My reason for not wanting to automate that push was that I wanted to tweak whether (or how) it happens. I should have realized that WordPress had thought of that:

Nice! This is an excellent step in the right direction. Thanks for the reminder, Stephane!

What’s next? Here are some things that will help me consolidate my output in my own personal cloud where it primarily belongs.

  • Different messages to each foreign cloud. Because headlines often need to be audience-specific.

  • Private to my personal cloud, public to foreign clouds. Because the public persona I shape on my blog serves different purposes than the ones I project to foreign clouds. Much of what I say in those other places doesn’t rise to the level of a public blog entry, but I’d still like to route that stuff through my personal cloud so I can centrally control/monitor/archive it.

  • Federate the interaction siloes. Because now I can’t easily follow or respond to commentary directed to my blog echoes in foreign clouds. Or, again, centrally control/monitor/archive that stuff.

In my Wired.com column I often reflect on these kinds of issues. The personal cloud services I envision mostly don’t exist yet. But it’s great to see WordPress.com moving in that direction!