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). Trying to get information about EditLive! Dynamic out of us will be much more difficult – it’s so secret, most of the company won’t know it exists. We’ll talk endlessly about Rythmyx integrations, and anything else we know about though.

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. Many of the comments however want to strip styles to preserve a uniform look in a “river of news” type of reader, for example Nick’s comment:

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. I’m still impressed at how easy it was to switch to a backup machine and back – keeping a full clone of the system around is definitely a good idea.

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. So let’s take a look at what’s really going wrong:

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. Tell me why exactly you need the URL of the blog to determine if a new version is available? Exactly what use to you is blog.ephox.intra going to be? Oh well, I’m already removing all the pointless blog entries they spam the dashboard with and those weird technorati partner parameters so I guess I’ll be asking for updates from wordpress.com or something too….

It’s a common question – what’s the point of social networks? The most common answer is basically none. Most social networks provide yet another way to get in touch and keep in touch with people which is great but lets face it, there are about a billion different ways to communicate and leaving messages on someone’s wall only looks good compared to sending smoke signals. Some people might argue that it lets you map out and visualize your social network but seriously I know who my friends are, why don’t you? The address book has been around a long time and it still works seriously well.

 My open tabs in NetNewsWire have exploded in the last couple of days with really good articles about driving wiki adoption and generally making wiki’s work. First up Making Wikis Work is a pretty good overview of all that is wrong with wikis. It’s odd to think that a technology as young as wikis has legacy cruft but they do.

In particular, WikiWords are no longer required or a good idea, use an editor that makes creating links easy or use a simple shortcut for creating links (the square bracket notation was easy for most people to learn, but you need to provide a completely GUI alternative as well).

I got some really positive feedback on the various community/openness projects that I’ve been spearheading within Ephox from one of our OEMs today. Apparently they’ve discovered our early access program and are already trying out our brand new Express Edit functionality1.  It’s really nice to actually hear from clients that these elements are useful as we haven’t really managed to build up a community, even if we are seeing gradually increasing traffic. For a while now we’ve had potential new employees commenting on Planet Ephox which is great, but we haven’t really heard from clients taking advantage of it, even if we’ve seen some of the indirect effects via analytics and support cases.

Yesterday afternoon Suneth and I took on a research project to see how feasible it was to keep server caches up to date by using XMPP to notify the other servers in the cluster of a change. Imagine a web server with some latency between it and the resources it’s serving (eg: it’s using S3), to speed up performance you’d want to cache the recently used or most commonly used resources locally on the server, but if you need to scale up to a cluster of servers and the resources are being changed, that cache becomes a problem.

When I first joined the company it was tradition that the engineers (and often the CEO, CTO and COO who were in the same country back then) headed down to the Paddo tavern for a pub lunch. Sadly a while back the quality of their roast lunch started to reflect the $4 price tag and we abandoned the concept. With the new renovations to the Paddo and rumors of improved quality we’ve started heading down the street for a roast lunch and a beer again.

I was just thinking to myself this morning how good it is to see Andy really stepping up, taking responsibility and showing great initiative to keep the team moving forward. Turns out the rest of the business agrees – he’s officially acquired the “Senior” title.

Well done Andy!