It starts at 10:00 AM Pacific Daylight Saving Time (the Mozilla offices are in Mountain View, California), i.e. 17:00 UTC. You can use a time zone converter to figure out your what time that is in your own time zone.

Only full downloads count, so if you’ve been using one of the release candidates and want your download to be counted for the record, you’ll have to go to the website instead of just using auto-update. Edit: The Download Day page is swamped — just head to Mozilla.com for now.

And yes, Firefox 3 is good. I’ve been using the betas and release candidates for several months, and it’s a huge improvement over version 2!

Neither browser has announced a definite release date (though Mozilla has stated Firefox 3 will launch in “late June”), but both are in the final stages. Update: Mozilla has announced a release date of June 17.

Update 2: Opera wins with a June 12 release.

• Read about Opera 9.5 RC1
• Read about Firefox 3 RC2

Update: The release date is June 17.

Codedread comments on Apple’s Web Inventions.

Asa Dotzler counteracts FUD about the safety of Firefox, Safari, and other alternative browsers. His main point: the key measure of security is not the number of vulnerabilities, but the window of vulnerability: the time between a hole being discovered and the patch getting onto users’ systems. (In addition to a responsive security team, automatic updates really help here.)

In just over a week, Opera’s new developer toolset, code-named Opera Dragonfly, will be ready for an alpha release. This will be a welcome addition, not just for developers, but ultimately for Opera users as well. Obviously, it’ll make it easier for web developers to debug compatibility issues, leading to fewer sites breaking in Opera. But it could also bring more people in. Firefox’s growth got started with recommendations by techies. If Dragonfly proves to be as good or better than Firebug, developers will spend more time with Opera, which could lead to recommendations.

Admittedly, Linux distributions often include non-final software by necessity. Many open-source projects spend years in the 0.x state not because they don’t work well, but because the authors don’t feel that it’s complete yet. (Often, a project will take their checklist and build feature 1, stabilize it, add feature 2, stabilize that, etc. so that you get a program that’s a stable subset of the target. Off the top of my head, FreeRADIUS was quite stable long before it hit 1.0, and Clam AntiVirus has been quite usable despite the fact that its latest version is 0.93.)

Lately, though, there’s been a tendency toward sticking with the latest stable release, at least for projects that have reached that magical 1.0 number. Sometimes they go even further. Only a year and a half ago, Fedora planned to skip Firefox 2 and wait for version 3. (Clearly, they expected Firefox 3 would be out sooner!) So it was a surprise to see that this time, Fedora has decided to jump on the new version before it’s finished.

CNET UK presents The 30 dumbest videogame titles ever, including “Spanky’s Quest,” “Ninjabread Man,” “How to Be a Complete Bastard,” “Touch Dic” and “Attack of the Mutant Camels.” (via Slashdot).

Cowboy Bebop at His Computer — examples of media articles (especially about pop culture) in which the reporters (and editors) clearly didn’t do their research. The title comes from a caption on a still from Cowboy Bebop. That’s not the character’s name, and the character in question is female. It probably is her computer, though.

Archeophone Records: Actionable Offenses: Indecent Phonograph Recordings from the 1890s. Comedians telling bawdy stories, recorded on wax cylinders. The write-up is PG, though the track list looks to be at least PG-13. Looked up after reading NY Times’ article on voice recordings from 1860 (recorded with ink on paper), which is also worth a read. (via Slashdot)

Edit: Forgot to list the (temporary?) resurrection of 1994-era home.mcom.com, the website of what was then Mosaic Communications Corporation and would soon be renamed Netscape. Subsequently picked up by Boing Boing and Slashdot. For more old web browsers, check out the Browser Archive at evolt.org. (via Justin Mason)

It is, of course, much more complicated than that. There are caches, fragmentation, places where memory is used inefficiently, bunches of small leaks, leaks that only happen under specific circumstances, leaks in extensions, leaks triggered by combination of extensions, etc.—not one single leak that can be fixed. And then there was the unfortunate post in which one Mozilla developer (I’m too lazy to look up who) pointed out that 1.5 stored more information in memory, and that probably had a bigger impact on total memory size than actual leaks, which many people on the Internet jumped on as “It’s not a bug, it’s a feature.” (Why should they bother to read what was actually stated, when they can just read a misleading but sensational summary?)

A lot of the small leaks were patched in bugfix releases for 1.5 and 2.0, but really big changes are coming in Firefox 3. Mozilla’s Pavlov has written a detailed post on Firefox 3 Memory Usage, describing the different categories of memory improvements that have been made in the Firefox 3 development cycle.

I wouldn’t be surprised to find that this is one of the big reasons Firefox 3 has taken so much longer than previous releases. I suspect it’s time well spent, though, and users will be happier with a later, lighter Firefox than with one that shipped earlier, but used just as much memory.

(via Asa Dotzler)

Really, the only things holding me back from jumping up to Firefox 3 on my main computers at home and at work were Firebug and some of the HTML validator extensions. Firebug is complicated enough that I didn’t want to rely on the Nightly Tester Tools to disable the compatibility checks. Then I found out that there’s a Firebug beta that does work with Firefox 3. That was enough. Last night I took the plunge.

Meanwhile, things look good on the ditch-IE6 front. After last month’s false alarm due to a local maximum, it looks like IE7 has solidly overtaken IE6 on this site! For the first 13½ days of January, Internet Explorer accounted for 62.5% of total hits. IE7 was 33.5%, and IE6 was only 28.4%. Even better, that’s barely over 1 percentage point from Firefox’s 27.2%!

Most likely, a lot of people got new computers for Christmas. New Windows boxes would mostly be Vista, and would ship with IE7. Another factor might be techies visiting their relatives and helping clean up/update their computers. They might have taken the opportunity to install IE7 or Firefox.

Firefox Floppy Disks – remember when software came on 3½-inch floppy disks? Or 5¼″? Just for fun, someone split the Firefox installer across 5 disks, complete with appropriate labels… and even took it a step farther

I usually avoid any sort of shopping on the day after Thanksgiving, online included, but I’ve been getting email from various online stores that are trying to get into Black Friday. Amazon is advertising a Black Friday Sale, and Apple is promoting a “special one-day shopping event” on their website—and annoyingly, neither of them is giving any clue as to what sort of deals are involved. Amazon keeps forwarding me to today’s deals, and Apple just says something’s coming. And neither site lists actual hours. Is it midnight to midnight? What time zone?

Speaking of Amazon, their entire home page is currently taken up by the announcement of their new eBook reader, Kindle. At $400 I’m not going to rush out and buy one, but it looks like they’ve solved some of the main e-book problems: it’s small, light and wireless, and they even bring up the reading-in-bed issue in the intro. The real question is going to be compatibility & openness: It’ll read plain text, HTML, Word, and a few other document formats (and they’re promoting its access to Wikipedia), so it should be possible for other stores to sell books for the device. And what about the e-book offerings themselves? Will they be loaded down with draconian digital rights management like the Adobe ebooks of a few years ago, or are they following the model of Amazon’s MP3 store?* In a nice change, their music downloads are entirely DRM-free and they use it as a selling point. Edit: Per Andrea’s comments and further research, Kindle ebooks are locked down with DRM. No, thanks!

The name, however, makes me wonder how soon they’ll offer Fahrenheit 451.

Finally, the Internet Storm Center has an insightful response to the statement, “There is nothing on my computer that a hacker would be interested in.” Let’s leave aside the question of your personal data for the moment. Just the fact that you’ve got a computer with an internet connection could prove very useful to someone who wants to cover their tracks or just add more power to their own distributed system.

* Amazon’s MP3 store is also surprisingly cheap. I replaced my old tapes of the original cast recordings of Les Misérables (Broadway) and Phantom Of The Opera for $9 each—they run upwards of $30 on CD.

To make these a little more useful, on my Flash site, I use JavaScript to switch the button if someone’s using Firefox, and instead promote the Spread Firefox site. I’ve written up a similar method for Opera, though it’s less clear where to send people.

I recently discovered that Flock has taken another approach to solving this problem. As you may recall, Flock is a browser based on Firefox, focusing on social networking. It integrates with blogging sites, photo-sharing sites, bookmark-sharing sites and so on.

The Flockstars Extension expands on this by converting the button into a mini-profile. You fill in information like an avatar, usernames at Flickr, YouTube, etc., and links to your website(s). It generates button code that acts like an ordinary Flock button, but contains all this extra information.

The extension reads this information. Visitors to your site who are using Flock and the extension will see an icon in the toolbar, which will pop up a short profile and a menu of all the facets of your online presence.

It’s a cool idea, and seems to fit perfectly with Flock’s target audience. But it only solves half the problem. The browser promo badge is still there, still taking up space. The fact that the profile data is in the button code doesn’t make a difference; it might as well be stored in a set of META tags in the page head.