(this is page 96 of 121)





Latest

I'm headed down to an HP analyst, customer, and press conference in NYC this week to kick off a bunch of initiatives from our overall group, IPG (Imaging and Printing Group). Thus far in my short tenure at HP, I've done one other event like this which I found to be great for a couple of reasons:

First, events like this help to remind us all of the scale and scope of HP's printing business. From the smallest little photo printer on your desk to the largest commercial presses used for printing on buildings, from cellphone camera processing pipelines to multimillion dollar realtime collaboration studios— each of these businesses reports into IPG, and at these events, we all tend to come wearing tails. As a just recently resource constrained startup, the best analogy that I can think of is that before the acquisition, we were this little tiny PT boat in big 30-foot seas, which was lifted onto the deck of an aircraft carrier. There are downsides to this, but plenty of upsides too, and one of my personal favorites is walking the decks and imagining what we could do with all of the fancy gear.

The second reason why I dig these events is because it forces everyone to get on message and clear about what it is that we are all doing here together. I know that it sounds pretty lame to think that a PR/customer event is what it takes— but in a big company every business unit spends most of its time head down getting stuff done, and there is nothing like talking to real outsiders to force the mind to focus.

The big push where that is concerned this year is what has been dubbed the "Print 2.0" transformation, which is essentially a shift in focus to the applications for printing and away from printers themselves. When I tell this to people, their first reaction is often, well obviously that is because printing is dying and you need to figure out how to squeeze the last bit o pulp out of the orange. But the reality is actually quite different. Print output— as defined by printed pages— is actually growing, even a bit faster than the economy itself. And digital printing (what HP does) is growing much faster, due largely to the shift from analog processes to digital ones. Think of what's happened to photos over the last eight years and apply it broadly across everything that gets put down on paper— all 48 trillion pages per year— and you get the general idea.

Anyway, for those of us in the business of building things that people use, the "applications space," this shift away from printer models and ink cartridges to use cases and building end to end experiences is a welcome one for many reasons, the biggest one being that it is only when you start to think about the full end to end experience that you can really engage all of the parts of the carrier towards delivering something really compelling. It is like iPod + iTunes + iTunes Music Store but for the consumption of printed content.

If you're coming to the event, please don't hesitate to find me— and I'll be glad to chat more.

Comments Permalink

One of the best things that I've learned to do in order to improve my "game-changing technologies predictive power" is to look back in 2,3, and 5 year chunks at what the things were back then that I thought were for sure the up-and-coming winners. It is a sobering exercise for understanding how in technology it is so very easy to confuse a long view for a short distance.

For instance, take web services. Back in 01-02 they were all of the rage. Websites were going to syndicate functionality to everyone, and companies big and small were going to reap huge rewards from weaving all of these new-found APIs together. And sure, 5 years later we've got a collection of interesting services from Amazon/eBay/Google, a bevy of Web 2.0 companies with half-baked APIs (mostly following in the lead of Flickr), and the built in expectation that if you're building a website today, you are a nobody until you can offer an API to your web service.

In the meantime though, only one ubiquitous API has truly emerged: RSS. As Steve Rubel pointed out in the blog post that started me thinking about this again, RSS is now the common glue by which developers can weave blog posts, pictures, tweets, and whatever else into one uniform stream of data to be consumed, remixed, and shared as needed.

And indeed, this is pretty awesome, despite the fact that we're just now scratching the surface. Adam Green (who in my mind is one of Boston's best software minds, a guy that really can span generations with his thinking) told me almost two years ago that right about now developers would be waking up to a "feed management" problem. What is more, he then set out to build the tools needed for addressing some of these challenges. I haven't stayed close enough to what he's done thus far, but I do agree with the notion that most of the interesting opportunities out there today for people working in the consumer Internet revolve around orchestration of different services through "feed management," though not quite in the publish-it-all-this-is-who-I-am-hear-me-roar style that is so prevalent among the Web 2.0 set.

Most "regular folks" don't care to be emitting digital excrement about every part of their lives for all to see, all of the time. And unfortunately, the privacy model for sharing items from feed selectively is either not there (most blogging tools), too cumbersome (Vox), or too coarsely grained (Twitter). Of all of the existing services, I've seen, Facebook's Mini Feed comes the closest to representing real life use cases, but only because Facebook is itself a closed system with a nice natural mechanism for representing friends and colleagues (though we'll see if this scales as the company moves beyond its traditional college demographic).

In order to be able to remix feeds in an interesting way, we need not only a service that sucks up RSS output from all of one's online publishing/communication platforms and normalizes it all, but also one which can then provide the right level of access control to the people and services that are likely to want to consume that amalgam of information. Now, who is working on that part of the feed management problem? Who has the scale and scope to pull it off in a way that both users and developers trust? Or can we pull it off with some combination of OpenId and RSS extensions?

It seems to me that cracking this identity/authentication/access problem is going to open up a whole world of interesting opportunities for syndicated content and services that will go well beyond publishing for most regular folks, but only if it is done in an open and distributed way. Let's just hope it doesn't take another 5 years to get there.

Comments Permalink
sunrise

While traveling this week, I discovered a really amazing radio show called "Radio Lab" from New York Public Radio (more specifically, I discovered its podcast). The first episode I listened to, on the ephemeral nature of memories, blew me away both from the quality of the content, and the way in which it was brought together by the show's producers.

The basic premise of the episode is that the old analogy that memories in the brain are stored like pages in a book (or more currently speaking, files on a hard drive) is actually flawed, and that memories are in fact stored in such a way that we re-create them every time we recall them (there is a better code + data analogy which I won't make here but is how I currently understand it). The piece really got me thinking about memory, identity, and what may come from all of us web who seem so obsessed with chronicling life in pictures, blog posts, and just about every form of digital excrement.

An example: right after listening to the piece, I found myself giving a toast at a wedding and trying to recall a story about the groom and I from sixteen years ago. As I felt my brain struggling to reform the memories, it occurred to me that this whole process would have been a whole lot easier in today's Facebook-enhanced world. The episode (and I won't go into it here) was exactly the kind of embarrassing thing that someone would now have caught with a digital camera; it would have made its way to Facebook, and ended up tagged with both of our names by all of our friends. And sixteen years from now it would be a trivial exercise for anyone preparing a toast to pull all of the interactions they've ever had with the person being celebrated— assuming of course that Facebook is still around. And not just pictures but comments, wall posts, blog posts— in short a whole lot of data that would go very far in helping assisting a more accurate reformation of those exact memories.

Progress, right? I've always thought so, for two reasons: because the act of chronicling is itself engages and rewards the author, and for the sake of history (even when you yourself are the historian coming back later to see how you've changed). It is after all exactly like Cory Doctorow wrote when he claimed that his blog served as his outboard brain. And in the Facebook example, the collective nature of the chronicling makes this outboard brain proposition even more compelling.

But the folks on the podcast made me think about whether this is in fact absolute progress. Apparently, every time you do the work of recalling a memory, you change it a little, according to the particular way in which your brain processes it at that given time. It is as though the process of bringing it to the surface bumps it against all of the stuff that has accumulated in your brain since the last time you thought about that particular memory. And in the process, the memory itself changes ever so slightly. Then when you put it away again, it goes back changed just a teeny tiny little bit. Less like what may have "objectively" happened, but a whole lot more "you" in the process.

Obviously the incessant chronicling of our lives doesn't have to affect this very human process for grooming memories over time. However, I suspect that this will only be the case for as long as the tools for chronicling our lives are lossy. Writing something down will almost always leave enough room for the memories around the words to evolve, and the photos we take are only snapshots of instants in time. But what happens when we've got Justin.tv style chronicling (assuming we could store, search, and excerpt it all)? What happens when the collective brain of all of your friends tagging and commenting puts enough perspectives in the chronicle to mitigate this process?

One of the hosts on the show made the incredibly insightful statement that in the end all we are is "a bunch of memories strung together." But from the sound of the rest of the show, it is a string that is always moving twisting slightly this way and that. I wonder what will happen as technology starts constraining the way in which we allow ourselves to move the string over time.

Comments Permalink

After yesterday's rant about creating parallel infrastructures for messaging, I was amused to read Scott Karp's blog post on the "inefficiencies" of Web 2.0 where he argues that plugging your Twitter stream into Facebook and then consuming both it and the Facebook feed in Google Reader can get annoying.

Absolutely true.

However, parallel messaging infrastructures aside, Scott is missing the point. The cool thing is that we can do these things at all.

Find any three year-old who has discovered Legos and watch him go to town snapping stuff together. For the two years, the creations that he will assemble will look like molten piles of plastic growing haphazardly every which way, really amounting to nothing more than the sheer joy of knowing that force and concentration work magic with Lego pieces. This is exactly where we are with RSS and ATOM feeds and all of the hidden readers that can consume them (Facebook, Jaiku, Google Gadgets, Yahoo Pipes, etc.).

But keep watching that three year-old as he turns into a five year-old and you'll see something really amazing start to happen. The jumbles become ships, airplanes, cars. The haphazard construction gives way to a careful understanding of where a 1x2 makes all the difference and where a right angle join can turn a car into a rocket. And in the best of cases, these new found skills find ways to surprise even the very designers of the kits the respective pieces belong to.

When it comes to syndicating and remixing content and web application functionality, I think we're just about to turn that five-year old corner. We're really about to see the true promise of web services delivered— on a consumer platform and mostly by "user programmers" remixing feeds and plugging things together. And a little redundancy is a small price to pay for that.

Comments Permalink

I've have four different exchanges with folks today about the puff piece that Jason Pontin wrote on Pownce in today's New York Times. Essentially Pownce seems like another social network Web 2.0 application that is trying to build its own messaging infrastructure. Maybe I'm not getting something about what is going on with these sites but my general thinking is that between the web, email, IM, and SMS (all relatively open albeit in decreasing order), we've got enough bricks to play with, and that building closed systems in the name of expediency is a waste of effort.

Jason Kotke nailed the general sentiment a few weeks ago when he accused Facebook of "becoming the new AOL." In jumping on its closed platform, developers are cutting a Faustian bargain at best— and especially so if the revenue model is not clearly split out.

That said, Facebook is a juggernaut, and as such not many can ignore their "platform" play. I'm almost ready to admit that their in-system messaging and status updates make sense. After all, there are millions of college kids hitting refresh 60-70 times a day in order to see what they might have otherwise seen in their inboxes and buddy lists. But a brand new startup attempting to replace email and IM?

I love the implementation of Pownce (especially because it's powered by Django and feels very fast and light). But I just can not see getting onto yet another identity network and another messaging platform just so that I can send big files around. And I think that the Pownce folks would do much better to focus on the features that could complement email and IM instead of wholesale replacing it. For instance, both of these mediums could use much better integration with SMS— and yet Pownce didn't even come out of the gate supporting SMS at all (which to me this was the killer feature that made Pownce's original inspiration so compelling).

Note: to anyone who still wants to try it, I've got a whole load of Pownce invites. Send me an email and they are yours— no need to be bidding on eBay.

Comments Permalink