Safari on Windows is About the iPhone

June 15, 2007 – 11:02 am

The pundits are all a-buzz about Safari on Windows and wondering why Apple would do it.

Personally, I think it’s really obvious why Apple has done it and its not about switchers or browser market share, it’s about the iPhone.

The other announcement Steve jobs made during the WWDC keynote was that the third-party application model for the iPhone is Web applications with AJAX goodness. Want to write an application to run on the iPhone? You’re going to be doing it with web technologies.

So, now connect the dots. Apple wants people to write cool apps for the iPhone. The iPhone uses a version of Safari that likely shares a lot of code with the desktop version. Now there is a desktop version of Safari for Windows.

In other words, Safari on Windows is about providing Windows developers with an iPhone development platform. If people like the look of Safari and decide to switch to a Mac, that’s icing on the cake.

Microsoft Just Blinked

May 16, 2007 – 8:26 pm

Wow. I’ve been in the IT industry for over ten years and one of the things I’ve learned is that strong companies compete and weak companies sue.

Microsoft’s sabre rattling over possible patent violations in Linux and other open source software is incredible because of what it says about Microsoft. If they thought they could beat open source by building a better mousetrap, they would. But they can’t. And their standard tactic of buying the competition just won’t work here.

So instead, they’re threatening open source users with patent lawsuits. Amazing. It makes me think they are in more of a panic than anyone thought. And, to be honest, it’s not surprising.

Why the AACS Key is a Non-Story

May 13, 2007 – 7:49 pm

One of my friends asked me why I hadn’t written about the recent publicity surrounding the AACS Processing key that’s proliferating on various blogs, news sites, t-shirts, and songs.

Part of the reason is, of course, that I’m lazy. As said friend well knows, I’d much rather drink beer than almost anything else. But that’s not the entire reason.

The other reason I haven’t written about it is that it’s actually a big pill of non-story. The AACS copy protection system, like all DRM systems, is never going to do what it says on the tin. The fact that it was broken in less than two months merely reinforces the point once again. But, it’s not really news.

The problem with AACS and every other DRM system is that they are simply trying to achieve the impossible. Really.

All DRM systems are built around cryptographic techniques where the message (in this case, a film) is encrypted with a key. The idea in cryptography is that only the person with the key can decrypt the message. So, lets say Mr. T wants to send a message to Mr. H without Mr. F reading it, he can give the key to Mr. H and only Mr H. will be able to read the message.

Encrypted communication forms the basis of online banking, shopping, e-commerce, and of course, military command and control systems. They work and work well. But, when applied to DRM systems, they fall apart. Not because weaknesses in the cryptography itself, but because of who it’s trying to stop from reading the message.

In a DRM system, the person who is given the key is also the person the system is designed to prevent from reading the message. Read that again as it’s the fundamental problem with DRM systems. In other words, when you buy an HD-DVD disk, the movie studio has to provide you with a way to de-crypt the contents (otherwise it’s just a shiny bit of plastic). But, they don’t want you to be able to de-crypt the contents unless your playing the movie on a standard player hooked up only to a television.

Therein lies the inherent weakness of DRM. They have to give you the ability to decode the contents, but also prevent you from decoding the contents when not allowed. The problem for DRM is not one of crypto, but rather that a machine cannot be made that can’t be tricked into giving up it’s secrets.

Crypto systems work because the sender isn’t stupid enough to send the key along with the message. In a DRM system, that’s exactly what happens. So the AACS system is broken.

The situation with DRM is a bit like the ending of Wargames. One of these days the content industry will realise that the effort to win is futile and the best way forward is not to play. In the meantime, they will continue to send out stupid letters, hold back technological innovation, and drive up the cost of hardware and software for everyone.

CD Baby’s Fantastic Shipping Notification

March 30, 2007 – 8:18 am

I just recieved the obligatory “we’ve shipped your item” from cdbaby.com. I’ve gotten thousands of these, but this is the first one that ever made me laugh out loud:

Your CD has been gently taken from our CD Baby shelves with sterilized contamination-free gloves and placed onto a satin pillow.

A team of 50 employees inspected your CD and polished it to make sure it was in the best possible condition before mailing.

Our packing specialist from Japan lit a candle and a hush fell over the crowd as he put your CD into the finest gold-lined box that money can buy.

We all had a wonderful celebration afterwards and the whole party marched down the street to the post office where the entire town of Portland waved “Bon Voyage!” to your package, on its way to you, in our private CD Baby jet on this day, Thursday, March 29th.

I hope you had a wonderful time shopping at CD Baby. We sure did. Your picture is on our wall as “Customer of the Year.” We’re all exhausted but can’t wait for you to come back to CDBABY.COM!!

Thank you, thank you, thank you!

Sigh…

Brilliant.

Linux (the OS) Will Be Subject to the GPL v3

March 29, 2007 – 6:54 am

Today, the FSF released the latest draft of the GPLv3. The reported reason for the delay is to deal with the Novel/Microsoft deal. I.e., making explicit that if you distribute GPL licensed code, you are not allowed to sue people for patent violations implemented in that code.

A lot of people are talking about the fact that Linus Torvalds has stated he won’t move the Linux kernel over to GPLv3. And, while a shame, doesn’t actually mean much. You see, the kernel is only one of the many critical pieces of Linux. Sure, it’s got the highest profile and is the brains of the OS, but a brain without a heart can’t survive.

The FSF is not just a supplier of licenses. They are also the copyright holder on a number of critical components of any Linux distribution. They hold the copyright on:

  • The Bash shell
  • The GCC compiler
  • The glibc C library
  • The fileutils package

etc. So without the above, you might be able to boot your kernel, but you won’t have a shell, a userspace library, or a compiler for your OS.

And, of course, the FSF is certainly going to move all of their own software to GPLv3 as soon as possible. So while the kernel might still be under the GPLv2 licenses, you won’t be able to distribute a usable Linux (the OS) without becoming subject to the GPLv3.

Interesting times indeed.