So Apple have released Safari for Windows – really no idea why, but they have. Sadly, just like on Mac it has terrible JavaScript and Java debugging support. In fact, it’s worse on Windows than on Mac – anyone know how to turn the debug menu on? Anyone know how to get a Java console to appear?

I’d really, really like to make things work with it but all I can do at the moment is randomly guess at the source of problems.

The antileech plugin so far has done nothing towards actually blocking content and frankly doesn’t really show a lot of promise that it ever will, however it has been interesting seeing where my content pops up. One that looks rather odd to me is dcomments.com. Frankly it looks just like a splog but it doesn’t have any ads or links out to other sites. It does however republish all my content without any extra comments and has the absolute minimum of linkage back to symphonious.net. In fact, regularly through the site the term “Symphonious” is used but linked to their version of the content – the only link back is labelled “Original article here”, right about an Add Comment button.

I suppose I should be happy but I’m not sure I am. It appears that my blog has moved from the insignificant long tail to the worth spamming and leeching long tail. Like every blog, I’ve always seen comment spam coming in, but I’m not seeing targeted comment spam picking out the posts with the best page rank and focussing on them. I’m also suddenly seeing splogs leeching my content.

Apparently someone told bloggers that adding pictures to your posts helps make things easier to read. Unfortunately, what they forgot to mention is that the pictures should actually be part of the message or at least tangentially related. Take for instance this post by Joel Spolsky about UI design and alarm clocks. Scattered through the article are pictures of random buildings, including for some unknown reason one with a sign reading “Cemetery for Soldiers’ Dogs”. Wouldn’t pictures of alarm clocks make more sense? What about a frustrated old woman? A sleep deprived man? All these things would actually relate to the content and perhaps enhance the message the post is trying to make. Buildings however only distract from the actual message – particularly quizzical things like a cemetery for soldiers’ dogs.

Olly Hodgson has a great article up pointing out how important it is to think about the usability of your CMS, not just the websites it creates. I’m even more impressed that he realized the editor is the key point of usability in the CMS and gave advice to go about configuring it properly.

Most people think a CMS lives or dies by it’s repository design, it’s content reuse potential or some other fancy backend feature. The reality though is that content management systems are really all about creating and editing content and that’s done with the editor. Most of the user’s time is spent using the editor and so their perception of the whole system is very much dependant on how good the editor is.

It’s been interesting watching the blog adoption cycle here at Ephox. For a long time I think I was the only person actively blogging, and just from the positive effects of blogging that I’d experienced other people got interested. Our CEO was pressured into getting back into blogging again1, the engineering team started up an internal blog to share some of the cool stuff we found which never really took off and then the CEO started an internal blog2 which has helped the rest of the company get more of a grip on where he’s going. Andy started a blog and we had a couple of hires who had blogs lying dormant that they were then pressured into getting back into and suddenly there was a critical mass of people blogging – enough to have a conversation between us on the blogs.

It seems every blog post today last fortnight1 has to use the word “malaise” so I might as well chime in. What tipped me over the edge was seeing the comment:

Scoble and Mike – get a life. You peaked.

What’s really amazing about that comment isn’t just that it’s mean and inconsiderate, but that I came across it by reading Robert’s link blog. He’s actually publicizing criticism of himself. Frankly, I wouldn’t be big enough to do that. Maybe A-List bloggers are as stuck up as people tend to assume they are, but I suspect most of them are just normal people that everyone else keeps putting up on a pedestal. I certainly found Robert friendly and approachable when I met him the other week. People need to stop assuming that a link from an A-List blogger is going to make or break their business. The fact is, getting a link from an A-List blogger isn’t as big a deal as you think and it just takes the fun out of it for the A-List bloggers:

Probably the most commented on experience from Mac OS 9 was the fact that once one application crashed, they were all in trouble; generally, you were in for a complete system reboot. At last OS X came along and solved all that, finally providing protected memory and the ability to force quit one application without affecting the others. People rejoiced as they left their computers running for days on end without needing reboots and uptimes soared.

Two very interesting things I’ve learnt today:

1. Ousted is a real word.
2. Suneth has a blog.

Apparently Andy discovered him within a few hours. By the time I got back to reading feeds this morning both he and Brett had ousted him. Of course, I’ve now added him to Planet Ephox.

Opensource projects tend to have a well-earned reputation for being poorly documented. Originally this was caused by the fact that most of the people who knew the codebase were developers who didn’t have the skills or interest in writing the documentation. With opensource becoming more mainstream and more people getting involved I think that reason, while still having an effect, has become less of a problem. Despite that the quality of opensource documentation hasn’t improved – if anything it seems to be getting worse. More and more projects don’t even have half-decent reference information and just a few scraps of information on where to start.

Where is it? Clearly I’m missing something here. There’s a wiki with some good getting started overview stuff and some other chicken scratching but I’m yet to find an actual reference telling me what’s actually allowed in struts.xml. Shouldn’t that be pointed to in a big neon sign? The struts.xml page on the wiki isn’t exactly comprehensive and while the DTD is listed on the examples page it’s not exactly commented..

Oh and did I mention that wiki’s are a horrible way to write documentation?

Robert Scoble posts about saving Pandora:

…Tom talking about how the business of Internet Radio is under pressure due to coming changes in how the music industry wants Internet Radio stations to pay for the distribution of music (basically the costs will triple, if the proposed changes go into effect). After we talk about the challenges that Pandora’s business faces if the fee changes go through Tom gives me a preview of their new Sprint/mobile service.