NetscapeFlock. When AOL first announced they were discontinuing Netscape, they recommended Firefox (a logical choice for many reasons). Since then, they’ve also started heavily promoting Flock—to the point of offering seamless upgrades from NS8 to Flock. (In theory, anyway; I fired up the copy I had for testing and couldn’t get it to do anything but update to the most recent 8.x version. Confirmed. I let it sit open in the background for a while, and it eventually popped up the offer for 1-click Flock migration.) Netscape 9 has an update notice that offers to download Flock or Firefox.

The key issue, of course, is moving as many users as possible from a discontinued browser—there’s no doubt that security holes will be found in it over time—to one that is actively maintained.

Why Flock, specifically? Well, sticking with the same toolkit and user profile makes migration easier, so that narrows the field to Firefox and Flock. (Not sure about SeaMonkey’s profile.) Since Netscape 8 and 9 were big on integrating with websites, Flock’s “social browser” seems a slightly better fit. And it turns out most of the Netscape 8 team went on to build Flock. Talk about social networking!

(via Flock: The Netscape Spirit Lives On)

IE9 to include alternative CSS.2012 standard instead of following anything remotely like the rest of the world.

Social tagging initiative from WaSP to physically tag bad web designers.

Opera hits 106/100 on Acid3 after discovering an Easter egg in the test.

The openSUSE mailing list announced OpenSUSE 4.1, with KDE 4.1, GNOME 4.1, MP41 support, OpenOffice 4.1, XEN 4.1, VirtualBox 4.1, and a 4-in-1 CD install.

Added: The Electronic Frontier Foundation has sent out a newsletter detailing its findings on a Congressional Listening program (apparently they monitor citizens for their opinions—who knew?), plans to move the EFF offices to an armored zeppelin, an NSA-sponsored social networking site (to “allow ordinary Americans to instantly share their private data with the government”), and Homeland Security’s conclusion that Wikipedia is a “Larger Threat Than Terrorism, Dixie Chicks Combined.” Sadly, the newsletter does not appear to be archived on the website.

Added: Virgle, a Virgin/Google joint venture to establish a permanent colony on Mars. Now seeking applicants for Martian pioneers. Takes the Google moon base from 2004 to the next level.

Added: A co-worker pointed out that all of YouTube’s featured videos are Rickrolls today. And it looks like Google is going all-out with some 15 hoaxes today. *whew!*

The Internet Storm Center is keeping a list as well.

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)

I appreciate the fact that Apple provides a single updater for all their Windows software. It’s nice to consolidate things a bit with the profusion of updaters for what seems like each and every application (sort of like how every mobile device seems to need its own charger). But it has its flaws. I’ve mentioned some broken UI design, but the most annoying thing is that it tries to install new software instead of just updating what you have.

At work, I have QuickTime and Safari for development purposes. I don’t have iTunes. I don’t need it. I don’t even have speakers hooked up to the computer. But every time a new version gets released, it shows up in the Apple Software Update list, and I have to tell it to ignore it until the next time they update iTunes.

Now that Safari for Windows is out of beta, it’s doing the same with Safari*. And people are complaining. People like John Lilly, CEO of Mozilla, who sees it as an anti-competitive measure that dilutes users’ trust in software updaters.

Personally, I think there is a problem, but I hardly expected it to turn into the firestorm it has, with Asa Dotzler, c|net, digg, Techmeme, [edit] and now Slashdot, [edit 2] Daring Fireball and Wired (it just keeps going!), and dozens hundreds of commenters entering the fray.

There’s a simple solution, and it’s one of those rare cases where Microsoft gets something right in their software that Apple gets wrong.

  1. Create a separate section for software that isn’t already installed, and label it clearly. It can be in the same list, as long as there’s a separation and a heading.
  2. Leave the new stuff unchecked by default.
  3. Added: If set to check automatically, don’t pop up a notice more than once for each piece of not-installed software.

That’s it. Done. Apple still gets to leverage their installer to make people aware of their other apps, but there’s no chance of someone accidentally installing Safari (or iTunes) by accident because they didn’t read the list too closely. Take a look at Microsoft Update and how they (currently) offer Silverlight. It’s in a list of optional software, and it’s not checked until you choose it.

That’s all this really comes down to: sensible defaults and proper labeling.

Update: Well, two out of three ain’t bad.

*I have to admit getting a kick out of the title, “Apple pushes Safari on Windows via iTunes updater,” because my problem is that they’re pushing iTunes on Windows via their Safari updater. It’s a matter of perspective.

Acid2 reference image.After looking at how Safari 3.1 handles the Acid2 test, and finding that under some circumstances/platforms it fails the test, I realized: that one line, with the eyes, has been the cause of most regressions in browsers that previously passed the test.

Rows 4-5 test fallback behavior for objects. The idea is that if a page tries to load an external resource, but can’t—the file is missing, the server’s down, the network’s slow, the browser doesn’t have the right plugin, etc.—the page can provide alternate content. And it can be nested, so you can try, say, a video clip that falls back to an SVG image that falls back to a PNG that falls back to text. Continue reading

Safari LogoGrabbed the new Safari 3.1 this morning, both at work (WinXP) and on the laptop at home (Leopard). Noticed that the website no longer says “Beta” for the Windows version.

Oddly enough, there doesn’t seem to be much chatter from the browser community about it, at least not on sites I follow from work. There may be 25 posts on my RSS reader at home, for all I know.

I wish Apple would make the release notes easier to find. I clicked on the “more info” link in Software Update at home, but didn’t have time to really read it. I wanted to check the list at work, but there’s no menu item, it’s not visible on Apple’s website, and their search engine hasn’t indexed it yet. I had to search Google, and found it from some random person’s Twitter post. (Oh, and Apple? As long as I’m giving you advice, you’re running your site on Apache. Apache has a feature called mod_speling [sic] that will automatically correct a single-error typo when someone hits your site. I highly recommend that you look into it instead of handing out a 404 error whenever someone’s finger slips.)

User interface seems mostly the same as 3.0.

Not sure if it’s new or I just never noticed it, but the history menu has an option to reopen all windows from the previous session. It isn’t the automatic recovery offered by Firefox or Opera, but it’s the next best thing—and quite handy for cases when, for instance, Norton Antivirus has just updated itself and popped up a “will reboot in X seconds” warning, which you didn’t see because you had too many windows open. *ahem*

I believe this is the first browser released that supports embedding TrueType fonts. (IE has been able to embed fonts for years, but you had to convert them first, which may be why you don’t see too many these days.) When WebKit first added the feature last fall, I tested it out on my Les Mis page.

I really like the new developer tools (Prefs→Advanced→Show Develop menu), especially the network timeline. This, combined with YSlow on Firefox (itself an extension to Firebug), will be extremely useful for optimizing site performance.

It gets 77/100 on the Acid3 test, much better than Safari 3.0, which only scored 39/100. WebKit looks like it’s on track to be the first engine to pass again, having hit 93/100 yesterday. Oddly enough, the Acid2 regression is still present on XP (need to compare to the Mac version it displays correctly on the Mac), with an orange band covering the eyes and the border to the right of that band red instead of black.

Another odd thing: when it’s really busy, it seems to revert to a standard window frame instead of its own skin.

Who wants to bet that .Mac will be one of the first webapps to really make use of offline storage?

FirefoxOne of the biggest complaints about Firefox since 1.5 was released has been its high memory usage. Go to a forum anywhere and you’ll get people griping about “have they fixed the leak yet?”

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.

»All pages site-wide with this tag