June 13, 2009

Testing Liveblogging

Category: Site News — By Kelson @ 7:46 pm

7:22:57 PM: I wanted to make sure this would actually work if I wanted to liveblog, say, a DC Nation panel or Geoff Johns talk.

7:24:19 PM: And no, I didn’t manage to get out to the Earth-2 grand opening today.

7:32:12 PM: Let’s see about photos. Here’s a preview of something I plan to write up soon http://twitpic.com/7ch5u

7:35:02 PM: Okay, so the post is there but it’s empty. And there’s no URL for it. Better to find out now than during SDCC. Maybe I can fix/report it.

7:36:08 PM: Oh. Not good. Now there are two post, both empty, both unlinkable.

7:38:26 PM: @SpeedsterSite Jay’s hair was originally black, then retconned to brown. The wrong color is the only thing I don’t like about this statue.

7:39:56 PM: Great, the server crashed while I was trying to test.

7:47:36 PM: @jcbaggee It’s worse than that: I’m the admin on that server. Well, there’s an upgrade planned.

7:49:30 PM: Okay, now I’ve got 2 empty posts and 1 that looks like exactly what it’s supposed to do.

7:52:17 PM: I think it just doesn’t work well with WP-Super Cache, Let’s see how it works if I disable that.

7:52:59 PM: @jcbaggee On the plus side, it DID recover automatically.

7:55:25 PM: It’s supposedly set to check every 2 minutes once it starts, but hasn’t picked anything up in 15 min

7:59:12 PM: OK, it’s picked up the missing tweets. I wonder why the delay?

8:00:39 PM: Well, it mostly works. I’ll have to test it again and see whether disabling the cache helps with starting. For now, signing off.

Notes: The post above was made using the WordPress plugin Twitter LiveBlog. It follows your Twitter feed looking for a signal (“//NLB//” for “New Live Blog” followed by a title), then creates a blog post and starts updating it with your tweets until you send the closing signal (“//ELB//” for “End Live Blog”)

The first time I tested it, I had WP-Super-Cache enabled, and ended up with two empty posts with the right title, but no usable URL, then the expected post. The second time, I tried it with WP-Super-Cache disabled, and it worked as expected. (That post was a lot shorter and didn’t have any conversations or links, so I deleted it.) Except that it doesn’t seem to be checking as often as it’s set for. I don’t think I’ve got enough plugins/apps/etc. on here to use up the Twitter API limits, but it’s definitely something I’ll be looking into.

Comments are closed.

RSS feed for comments on this post.

This Time Last Year