Tuesday, 17 July 2007

5k – 28:11

Nike Bug was off by 150-220 meters tonight. So no pace info. Grumble, grumble. I re-calibrated it during the cool down walk, so hopefully it’ll be better on Thur.

Why Browser-based Feed Readers are Free

“I +love+ the new Google Reader app on Facebook. Interesting that most people only have around five to 10 feeds.” – Robert Scoble

I now understand why start pages (NetVibes, PageFlakes, iGoogle) have traction. A volume that low has a lot of flexibility in presentation – and comparatively light on server resources. Things get interesting once feed quantities hit triple digits – it stops being live bookmarking and more like email.

Monday, 16 July 2007

PodcampMN at Flat Earth on Aug 25, 2007

Yes, it’s official.

PodcampMN, August 25th, the Saturday before Labor Day, at the Flat Earth Brewery in St. Paul.

The goal is to try to accomplish some real, dirty, uncomfortable work… as Eric Rice describes it.

If you haven’t yet, add your name and other things you’d like to both share and learn about to the wiki:

Thanks to Philip from WhatAlesThee.com and Jeff @ Flat Earth for making this happen.

How to Construct an RSS 2.0 Feed for Faster Parsing

I’m parsing more and more RSS feeds and I’m seeing some very basic problems. While the feeds are valid, they’re obfuscated. Harder to parse – not by poor tag usage – but by misusing the content within the tags.

Here’s a quick run down of the tags as documented in the RSS 2.0 Spec and my interpretation of them.

Item Tags
One or both of the following are required by the spec:
title, description
I’m fine with encoded HTML. I’m fine with using the first 50 characters or so as a title if you’d rather not use title (it is overrated). I’m not cool with having author or pubDate info in either of these tags. Just makes it harder to parse.

and then any of these. I consider the first 4 required:

A special place for the author. Author info doesn’t belong in the link, description, or title – it belongs here. If there’s author info, the author tag should be used. (Twitter, Twittergram)

The URL pointing to this specific item, most likely something that’ll load in a web browser. Not a tinyurl or another redirect, this should be the permalink at the originial source (Feedburner)

A unique string identifying the item. For simplicity in publishing this tag may be identical to link, doesn’t have to be. For example, in Twittergrams, the guid is a tinyurl. Still unique, but not technically the link.

At some point, every item was published – so it has a publication date. Put it here, in RFC 2822 format, e.g. “Thu, 7 Apr 2005 01:46:36 -0300”. In my aggregators, I don’t guess what the publication date is, I set it to Jan 1, 1970 00:00:00 2, so items don’t show up in reverse chronological order, but they’re still in the system.

One enclosure per item. Thanks. Other tags aren’t duplicated, no reason to duplicate this one. Remember, any file can be an enclosure. Not just audio and video files (Flickr).

The URL of the site the items was originally published at, think of it as a more general link. This one should be used more by aggregators.

category, comments
I have no qualms with how these tags are used. Yet.

Elsewhere 18 Aug 2008:

“Microblogs absolutely need GUIDs….Since every microblog post originated somewhere, I believe this GUID should almost always be the URL of the individual message on the originating service.” – Dave Slusher

1. I argue link is the URL attribute of the Twittergram’s enclosure
2. Specifying ‘now’ sometimes backfires, bringing old posts back from the past.

Sunday, 15 July 2007

5k in 27:40

Held a firm 8 mn/mi for 2 ks before needing a 5 min refresher. I picked the pace right up again, hoding it for the duration of the run. Ending with a 8’51″/mi average. No 7s this time – and I can feel the difference – less of a driving rhythm, more on autopilot.

Idea for a new biathalon: run 5k then give a over-tired toddler a bath.

Friday, 13 July 2007

I’m skimming Dave Slusher’s shared items. Dave doesnt’ Twitter (at least that I know of) – eavesdropping on shared items is at least as good. Yes, shared items and tumble blogs are exactly the same thing – one is a whole lot easier.

5k in 28:20

Found a good 8 mn/mi rhythm right away. Too bad it only stuck with me for, well, 8 min. By k 3, I was there again and ended strong with a 7.5 mn/mi after another brief rest.

Overall pace: 9 mn/mi.

Thursday, 12 July 2007

Running Past

Mom sent over the times from my last season in High School XC – I mostly finished between 20:30 and 21 min. Thanks mom.

Some good motivation after last night’s failed attempt due to going out too close to finishing dinner. While I hit a 7’42” mile. I stopped there.