Measuring blogs, part 3: Tracking RSS the old fashioned way?

A reader emailed after my post last week about measuring RSS to ask “Why not slip a 1 pixel ‘webbug’ into the RSS feed?” Good question.

Advantages of web bug graphics:

  • Unobtrusive in the RSS reader’s pane.
  • A direct hit to your server, allows you to play games like feed views and unique users. Note I didn’t say page views or content views; more on that in a second.

That’s about it, really.

Disadvantages? Plentiful:

  • No referrer, no specific content tracking. RSS readers generally send “no referrer” per the HTTP standard rather than try to make up a referring URL (though some, like Radio Userland, refer back to a host page for their services). So you can’t track which content piece the reader was coming from.
  • Doesn’t always get forwarded. RSS items generally contain minimal markup, so an extra image tag inserted is sure to be noticed and removed by most bloggers. Why is this important? We care about the total reach that our content gets, on other peoples’ sites as well as our own. At minimum you won’t be able to count any references that your content gets on tech-savvy bloggers’ sites.

Plus, of course, any tracking system that relies on client side code can be exposed—and risks your readers’ alienation. And, as we’ve discussed before, alienating your blogging readers can be a sure way to invite shunning—and shrink your reach, but good. Kind of the opposite of what you’re trying to do in the first place.

And, by the way, this goes double for any more complicated embedded Javascripts or other solutions.

But what about embedding meaningful images, each with a unique name (perhaps associated with your article’s GUID), in each article? Kinda suggests that the photobloggers are the people most likely to get real tracking of how their content is read.

Of course, they’re also the most likely to get it stolen, renamed, and rehosted on someone else’s site.

This is starting to feel like the three laws of thermodynamics, which I propose we recast as the three laws of measuring RSS:

  1. You can’t win.
  2. You can’t break even.
  3. But you don’t want to get out of the game. Not if weblogs are worth one one-hundredth of the hype that they’ve received. (And I think they’re underhyped. Weblogs at Harvard? You ain’t seen nothin’ yet.)

Second blogaversary

Today is my second blogaversary. Two years ago I started this blog in earnest and quickly got embroiled in XMLRPC, scripting, and other stuff. Since my first blogaversary, graduating from business school, moving 3000 miles, and buying a house, the blog has been a lot less technical and hopefully a little more human (apologies to those for whom either prospect is daunting).

Some things remain the same: the first post was about listening to Radiohead’s Amnesiac, and music has continued as a theme. The second post was about beer, and I’ve since broken out food and beverage as a separate department (and one that I haven’t written for in a while). The third: about the Mac and streaming audio.

AmazonHandler acting up

I’ve had no less than four people contact me within the last few weeks to tell me that AmazonHandler, my AppleScript glue to allow calling the Amazon Web Services API, isn’t working for them. The most common error is “Can’t make ‘’ into a record” but others have been reported as well, including problems with finding and loading the support scripts to do SOAP.

I think the first problem is caused by some code I put into SOAPXMLRPCHandler to work around a bug Apple introduced in the underlying SOAP layer sometime in the late 10.1.x/10.2 timeframe. The support script problem is tricky. The point of scripts is that they’re supposed to be quick and easy, so making the user install support scripts seems dumb. But it’s quicker and easier for me to release scripts that use common technologies (including the Manila API and SOAP generally) if I keep the scripts separate.

I promise I’m looking at it, if only because having this script would allow me to automate some of the workflow around “Current Listening” and “Current Reading.” But be patient—I have a day job, after all.