Okay, so it took a few months more than I expected…but I’ve finished the Twitter digest cleanup on this blog that I started last August.

I’ve deleted redundant or trivial items, split some digests by topic, tagged, categorized and titled the rest, fixed typos and expanded abbreviations, reformatted quotes, links and lists, imported photos, and more…all in an attempt to make the archive a little more useful.

After trying to unify some of the more eclectic mixes of unrelated one-line remarks and links, I’ve decided it’s time to stop automatically importing “tweets” to the blog. Sure, the digests maintain quantity, but I think it’ll be better to keep the quality up instead. What makes a good status update doesn’t always make a good blog entry, and I’d frequently find myself either staying up late to edit that day’s “Line Items” post or rewriting it the following day. (Plus I was always worried about a bug in Twitter Tools that would cause a duplicate post about 30-50% of the time.)

I think the blog will be better off if I copy, expand or skip stuff from Twitter at my own pace and put it in a more suitable format to begin with.

Since the normal Twitter/Facebook link stopped working, I’ve switched to Selective Twitter Status. Instead of importing all your Twitter status updates to Facebook, it only pulls in the ones that end with the hashtag #fb. I’ve thrown together a plugin that hooks into Twitter Tools and filters out that tag when building a daily or weekly digest. (It was complicated by the fact that the README didn’t provide any real detail for the relevant API hook.) I tested the function outside of WordPress, then set it up to run on Thursday evening.

Good: It worked! Every instance of the #fb tag was removed, and everything else stayed.
Bad: Twitter Tools posted four copies of the digest.

Well, Twitter Tools does that sometimes. I’ll frequently see it post 2 or even 3 copies, and while I’ve determined it’s not related to WP Super-Cache, I haven’t gotten around to seriously debugging it. So I don’t know if it has anything to do with my plugin. Actually, it probably doesn’t, since it runs within the digest-building code.

For what it’s worth, Friday posted only two copies of the digest. I only found one item worth saving, though. (Well, two, but I expanded the other one into this post.)

I guess it still needs some testing. When I’m sure it’s working properly, I’ll post the code.

Update: Check out Version 1.0.

Following through on my thoughts on blogging with Twitter, I’ve started going through and cleaning up the imported Twitter digests made over the past 10 months. Some of the things I’m doing:

  • Rewriting titles to be more meaningful than “Line Items for YYYY-MM-DD”
  • Rewriting post slugs for the same reason. (WordPress will remember the old URL and redirect it, so it won’t break incoming links.)
  • Adding tags and categories
  • Reformatting single-item lists as very short posts.
  • Reformatting links and expanding shortened URLs (which I’ve been doing for a while now).
  • Pulling the “Powered by Twitter Tools” link from the shortest posts, generally those with only one or two items, so that it doesn’t end up dominating the related-posts data.
  • Removing redundant items. No need to keep, for instance, a link to an article when it’s followed by a post with detailed commentary on the same article. Or a link to a phone photo that’s followed by a post embedding the same photo, or one of the same subject taken with a better camera.
  • Removing really trivial items. Though I’m not always sure where to draw the line.
  • Fixing, replacing, or just dropping dead links.
  • Update: Uploading photos to show them inline instead of linked. Especially when the original link is dead.

I’ll be updating a few posts at a time for the next week or so, but it should be manageable once I’m caught up.

Meanwhile, I’ve separated my LiveJournal from my Twitter account. There’s no sense in maintaining two archives of ephemera, so I’ve decluttered my LJ: Any “Line Items” that didn’t have comments are gone, and the few that did now have proper titles, tags, userpics, etc.

Update: The cleanup is complete!

I’m really impressed with the new version of WordPress Mobile Edition. It handles both the low-end and high-end (iPhone, Android) devices cleanly and efficiently. I was using a three-tiered setup with WP-Mobile for basic phones, WPTouch for iPhone and Android devices, and of course the regular theme for desktops, but it seems simpler to drop WPTouch for now.