OStatic

Just last Thursday, I wrote a post proclaiming my undying love for how quickly open source projects tend to right themselves when sailing the choppy waters of software vulnerabilities. This time around, a vulnerability had been spotted in Firefox, affecting 3.x releases on all platforms. The fix was scheduled for release sometime this week, in the browser's 3.0.8 version.

Firefox 3.0.8 made an early arrival, however, and was officially released Friday afternoon (at 3:45 PST). For those keeping score, this was roughly two days after one of the vulnerabilities it patches was discovered.

There are many reasons to love the open source approach. The events chronicled in an article on NetworkWorld surrounding an exploit affecting Firefox outlines, quite elegantly, how open code outwardly appears risky, and -- well, wide open -- and how that same quality generates faster fixes and stronger applications.

A security researcher discovered that Firefox is vulnerable to remote memory corruption, enabling attackers to execute malicious (or at least very much unauthorized) code within the context of the browser. While security researchers spend countless hours searching out bugs and vulnerabilities, it's not usually the case that the offending attack finds its way into the public eye. Yesterday, however, this little exploit was published on several security sites. The vulnerability affects Firefox versions 3.0 through 3.0.7, on all platforms. In less than 24 hours, developers issued a patch for the vulnerability, to be included in next week's 3.0.8 release.

Late last week, Sam took a close look at the rapidly changing browser landscape. In one of the posts linked therein, Keir Thomas speculates that Firefox may well have just given up the ghost, what with an alpha version of Chrome now being available for Linux (or, at the very least, Ubuntu).

I don't think it is, nor is it going to be, quite that easy. Firefox isn't without issue -- or momentum. And Chrome for Linux? In all reality, it doesn't exist, yet. Chrome may have a number of advantages over other browsers, including Firefox, on other platforms. But if it's still too early to call this fight on Windows, declaring the superior browser on Linux is pretty much a coin toss.

According to Mike Arrington at TechCrunch, several sources say that the Mozilla-based social browser, Flock, will soon shed its Mozilla code base and start using Google's Chrome framework for future releases.

Flock's CEO, Shawn Hardin, responded to Arrington's post, saying that the browser's upcoming 2.1 release is being developed, and will be released with, its traditional Mozilla underpinnings. Hardin does not explicitly say that Flock will move to Chrome, only that the browser space has been heating up rapidly in the last few months, and that the Flock development team will continue to make architectural decisions that balance what's best for our users and what's best for Flock as a business.

Digital Arts Online has a thorough break down of some of the snags the Firefox development team has encountered as it continues work on the browser's 3.1 release. TraceMonkey, the JavaScript engine that's responsible for the browser's performance boost, seems to be what's holding its actual release back.

According to the forum posts the article points to, both Firefox developers and those focusing specifically on TraceMonkey agree that a decision has to be made -- but whether it's better to release Firefox 3.1 without TraceMonkey, release Firefox with TraceMonkey disabled by default, or give the developers a set amount of time before making the decision at all -- might be a sticking point.

By way of Glyn Moody's Open Enterprise blog comes word that Mozilla's Creative Director John Slater is gearing up to better organize and expand Mozilla's visual design community through the Mozilla Creative Collective.

The Mozilla Creative Collective hopes to harness the enthusiasm and talent that made the Spread Firefox campaign such a success. Slater plans on running regular challenges on the MCC site, as well as integrating a job board to unite artists with projects in need of design work.

By way of PCWorld comes word that Mozilla Labs will release its Test Pilot project in the next few weeks.

Test Pilot's ultimate goal is to collect data on how people use Firefox (or any Mozilla based code, extension, or add-on). While word-of-mouth and formal usability testing are effective in developing and improving features, they rely heavily on getting the word out, getting feedback in return, and tend to attract the same demographic (power-users, or early adopters, for instance). Test Pilot aims to make usability testing private, open, and easy -- with participation and the type of information shared remaining completely optional and up to the user's discretion.

On Monday, the Mozilla team announced the general availability of Firefox 3.1 beta 2 for testing. Aside from increased localization support, a new Private Browsing mode, new tab switching and preview behaviors, and support for a number of new web technologies (such as the W3C Geolocation API and offline applications), the new beta release uses the TraceMonkey JavaScript engine by default, and has made tweaks to the Gecko engine to speed content rendering.

Last month, I took a brief tour of the pre-release Songbird music player. Songbird is a cross-platform media player based on Mozilla code. This week, the Songbird project released the finalized 1.0 version of the player.

The pre-release versions of Songbird featured iPod support, Last.fm scrobbling, SHOUTcast radio, plugin extensions, and a localized concert discovery service. The 1.0 release adds one more feature to its default list -- MashTape -- and turns an ambitious eye toward the future.

The Mozilla Foundation's Mitchell Baker reported yesterday that Mozilla's revenues were up approximately 12% in 2007 over 2006. She also mentions a few matters that are worrisome. Though eWeek's Joe Wilcox's predictions of Firefox's demise are premature and without a doubt require a sizeable grain of salt, he makes a good point concerning revenues coming from Google versus Google's commitment to the Chrome browser.