Questioning Blogging Fundamentals

An email exchange I had with Woodge a week or two ago has had me thinking about some of the traditional “fundamentals” of blogs and blogging. You see, Woodge doesn’t have comments on his site. He doesn’t archive his old posts, either. Once you get to the bottom of his home page, you’re confronted with the declaration:

“Archives? There ain’t no stinkin’ archives! Older entries are just plain GONE. Too bad if you didn’t get a chance to read ’em. They were really good, too. Not like the crap posted above.”

The first time I read this, I felt a twinge of panic. I’ve ventured into the abyss of catastrophic data loss on two occasions, and both times I was lucky to make it back with only minor injuries. The thought of deliberately throwing away blog postings makes me twitchy.

But this isn’t what Woodge does. He said that he does keep his own archives of (at least some of) the things he has written. They’re just not available as traditional on-line blog archives.

Hmm. Let’s think about this for a moment.

All the main blogging tools take care of archiving automatically. When you write a new entry, it gets its own permalink at the same time it appears on your front page. From that point on, that particular entry has a unique and stable URL that you can bookmark, link to, or email to others. For blogs and sites that have a certain amount of focus, this can be immensely valuable. The abreviation “URL” stands for Uniform Resource Locator. News items, announcements, technical articles, handy tips and tricks, can all be said to be useful resources on the web.

But what about all the fluffy little entries that litter unfocused, personal blogs like mine? “Today I went to the park with Alex. We had a nice time.” Entries like this are of interest to my friends and family, but only for a limited time. They can’t really be said to be a permanent resource to anyone but myself (as souvenir memories), my kids (when they’re older and want to see what daddy was doing back then in the old days) and crazy blog stalkers who want to obsessively research the minutiae of my everyday life.

I’m starting to think that permalinking everything in sight isn’t a particularly good strategy in the long term. I definitely want to keep writing new blog entries, and I want my personal content management system to store them in a permanent archive, but that doesn’t mean these entries should be permanently visible and Google-able to the rest of the world.

There are blogging tools available that allow you to make a distinction between simple “posts” and longer “articles” (e.g. .Text and Radio Userland). With Movable Type, creating this distinction takes a bit more effort: you can set up two blogs, one for articles and one for postings, and then interleave with with a technique such as the one I described last year. You could then set the “articles” blog to generate entry archives as normal, and tell the “postings” blog to only ever show entries on the front page.

It might be a nice feature, though, if Movable Type had more options available for your “Post Status”. At the moment, you’ve got “Draft” and “Publish”. If I want to remove a published entry from my visible archives once it has outlived its usefulness, then I can set its status back to “Draft”, but that doesn’t capture my intention. Also, MT won’t actually delete the static page that had been created when the entry was originally published, so if anyone has its URL, they can still get at it. Better would be if there was a status of “Retired”, which could remove the page on disk, or could tell your web server to generate an HTTP 410: Gone message.

(Note to self: the MT3 developer contest is still open. Could I slap together a plugin in time for the deadline? Nnngggngngn….Perl…ggahhgg…)

A similar argument can be made about comments. Blogs with a strong subject focus, or with a strong community can generate lots of interesting and on-topic comments. The majority of blog comments I see, however (both here on my own blog and elsewhere), are “me too” posts, or thinly veiled pleas for a reciprocal visit or linkback. “Community” and “discussion” don’t arise on their own–they’re things you have to cultivate. And if you don’t have the time to cultivate and encourage them, and spend the associated time weeding out trolls, rubbish, and spam, then why have the comments form on your blog in the first place? Why not just show your email address, so that anyone who wants to discuss the entry can do so in a more direct manner? And if you want to run a disussion group, why not use bulletin board software?

Taking this line of thinking even further leads to the inevitable question: why am I blogging at all? If I don’t want people link to or comment on something I’ve written, why say it in public in the first place? Why not just scribble in a journal, or rant at Abi over dinner every evening?

The answer for me is at least partly laziness: I find it easier and quicker to write blog entries than to write emails to keep in touch with friends and family. Anyone who wants to know what I’m up to can check the blog. The second part of the answer is that I do occasionally have thoughts or information that I like to think other people might want to share. I put them up here, search engines index them, and sooner or later people start showing up. I don’t aspire to blogging fame, and a readership that hangs on my every word. Fame might sound like fun, but I think it would get rather stressful and annoying after a while.

Finally, I blog because I enjoy it. I like working with blogging tools, in particular Movable Type. Noodling around with HTML and CSS is fun. I like having a corner of the web that is just me, or at least an extension of myself in virtual space. If I meet someone in real life or online, I can point them over here so they can learn a little bit more about me. It’s a calling card and a playground all in one.

Is this reason enough to carry on blogging? I think so. But it might be time to change the format.

Pox duty

I’ve been home on pox duty all day today, helping Fiona through the last stages of spotty itchiness. (She’s fine, and she’ll be back at nursery tomorrow.) And it’s only just now that I’ve realised that this is the first whole day that I’ve had on my own with her.

A very pleasant day it was, too. We had some sleepy time, we watched some tennis on TV (Henman giving away his customary first set before coming back to win the match), and we had lots and lots of smiles. How different this is from Alex, though. Until last November, I was working part time, with each Wednesday off to spend with Alex. Now that I’m working a full five days a week again, I don’t get that same amount of precious daddy-baby time.

I do spend plenty of time with the kids in the evenings and at the weekends (I take them to nursery in the mornings, but that time is usually hurried and hassled), but it’s time with the kids, not time alone with the Chuffer-babe. When we split up childcare duties, I usually take Alex, while Abi takes Fiona. It’s just the way things work out. We knew it was going to be different with two children around the house than it was with just one, and I’m perfectly happy with that. It was just lovely to have so much time alone with Fiona.

Health update

The pain in my wrist is down to a manageable level again. It still hurts when I over-extend it, but at least I can grip things again. The doctor said it was probably a bruised tendon. It certainly puts my previous complaint about low-grade shoulder and wrist pain into perspective. I’m going to keep on with the left-handed mousing for the moment, though. (It actually feels kinda strange already to mouse with my right hand again.)

But as if to counterbalance the improvement in general health around the household, Fiona has now come down with the chickenpox. This is not unexpected. Alex had them about two weeks ago. With an incubation period of about 2-3 weeks, Fiona is actually right on schedule.

Curiously, the outbreak seems to be mostly restricted to her head. Being a vain kind of girlie, Fiona has taken to pulling her blanket down over her head in embarassment whenever I try to take a photo. When she’s awake, that is.

Fiona with chickenpox
Fiona with a blanket over her head

Dynamic Text Replacement with PHP and Javascript

Holy . Cow.

Most sites that replace text with images do so using hand-made images, which isn’t so terrible when there are a set number of headings, but it quickly becomes unmanageable on a site that is updated several times per day. However the replacement is performed, each image needs to be bound to the text it is replacing. That binding usually manifests itself as an <img> tag, an embedded style sheet, or a custom id attribute. And over time, through layout changes and redesigns, that binding needs to be managed by someone.

We can forget all that nonsense. No more <img> or <span> tags, no more id attributes or wasted time in Photoshop, and no more messy CSS hacks. Using JavaScript and PHP, we can generate accessible image-headings using any font we like. And we don’t have to change the structure of our HTML or CSS at all.

And again: Holy. Cow.

Watch as the download size for all your favourite design blogs increases by approximately 15% over the next couple of weeks as they all start using custom fonts for their entry titles.

For that matter, I’ve been dying to use Papyrus here on Sunpig for some time now…

Firefox 0.9

Gosh, there’s a new version of Firefox, too. The ol’ cable modem is fair creaking under the weight of downloads today.

I don’t like the toolbar buttons of the new default skin, but on the other hand version 0.9 now has a nice new Theme manager, and the long-awaited Extension manager, too. Nifty.

iTunes Music Store (UK) opens

About time, too. At this point, I can’t really see myself buying whole albums from the service, but that might change depending on how easy it is to turn the protected AAC files into unprotected MP3s. (I usually go through several Windows reinstalls and multiple PC hardware upgrades each year, and I can really do without the hassle of reacquiring and reinstalling even more licenses and keys.) I suspect that I’ll mostly be buying single tracks, both new and old. 79p a track is really not that bad.

Update: …and iTunes 4.6 still can’t sodding properly refresh CD-ROM drives that don’t have autoplay enabled.

Second update: …okay, so it does refresh CD-ROM drives, sort of. Here’s how:

  1. Eject disc
  2. Switch to a different application
  3. Switch back to iTunes
  4. The old CD should now wink out of existence
  5. Insert new CD
  6. Switch to a different application
  7. Switch back to iTunes
  8. The new CD should now be recognised

This, to my mind, is still far from “proper” refreshing. Still, for all the chunky goodness that is available in iTunes, I can forgive the programmers this minor oversight.