Archive for April, 2009

Monthly Archive

Daniel Sandler is experimenting with using twitter for comments, and makes some very good points about comments on the web in the process. Essentially, he pulls in the content of any tweet that references his post’s full URL, TinyURL, or even just the TinyURL hash. This has the very nice effect of forcing people who want to comment on his post to own their words. Their comments will be public to their own audience, and so are more likely to be constructive and civil.

Twitter comments on Daniel’s website.

Tying your tweet to a particular page online is awkward though, due to Twitter’s 140-character limit. URLs were designed to be expressive, but not necessarily space-efficient (compare them to DOI or ISBN codes). Twitter’s recent rise has driven the increased use of URL-shortening services like TinyURL and, which were originally designed because of the limitations of email clients that weren’t able to correctly break up an URL that was wider than the 80-character wide text columns used at the time.

We seem to have replaced one limitation with another though. By feeding all URLs through minimisation services, readers lose all context about the page they are about to open — is it a video? What domain is it on? Have I visited it before? There are some links that I would be disinclined to click on when using my iPhone, but with minimised URLs, you don’t know what you’ve got until it begins to load in. Plus, there’s the nightmare scenario that the URL service dies, and since their databases are kept private, all that information is lost.

I think URL shortening services could be obviated if Twitter started treating URLs a little differently. There are two main audiences for twitter tweets: mobile phone users who receive tweets as SMS messages (this is the original reason why twitter has 140-character limits), and users who visit the twitter website, or use one of the myriad desktop and smartphone applications to keep up with tweets. These users are not concerned about the character limit in the same way. I would expect this group of people to be growing faster than those who get tweets via SMS.

Ideally, Twitter would disregard URL content as part of the character limit. If you think about it, the URL (this page) conveys almost no information whatsoever. It could as easily be replaced with some single-character replacement in SMS messages (whose users are much less likely to actually follow links than web/applications users anyway). [On further reflection, it is clear that this wouldn't work as I imagined, as the target URL for these single character links would still need to be encoded somewhere as part of the message.]

On the web, and in applications, URLs shouldn’t need to be minimised at all. Twitter clients could truncate URLs for display, but all the URL content should stay available to be used by those clients that want it.

Like I imagine the majority of those users who migrated from a Windows PC to a Mac, Firefox has been my primary browser for the last five years (since Firefox 0.8 came out in February 2004). It’s so long ago now in web years that it’s hard to remember, but on Windows, back in those dark days, there really weren’t any options beyond the standard Internet Explorer 6 install.

Microsoft had lost interest in maintaining their browser, having secured 90% of the browser market. For web designers, this was a disaster. When Firefox emerged it was almost instantly better than IE in every regard, so it was an obvious choice. Nowadays, the three most advanced browsers — Firefox, Chrome and Safari — each have many strengths on which to recommend them.

Safari 4 iconWhen Safari 4 was released as a public beta in February, I decided to give it a try for a week. You all thought I was mad, many of you requested to be transferred to another peanut factory, but I’m still using it here two months later.

Safari’s main strengths are speed and stability. If you’re a tinkerer, a Firefox install has a Windows XP-style half-life, after which its performance continuously degrades and it becomes significantly more prone to crashing. I tried opening the Safari feature page in my new copy of Safari and my many years-old Firefox, and the difference in performance ellicited an honest-to-God laugh-out-loud. That almost never happens! (I should say that I’m open to the idea that I am wholly responsible for Firefox’s poor performance by loading my profile with too many extensions and customisations. One badly-written extension or Greasemonkey script and the browser can begin to drag.)

Safari is ahead of the game in other ways too though. Full-text search of your history with rendered thumbnails of each page is a killer feature. These are indexed by Spotlight as well and can be searched from apps like Launchbar. The Chrome-style new tab screen is excellent for keeping track of pages that change over the course of the day. The lack of a progress bar when loading a page is a very interesting departure which I find myself liking more as time goes on. The new tab bar does take some getting used to, and has been discussed at quite marvelous length elsewhere. I would favour one of the proposed mockups which give more space to the window controls.

There were two things about my Firefox setup that I did really miss when switching: keyword search from the location bar, and delicious integration. In Firefox you can just type directly into the location bar and it will do a Google search. Even better than that is using keywords to search specific sites — “wp Bell pepper” to open a Wikipedia page for example.

Kewurl example

Safari can’t do any of that out of the box, but there is a SIMBL plugin that manages this very nicely, called Keywurl. Delicious support is provided by the Delicious Safari extension, which does the job admirably. Boom.

Twitter has really taken off in the last few weeks. If you haven’t signed up yet, and are sick of hearing about it, I sympathise. I didn’t understand what the point was at all until I signed up, originally just so that I could follow a few interesting people better than I could using RSS. Eventually, you’ll see a conversation going on and want to join in.

From a web architecture point of view, Twitter is particularly interesting because it is, to my memory, the first web 2.0-ey application that doesn’t really need a website. They’ve done such a great job with their API and backend that there are dozens of excellent applications and plugins for just about every publishing platform. I read and post from a bunch of applications — Tweetie on my iPhone, and Lounge and Tweetdeck on my laptop — and very rarely actually visit the Twitter website.

I guess this is a matter of partly good timing (now that smartphones are common), and partly that tweets are perfect iPhone-sized data.