If you blog and also are on Twitter or a competitor, I think that’s a problem. Twitter doesn’t (yet) have a business model, and doesn’t make it terribly easy to refer back to the beginning of your tweet-stream, and the data is full of fragile URL-shortener output. So it’s time to reel things in.
First, I used BackupMyTweets as a quick-and-easy way to get an XML copy of my Twitterlife back to March 2007.
The next step is, I’m working on a script that’ll morph the XML into ongoing entries splashed back over the date hierarchy. I was thinking of grouping them into per-day batches, but maybe not. Hmmm...
The next step is, I’ll write a script that every day or so goes and uses the Twitter API to fish out everything I posted since its last run, and mashes that into the ongoing stream. Should I put them in the Atom feed? One at a time, or grouped by day or week or whatever? Hmm, not sure.
I could also write a local URI-shortener to make all my Twitter links at least as persistent as this blog, but if I just un-shorten the links in the versions I store here, that seems just about as good.
Because whenever you see a vendor owning a communications medium, that’s part of the problem, not part of the solution. Even if the vendor is as lovable as Twitter; and I do love ’em. So I’m going to route around the breakage, and you might want to think about doing the same.