Swiftfox

» see getswiftfox.com as it lived, on the wayback machine

~ the goodbye ~

Swiftfox was one person's answer to a small annoyance. Mozilla shipped a single generic Linux build of Firefox, compiled for the lowest common denominator so it ran everywhere, and Jason Halme thought that was leaving free performance on the floor. His first build went out on 28 March 2005, synced to Firefox 1.0.2, with the compiler pointed at one processor family instead of at all of them.

The operation never pretended to be more than it was. DreamHost hosting, a donate button for the bandwidth bill, an AdSense slot in the corner, and Halme answering support questions on his own phpBB forum in the first person. That forum peaked at 826 members in October 2011, which is the honest scale of the thing: a browser with a name across desktop Linux, cut in one person's evenings.

The last build shipped on Christmas morning. Version 3.6.13 went into the RSS feed at 07:43 GMT on 25 December 2010, described in full as "New build for December 25". Nothing came after it. The feed never gained another item, the copyright line at the bottom of every page froze at 2011, and the download links began returning 404 in March 2013 while the pages around them kept serving normally.

Matching a browser binary to your exact processor is the same instinct that filled Turkish forum signatures in those years, the blocks under every post on donanimhaber and frmtr where people listed their CPU and their RAM timings for anyone who cared. I wrote those signatures. Swiftfox turned that impulse into a download page, and the build you took was the one that named your chip.

~ the chronicle ~

~ eleven binaries for one browser ~

In June 2007 Swiftfox 2.0.0.4 went out as eleven separate Debian packages: athlon, athlon-xp, athlon64, athlon64-32bit, k6-2, pentium-m, pentium2, pentium3, pentium3m, pentium4, prescott. Each one was around ten megabytes, each had a matching tarball, and the site kept a page that mapped roughly thirty-five named processor models onto the right target so you could look yourself up.

The measured payoff was smaller than the effort suggests. APC Magazine clocked a rendering improvement of about 1.7 percent on Swiftfox 1.5.0.6. People installed it anyway, because the number was not really the point of a build that had your CPU in its filename.

~ the license fight ~

Halme's LICENSE file is the document that decided the project's fate. Clause one: Swiftfox binaries are not under the MPL and are not freely distributable, licensed only to the person who downloads them from getswiftfox.com. Clause four: anyone else compiling the source has to use Mozilla's default unofficial build name or invent their own, because Swiftfox is Halme's trademark. His own apt repository sat at a path ending in non-free, so he knew exactly where this put him.

On 10 April 2007 Linux.com ran John Bielefeldt's piece "Swiftfox, the perverting of an open source browser", and the argument in it was that Halme had inverted the security model he claimed to be protecting. His defense was that the restrictions existed to stop anyone from maliciously altering a binary and redistributing it under his name. The effect either way was that Debian could not ship Swiftfox even in non-free, so every user had to fetch a tarball from one person's web host and trust it.

~ the redirect ~

The site outlived the project by almost six years and then went without a word. On 16 September 2016 at 14:39 UTC the download pages were still answering 200. By 11:47 the next morning Apache was returning a site-wide 301 to twitter.com/jasonhalme, applied so bluntly that even robots.txt redirected. No farewell page, no post, no notice on the forum.

That redirect held for nine years. The Twitter account it pointed to now returns 404, and the domain itself has been answering HTTP 500 with an empty body since January 2026. Halme is still paying to renew it. The registry expiry is 22 April 2027.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »