Archive for December, 2005

2005 Randoms

posted December 31st, 2005, no comments

We’re nearing the end of the year (less than twelve hours in my time zone) and it has become time to write down some final random notes.

  • There’s some interesting things going on with regards to tuning in sIFR 3, see these experiments. Of course there’s more info on the mailing-list.

  • If you hang out at the coolest webhosting company around (a.k.a. TextDrive), there’s a TextMeet being organized next week in Utrecht. See the forum topic for more info.

  • Laurent Haug, whom I met at Reboot last June, is organizing his own conference in Geneva early February. I won’t be able to make it, but check it out: Lift06.

And with that, all the best for 2006!

Back It Up Back It Up

posted December 22nd, 2005, 9 comments

As you are hopefully aware, backups are the only way to make sure you don’t lose your data in case of a crash or theft or an other disaster. There are several ways to back up your data, such as writing it to a tape-recorder stuck away in a fireproof vault.

Luckily there are easier methods as well.

My personal strategy is as follows: I keep one full backup of the PowerBooks hard drive on an external Firewire hard disk. Furthermore, I upload my documents and work (anything I code, basically) to Strongspace.

There are two programs I know of for the Mac which do full disk backups. One is Carbon Copy Cloner (CCC), the other is SuperDuper. I’ve used CCC for a couple of months, and I’ve recently bought a SuperDuper license. Whereas CCC seems to be aimed at users who know what they’re doing, SuperDuper is clearly for the folks who don’t and/or want assurance that the backup is really working. The interface is clear and consise, and the User’s Guide (pdf) is useful even if you don’t use SuperDuper. Please note that the risk of buying the application after reading the guide is significant. You’ve been warned.

My Strongspace backups are done by means of a combination of Ruby, rsync and SFTP. You can download the script here. It will allow you to upload specific directories, and it lets you exclude files and directories on a per directory basis. It will also remove files from Strongspace which no longer are on your disk. You can follow instructions on setting up a scripted backup at Invisible: Back-up. Instructions on my script are in the script itself.

And finally, there’s scheduling. You need to schedule your backups so you won’t forget making them. Please do as I say and not as I do, because I don’t schedule mine. I usually make a full backup before I take the PowerBook with me on a trip longer than the bycicle ride to university. If I’m not travelling for, say ten days, I’ll also make a backup. The Strongspace backups are made at least once a day, usually before I hit the sack. This means the latest stuff will have been backed up, no matter what time I go to sleep.

Luckily I haven’t needed my backups yet, but at least I’m prepared. I hope you will be, too.

sIFR 3: A Look into the Future

posted December 16th, 2005, 62 comments, tagged ,

Some time ago Mike and I asked you what features you wanted to see in sIFR 3. While we haven’t defined the exact list of features for the new version it has become time to look into the future to see where sIFR is heading.

As you probably know Mike is now the CEO of Newsvine, and as such he’s pretty occupied. The result of this is that the actual development of sIFR 3 is resting fully on my shoulders. Since I’m no super hero, I’ve been thinking about how the development process should be approached and how you can help with it.

sIFR Wants You

sIFR is meant to work in as many browsers as possible. Being a fully degradable add-on, it should not break sites when a browser has trouble supporting it. To accomplish this goal a lot of testing is needed. Much more testing than I have machines or time for. To speed up and improve with this testing we’re hoping for the user-base to lend a hand. Yes, sIFR wants you.

A mailing-list has been set up to aid in this process. After every significant iteration of the code you’ll be notified through this list of new tests. The tests will mostly be automated, aside from the occasional human verification. We’re hoping to get confirmations from two or three people for each browser and browser version we are supporting (more about that in a later post).

The list will also be used to discuss the way sIFR works itself. Here you can think of the tuning process or how to provide fallback for Flash transparency. sIFR is not going to be “designed by committee” however. While we greatly value your input, at the end of the day it’s going to be our call.

Time

Just as Mike is busy, so am I. Currently I’m studying Computer Science at the University of Twente and I also have to earn some money. If you have an interest in seeing sIFR developed faster please consider donating (by clicking on the Make a Donation button on the right) or hiring me to work on sIFR.

The Future

The future of sIFR is bright. With the advent and acceptance of newer browsers it has become possible to ease the use of sIFR. The release of the new Flash 8 gives us more power, and also means we’re letting go of Flash 6. Good stuff is on it’s way, and I hope you’re in for a ride. Again, please sign up for the mailing-list and thanks in advance for your support.

Optimizations

posted December 13th, 2005, 10 comments, tagged ,

When optimizing, you have to make sure it actually helps. In this case, not really. You’re lucky to see a one millisecond difference on a thousand function calls (in Firefox 1.5 on Mac, at least).

Update (a few minutes after the fact): I realized that Deans function checks for the existence of a property on a node. This lookup could cost more time, so I updated the test case to make sure the if/else clause looked up two properties on the document node. Differences now are 10 – 20 ms (still not very much as we are talking about a thousand invocations).

Update (December 13th, 11 pm): Updated test with Sjoerds suggestions. More interesting results in the comments.

They Searched, Came, and Left in Utter Confusion

posted December 7th, 2005, no comments, tagged ,

Some search engine referrers I found in my logs:

Looks like I might want to put some ads up when people are coming from search engines…

(And regarding that christmas card thingy… not feeling like it this year. Sorry!)