Yesterday I wrote about how micropublishing comes out of intercepting a communications stream and making the messages chunks of published content, ending the post with an argument that this will only work for a mainstream audience if it can be totally unobtrusive to the communications channel. Even then though, I have my doubts as to whether communications-parasiting micropublishing could really go mainstream (whereby I mean the "regular" folks piling iPhones under the Christmas tree this year).
What I do think serves as a great model for micropublishing is when applications or better yet, devices, can be properly instrumented to emit a steady excrement of relevant metadata that can then be "massaged" into something that resembles a micropublishing content chunk. Since that statement takes the Abstract Award for the weekend, let me follow it with some concrete examples:
Application: I love Google Reader. While the province of true geeks, RSS readers strike me as the next killer application for managing the vast information flows that we're all crumbling under, and as far as they go, Google Reader is tops. It is fast, reliable, and best of all, keeps sprouting these interesting social features that are likely to make it a very interesting product to watch over the next year. While Reader has always had the notion of "shared items" that friends could subscribe to, the process for doing this was cumbersome in that it required your friend to seek out the syndication URL of your shared items and the subscribe to it. This past week, the Reader team launched the ability for you to see what friends have shared without having to explicitly subscribe, a great improvement that I think will finally raise shared items to the level of first-class feature inside of Reader. This matters because every time a user hits Shift-S on an item, that is in itself a micropublishing event (on Tumblr this is called a "reblog" but Reader makes it seem like more of a non-event). And these events strung together make a great frozen flow of ideas.
Device: A location aware mobile device is the best possible excrement generator for review-based micropublishing that I could possibly imagine (assuming of course the phone is open enough to application developers). While we constantly debate the merits of the "thumbs-up" flyby reviewers at the office, there is no doubt that when I'm evaluating a restaurant I've never eaten at, a barber who hasn't yet nicked my ear, or a hotel I'm about to entrust my sleep to, I'd rather have that information no matter how hastily it may have been generated than not. And these are categories of services that I research today— with an ever-present ability to thumbs-up/down anything at any time, who knows what else we might start micropublishing in binary about? Playgrounds? Busy intersections? Barristas? "Hot" spots?
In both of these cases the work we expect from the user publishing is as close to zero as possible within a certain limit. In fact, taken to the limit, you get models where just by doing stuff, you're generating metadata. The Google Pagerank index for instance is the inadvertent result of billions of micropublishing events (links being created) and its aggregate value is huge. Similarly, the new GPS in my car gets its traffic information from over 1MM radio-enabled GPSes that get a free ride on top of all of the semi-tractor trailers you see on the highway.
However, there does seem to be a limit beyond which it really is just metadata— potentially valuable in the aggregate— but wholly useless to the type of micropublishing that facilitates social connections and fires off the creative endorphins in people. I'm not sure where to draw the line (after all some types of metadata can go either way depending on context— for example, my Nike+ running sensor data), but the key is that the closer we get to the line without going over, the faster we might see micropublishing getting a foothold with a huge audience.
