My first thought when I heard that the Leopard blue screens being were by Unsanity’s APE was “and that’s why only fools use hacks like that”. So it was with some surprise that I read John Gruber’s article on the issue this morning and discovered that the Logitech driver installs APE. Moments before I’d installed the Logitech driver… Turns out my decision to do an archive and install to get rid of left over cruft from all the software that I’ve tried was a pretty wise one – I’ve had the Logitech drivers installed for quite some time, so most likely I would have run into the “blue screen of foolishness”.

I was silly enough to open my work email this morning, only to discover that the Apple Java-Dev list had broken out into the age old Java on OS X argument. First up here’s what people have reported1: Java 6 is not included with Leopard. The previous Java 6 DP which was pulled from ADC a while back does not run on Leopard. Upgrading to Leopard from a system with the Java 6 DP installed can cause some frustrating issues with switching Java versions.

I’m writing up three proposals for the O’Reilly Web 2.0 conference. I think the content is compelling enough but I’m not overly hopeful that any will be accepted because it turns out I really struggle with writing session abstracts. This is actually the first conference I’ve submitted proposals too so hopefully I’ll get better (and faster!) at it with a bit more practice. In a lot of ways I’m actually more interested in just getting practice at submitting proposals than actual speaking at the conference – the timing of the conference is bad, but can be worked around.

If you’re using the scp or ssh tasks with ant, you may run into a problem where part way during the upload or never disconnecting after the command completes for the ssh task. There are a couple of possible causes: The scp problem is almost certainly caused by using ant 1.7.0 or below and jsch 0.1.30 or above. You could upgrade to the latest nightly of ant1 but it’s probably easier to just drop back to jsch 0.

Andy Herron: Tomorrow is a day I’ve been looking forward to for quite a few years. Dylan Just, one of my best mates from uni, is starting at Ephox. He’s not yet on Planet Ephox but I think we’re fixing that tomorrow morning. Indeed that has been fixed. Welcome on board Dylan! Any other Ephox folk who want to start blogging – just let me know!

The realization that there is valuable information in users attention data is a wonderful thing – it leads to so many really useful features like Amazon’s recommendation system. I’ve seen a lot of really good uses of this kind of data where systems use fuzzy logic to improve a users experience or make recommendations of things they’d like. It appears that Microsoft has noticed this trend as well, but somehow I think they missed the point:

So it seems that our super secret project “EditLive! Dynamic” has been outed somehow. Apparently Andrew Frayling is on the case (twice in fact) but I have no idea where the source of the leak would have come from. Any bets on how long it will be until we get a “Ephox Rumors” (and the associated “Crazy Ephox Rumors”) site? Oh and it’s never hard to get contact details of Ephox people, a large number of us blog, and there are plenty of contact details floating around (including my details in the sidebar of this blog).

Some interesting responses to my complaint about feed readers stripping CSS: Nick Bradbury – Response: On Stripping Styles For Security Sam Ruby - Stripping Styles There’s a common misperception that my complaint was about all styles but in fact I was just referring to inline styles on the basis that they are actually part of the content, not just presentation. Sam Ruby points to a feed from Wikipedia that is exactly the use case I had in mind.

Got my MacBook Pro back from service today, all fixed up. Total repair bill would have been $2500 if it wasn’t under warranty. So all up it took three and a half days to get fixed which isn’t too bad actually. I still think it’s a shame that Apple don’t offer guaranteed turn around, on-site support – it would make buying Macs for businesses a lot nicer, but I can understand it’s not their primary target market.

A while back people discovered that many RSS readers, and all online RSS aggregators didn’t sandbox content from different sites and malicious HTML could cause cross site scripting (XSS) attacks and general nastiness. As a result most feed readers filter HTML through a seriously restrictive white list, including removing all CSS information. I’ve reached the point where I’ve simply had enough of this. CSS is a vital part of the internet and if feeds are going to be useful, we need them to work with CSS properly.

My MacBook Pro has acquired insomnia and it’s firewire ports have given up the ghost so I’ve had to part with it while it gets repaired. It’s always annoying when problems emerge with new things, particularly when you depend on them to get work done, but it hasn’t worked out too badly. With Carbon Copy Cloner I backed everything up before putting the laptop in for service and commandeered the mac mini we have for testing so I’m up and running like normal – just a lot slower and with a tiny fraction of the RAM.

Here’s a really simple golden rule for anyone thinking of adding auto update to their products – never ever include any user identifiable information_._ There’s simply no reason you need to know who is checking for updates, you only need to know what version they have. Given the infrastructure of the internet you will wind up getting their IP address, your policy should be that these aren’t stored. It comes as no surprise to me that the WordPress mob broke this rule with their new auto update – they always seemed shifty to me.