SVNMate looks amazing - but I'd love to have support for Git. I'm currently building a TextMate bundle for Git (and, of course, using Git to track the development of the Git bundle). 

I meant to blog about this the other day. Chimezie Ogbuji, XML blogger and expert, lost two of his daughters in a fire at the weekend, and his third daughter has subsequently died. If you can, please send the Ogbuji family donations to help them rebuild their lives after this calamity. And be sure to ensure that your home is protected as best you can from fire. Stay safe everybody. 

Lots of drama in the blogosphere about Internet Explorer 8 (you can Google it yerself!). Can't exactly see the point. Hasn't Firefox supplanted the need for Internet Explorer yet? The only reason I still have a copy of Internet Explorer is to test to see how badly it renders otherwise standards-compliant web pages. 

Les has all the reasons you need not to buy a Western Digital hard drive - namely, that they try and police what users do with them. 

This kind of code is so filled with FAIL it makes the eyes water. It's almost as if they haven't heard of whitespace stripping functions, or regular expressions. Doh. 

According to Guido van Rossum, the great Python 3000 moment is immanent. Cool. We all love our Benevolent Dictator for Life. 

Martin Belam has a post on the BBC Internet Blog talking about how the BBC haven't really been keeping their old content available. Remember, folks, think like librarians. Cool URIs don't change. Cool resources don't disappear. Cool website owners make sure that URIs don't change and resources don't disappear. 

Curtis Poe says that for all the BBC's faults on the Web technology front, the recent blogstorm proves they are open to criticism. 

Apparently, a blog post I made inspired Matt Terenzio enough for him to create a new Twitter applicationc called @locals, which aggregates Twitter posts basedon location. Must play with it - I've been on a bit of a Twitter downer recently, posting a lot less than I used to. Still love the service though. 

An Admonition: Use Proper URIs, Dear Sirs 

I've tried being cynical and needlessly offensive. But nothing is changing. Please use useful and proper URIs.

I'm on a train. I'm reading your blog in my newsreader (Google Reader with Gears), and I run across an interesting blog post that you've written. So I decide I want to blog it. I right click on the title and choose 'Copy Link Location'. I paste it into my editor only to find it's "feeds.feedburner.com/~r/yourblog/~3/1234567890/12345.php". Helpful. I'm not linking to that - it's not the proper URI. It's like a fricking TinyURL.

My reaction when I come across a URI like this is to put the article on my back-burner stack - I'll look into it when I'm ready, but not until then.

What should you do if you want to track your RSS reader traffic? Well, make it an argument on your existing URIs. Just put "?source=rss" or something similar. That way, when I click through from my reader, your server can check it's GET variables for source=rss to see if I've arrived that way. And I can easily see what the original URI is in my reader and quickly link to it.

In the next version of HTML, there are also plans for a 'ping' attribute - here you can point to a URI which is 'pinged' when someone clicks on a link. This is a natural evolution of this principle.