What will 2020 look like?
I have no idea, but Shane Richmond asked me to guest blog for him while he was away on holiday. Here it is.
Basecamp pisses me off occasionally
We’ve been using 37 Signals’ Basecamp to write documents for the last couple of weeks at the Telegraph. All in all it’s a great product, but there are a few things that are really annoying.
For example, when someone writes a comment on a Writeboard that you created or contributed to you don’t get a notification by email, and there’s no way to subscribe to one either.
In fact, Writeboards are very much a second-class citizen in Basecamp. They’re hosted on another site, and because of the way the authentication works between them, the back button quite often ends up just redirecting you back to the same Writeboard again. The Writeboard itself has a URL, but that’s not the URL you should use to share it.
Writeboards are incredibly useful, don’t get me wrong, but they should definitely be better integrated. It would also be very useful if you could export them to PDF or Word format.
I’d probably not mention this, except that 37 Signals are really quite cocky about how usable their software is and how carefully they think things like this through. I wish they’d spend less time showing off, and more sorting issues like these out.
Not loving Stacks on Leopard?
Via Matt Legend Gemmell I found Quay - a way to have Tiger-style hierarchical folder menus in your dock, in case Leopard’s Stacks aren’t doing it for you. It’s shareware and costs only €7.
Leopard glitches
I’ve been using Leopard for a while now and, broadly, I like it. But there are one or two things that are really pissing me off.
- The PubSubAgent (used for .Mac bookmark synchronisation) craps itself all the time if you’re behind a proxy
- Disk images don’t always eject properly in the Finder sidebar
- As I mentioned before, AirPort Extreme discs don’t auto-mount or show up in the Finder properly
- iCal seems to have lost the event details panel and has replaced it with an annoying speech-bubble thing
- There are still too many apps with compatibility problems (Pukka and MySQL being the two that are affecting me at the moment)
From the archive: The software industry is quite crap too
[The second in my series of posts that have disappeared with Interesource, but which I would like to keep available. This one was a follow up to my post Don't ignore the crapness factor (which I've also republished here). It was originally published on 16th October 2006 and reflects the fact that at that time I was still stuck in Windows at work.]
A couple of days ago I blogged about how Amazon’s and other recommendation engines do a poor job. Recommendation was the cornerstone of Tim Malbon’s argument [link no longer available] that there will soon be so much data about our tastes publicly available that we will only ever recieve customised views of sites, and that this will ultimately result in less choice: stuff that the recommendation engine doesn’t think we’re interested in won’t even appear. In that post, I argued that just because we buy a book, it doesn’t necessarily mean that we want to buy anything else like it.
Today, I want to consider some of the factors in the software industry that will prevent recommendation engines from taking over our lives, even if the basic problems I outlined last time could be solved.
It occured to me recently that Web 2.0 services are the first new utility of the post-privatisation world. Most of the other services we rely on were installed, and are now regulated by, the government (I’m writing this from a UK prespective, so my terminology may not be 100% compatible). Trains, phones, roads, electicity, gas and the rest: they were all previously state monopolies and are now privatised with some form of regulator making sure that there is adequate competition and that consumers don’t get ripped off. Crucially, they also make sure that profits are ploughed back in so that infrastructure improves over time. Well, that’s the theory at least.
In the new web economy though, this isn’t the case: services like Technorati, Digg, Del.icio.us, Flickr and the rest are there with no thanks to governments. The so-called ‘blogosphere’ relies heavily on these and other services, but they are entirely unregulated. The W3C has proved itself to be so sluggish that cutting edge services cannot be expected to wait for them. Rather, someone proposes a new XML format or XML-RPC interface and it either survives or it doesn’t. RSS is a perfect example of this. Nobody is going to argue that RSS is a bullet-proof specification, nor is anyone going to suggest that it’s semantically particularly elegant. From the technology purists’ point of view, ATOM is far superior.
But here’s the thing: RSS is very very simple to create, whereas ATOM insists on using XML namespaces well and on mandatory elements and so forth. When I’m asked to describe what ATOM is, I’m left with ‘well, it’s like RSS only a bit more strict’. People don’t get enough extra for doing things ‘properly’, so they just stick with the technology that is widely adopted and good enough.
Even though RSS is imperfect, people have used it to do loads of things that would previously not have made any sense. I have an RSS feed of Subversion checkins to the projects I’m responsible for so that I can see what other people are doing right in my news aggregator. I probably use Omea Reader more than Outlook these days. There are entire businesses, like Feedburner, that are built on RSS.
For several years, RSS was the province of Blogging and XML geeks, was constantly changing, and competing extensions kept appearing and then being either swallowed or adopted very rapidly. If there is to be a world recommendation system, it will go through a much more painful process because it’s a lot more complicated than RSS. Not the least of the problems is that there isn’t a single way of identifying objects - even Amazon don’t know that two books published in two territories are the same text in different covers. You may love avocados but hate avocado bathroom suites. Good luck with the recommendation engines.
Now, imagine a world like Tim does. This is a world where everyone has agreed to work together, but that agreement has led to an undesirable restriction of choice and has been hijacked by Google, Yahoo, Microsoft and whoever else has bet on the right technology. But wait. Are Google, Yahoo and Microsoft ever going to cooperate on something like this? Can you ever see Microsoft ditching Passport Windows Live ID in favour of integrating with Yahoo’s ID system, or Google’s? No chance.
Will Hotmail Windows Live Mail, Yahoo Mail and Gmail ever be best buddies? I don’t think so.
Look at the reaction to Microsoft’s infamous Hailstorm product. I think there genuinely were people at Microsoft who thought people would enthusiastically embrace the idea of giving their entire online profile to the biggest software company in the world. When ‘don’t be evil’ Google announced something similar, even they were roundly slated.
The bottom line is that it is not in software companies’ interests to collaborate at the cutting edge. It takes years and years for them to work together on a technology (think Microsoft and Sun on Java, Microsoft and IBM on Web Services), by which time the cutting edge is elsewhere. It’s just that the battle front has moved on.
There’s simply no motivation for Google, Yahoo and Microsoft to create some über recommendation engine together. Still less for Amazon: it’s their most valuable data after all. As soon as the market for recommendation engines has settled down, the battle will move elsewhere and there will be incompatible fronobricator engines or whatever.
As far as I can see, there will always be competing pseudo-standards at the cutting edge. Collaboration on the scale Tim imagines is about as likely as the United Nations becoming the world government.
From the archive: Don’t ignore the crapness factor
[There are some blog items that I wrote in my spare time but published on the Interesource blog before it disappeared down the plug hole. I refer to these sometimes in conversation and in documents, but they are now no longer available on the web, so I'm re-publishing them here, thanks to Google's cache, so that they have a permalink that I can use to reference them. The first is about recommendation engines and was originally published on 11th October 2006.]
Norwich City fan, book afficionado, and all-round nice guy Shane Richmond has been blogging about the future of newspapers and how they might adapt to the ‘next web’. Tim Malbon responded in his blog [link no longer available] with an even more extreme vision of a world in which there’s so much data available about our preferences that we will end up with no real choices of our own, only those deemed to be of interest to us by Google or whoever. I think this latter vision is completely wrong.
Shane’s posts are well argued, as always, and are informed by his experience as the News Editor of the Telegraph.co.uk. Tim’s is compelling, but, I think, fundamentally flawed. Here’s the first part of why I think that: things are generally quite crap.
There are two oft-quoted exemplars of relevance on the Internet today: Google AdSense and Amazon. I have to say that I remain unimpressed with both of these, even though they represent the best there is at the moment. (I should say that my musical taste precludes me from using either last.fm or Pandora, so I can’t judge these.)
Let’s take Amazon. I buy broadly three kinds of books. First, books that I want to read myself for pleasure. These are generally so-called ‘literary’ novels. Then, I buy computer books for work. Finally, I buy presents for other people, things I would never buy for myself. Amazon doesn’t know why I’m buying these things, and unless I tell it, which I can’t really be bothered to do, it doesn’t know what I thought of them. Maybe there are people whoi obsessively keep their Amazon perferences up to date, but I have other things to do that are more exciting.
I recently bought and read all of the Booker Prize shortlisted books, most of them from Amazon. Once I’d bought them my recommendations were updated - to include the Booker shortlisted books that I hadn’t bought, plus one book from each author if they had a back catalogue (there was one first novel on the list this year). Clever, you’re thinking? Not so clever, if you ask me. This is the most basic possible recommendation. It’s a bit like buying the number one single and then being asked ‘have you thought about buying the rest of the top ten?’
In fact, the only time Amazon recommendations are useful to me is when I buy books so obscure that only a few other people have ever bought them there. Then, they very often uncover some completely unexpected ‘related’ books, related for no other reason that some other Amazon user has an eclectic taste that is similar to mine. This is the ‘long tail’, which is why Amazon is succesful, or at least why it is useful to me (other than the obvious pricing reasons).
The Guardian Review on saturday and the Observer Review on sunday are miles better at identifying books I may be interested in than Amazon are. Why? Because there’s an editorial policy (in the case of the Observer, a former editor at Faber, Robert McCrum) in place and it is broadly in line with my tastes. At Amazon there’s no editorial policy, just a load of people buying stuff and then some assumptions about their relatedness. Plus, Amazon are trying to sell me stuff, so I can’t trust their editorial judgement anyway. Newspapers, at the moment, can be trusted to slate stuff they think is rubbish.
One final Amazon example. I once bought Abbado’s most recent recording of Mahler’s 7th Symphony and Don Box’s Essential .NET, Volume 1. I can’t think of a single link between those two items, other than that I happened to buy them at the same time. But guess what showed up as a related item to the Mahler Symphony? Even someone who had little or no knowledge of classical music or computing can see that there’s no relationship between these things.
All these things are instances of the crapness I’m talking about.
I can’t see how this problem can ever be solved, unless computers have a way of knowing why I buy things and not just what I buy. Shane’s argument (as does Tim’s perhaps to an even greater extent) rests on someone solving this fundamental problem.
Next time I’ll look at human factors in the software business that may retard our march towards an automated society.
Is Facebook Sentient?
My brother got married last month. Since then, he’s been on his honeymoon, but his friends have been uploading pictures of the wedding to Facebook. Today he changed his relationship status to Married.
Then this showed up in my feed:
The spooky bit? The photo was uploaded and tagged by someone else, but Facebook figured out that a recent picture of the two of them would be a good way to illustrate the change of status. Was it just a coincidence that the picture was of them at the altar?
Nairnski Online
My ex-colleague Nairn Robertson, the man responsible for one of the funniest nights out in recent history, now has a blog. If you’re working on any sort of interactive project, especially one involving video, you should hire him immediately.
Telegraph week 2
Well, I’ve been at the Telegraph for a week now, and I’m doing something very different than I expected. In a good way. I’m now working on some super-cool stuff around My Telegraph, stuff that will make My Telegraph look like child’s play if we get it right.
I’ve also been able to bring in a couple of my ex-colleagues from Interesource, Neil Kleiner and Abbie Walker, both of whom have worked on social media projects for a while now. Neil used to work at the Mirror, and Abbie was key to the development of DoggySnaps. They will be helping me to work through the mountain of ideas that are bouncing around and to turn them into a implementable plan.
It’s very exciting indeed.
2020
Shane Richmond is on holiday for the next couple of weeks and, as he explains on his blog, is opening it up to a number of guest bloggers who will each blog once.
He’s asked me to be one of those who contribute their view of what the web will look like in 2020. Sometimes I feel that I have no idea what it will look like next week, so I’m not sure what I will actually talk about yet.
Suggestions are welcome required.
