K-Squared Ramblings

Lit Links

Author chosen to finish The Wheel of Time - When Robert Jordan died, he left behind his work on A Memory of Light, the final volume of his epic fantasy series, The Wheel of Time. His wife & editor has chosen Brandon Sanderson to complete the book, due out in 2009. Jordan was part way through the manuscript, left voluminous notes, and in the months before his death had told the remaining story to his family. There’s also an interview which I’ll have to read when I have more time.

Epic Pooh - Michael Moorcock on the state of fantasy literature, originally written in the 1970s but updated for the 21st century. The title comes from comparing the style of Lord of the Rings to Winnie the Pooh. I have no problem reading and enjoying both his work and Tolkien’s, and it doesn’t bother me that Phillip Pullman dislikes Tolkien’s work as well. (Link via something I was reading a few days ago.)

The Happy Endings Foundation - “originally founded in 2000 by Adrienne Small after she read the first book in A Series of Unfortunate Events by Lemony Snicket to her daughter. As well as making her feel thoroughly miserable, Mrs Small noticed her daughter seemed to take a more negative approach to life.” (Yes, it’s satire.)

And on another note:

Hixie’s Natural Log: Evolution in the species “Companies” - Microsoft’s dominance of the industry has killed off or absorbed many smaller companies. Those that have survived are those with strategies resistant to Microsoft’s tactics. The article looks at Mozilla, Google, and Apple. (via Asa Dotzler)

Safari Blend Coffee

In honor of the release* of Safari 3, here’s a little something we found at Trader Joe’s.

The mug is from the short-lived Mozilla Coffee. It seemed appropriate. Now if I can just track down some Opera Coffee, or Explorer Coffee…

*Safari 3 was included in Mac OS X 10.5 Leopard, released 2½ weeks ago. And it’s included in the 10.4.11 update for Tiger, released today. An updated version of Safari was released today for Windows, but it’s still a beta, according to Apple’s website and the license (even though the about box just says it’s Safari 3.0.4—the same version that’s in Leopard). I’d been planning to hold this until all 3 releases were out, but clearly they don’t feel that the Windows version is quite release-quality yet. So, on the premise that two out of three ain’t bad, I’m posting.

Spreading to the Converted

One of the problems with the ubiquitous Get Firefox! Get Opera! etc. web buttons is that while they might encourage someone unfamiliar with the product to check it out, they’re kind of pointless to someone who already uses your preferred browser. Sure, there’s a sense of, “Hey, this author uses Opera too!” but that’s about all it can do.

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.

Firefox too mainstream for Alternative Browser Alliance

I’ve been thinking about this for a while, but it’s time to refocus the Alternative Browser Alliance. Mozilla’s Asa Dotzler has referred to Firefox and Internet Explorer as the “mainstream browsers” for more than a year now, and it looks like that’s become true.

The web is no longer an IE monopoly. It’s become an IE/Firefox oligopoly. Firefox is no longer an alternative web browser. It’s sold out, its ads are everywhere, and it even allows people to build Firefox-only code.

So, starting today (April 1, 2007), the Alternative Browser Alliance will no longer promote Firefox.

So what will replace it? I thought about Opera, but most of its install base is on cell phones and PDAs, and we all know the mobile web browser is dead, right? Safari? Well, it turns out that WebKit is shutting down.

So the site will be putting its weight behind iCab. It’s as alternative as they come, and it’s guaranteed to remain that way (since it won’t run on Vista).

Update: Yes, it’s an April Fools joke.

Don’t Hurt the Web

The Mozilla Developer Center has just posted some desktop wallpaper promoting open standards, (and the MDC itself) with the theme, “Please don’t hurt the web. Use open standards.”

Apparently the design was a big hit as a poster at SXSW.

For those who haven’t seen it, the MDC is a great developer resource for web developers, describing lots of standards along with Mozilla-specific information.

(via Rhian @ SFX, who notes that the image is available for use under the terms of the Creative Commons Attribution-NonCommercial license. These wallpapers are also covered by the Mozilla Trademark Policy.)

Firefox and Opera: Allies?

Opera Watch posted an interview with Firefox co-founder Blake Ross yesterday, in which he talks about Firefox, Opera, and the relationship between the two. When asked about the rivalry between fans of the browsers, he says, “I think it’s ridiculous. Millions of people out there rely on us to make the Web better, not have pissing contests.” I couldn’t agree more. In fact, I launched The Alternative Browser Alliance primarily in response to that rivalry.

I found it interesting that when asked to describe Opera in three words, Ross’ response was: “Our best ally.”

Web Design is Like Pizza

When web designers switch from focusing on a single browser (usually Internet Explorer) to developing cross-browser sites (usually adding Firefox, sometimes Opera or Safari, ideally all three), they often find that things don’t work as expected in the “new” browser. This can be for a number of reasons, including:

• Bugs or “missing” features in the new browser (whether incomplete support in the new browser, or proprietary features in the familiar browser).
• Broken code on the website being handled differently.
• Different defaults where behavior isn’t well-defined in the specifications.

A big problem is that when you get into the code, a lot of pages aren’t as specific as the authors think they are. When you write code and test it on one browser, you’re not testing that the code is correct, you’re testing that that browser makes the same assumptions you do.

It’s like ordering pizza.

No, really. Let’s say Internet Explorer specializes in Chicago-style pizza, with a thick, chewy crust. And let’s say Firefox specializes in New York-style pizza, with a thin crust. But each can make the other style of pizza on request.

So you call up Internet Explorer and ask for pizza. They deliver you Chicago pizza, and if that’s what you wanted, you figure your order is fine. If you actually wanted New York style, you make sure that next time, you tell them you want that style of pizza.

But let’s say you like Chicago pizza. You get used to calling up IE and just asking for “pizza,” until one day you’re busy, and ask your roommate to order it. He likes to get his pizza from Firefox, so he calls them up, asks for “pizza,” and you get New York style. That’s not what you wanted. Obviously, Firefox pizza is inferior, because they got the order wrong! Well, no, it’s not, and no, they didn’t. They delivered what they were asked for. If you’d told your roommate to ask for Chicago style, Firefox would have been perfectly happy to deliver that style of pizza.

The moral of the story: always be specific with your code. Make sure it’s asking for what you think it’s asking for (validation helps here). And if something doesn’t do what you expect, make sure you didn’t leave that expectation out of your order.

See also: No, Internet Explorer did not handle it properly

(Expanded from a comment I posted at Mozillazine.)

Mozilla + Linux

This is good news: Mozilla will be working more closely with various Linux distributors including Red Hat, Novell, Ubuntu, and yes, even Debian, to coordinate Firefox updates, configuration, etc.

There are two main issues: making Mozilla’s Firefox installer work everywhere (it mostly does, but on some systems you need to install some compatibility libraries first), and keeping the distributions’ versions in sync with the official one.

After the Debian IceWeasel debacle, and Fedora deciding to skip Firefox 2 and wait for Firefox 3, it’s good to know that Mozilla has recognized the problem and is working on it. One key piece of information: Red Hat and Novell will both be providing extended support for Firefox 1.5 past its official EOL next April.

(via Fedora Weekly News)

Camino - Browsing for an Intel Mac

Camino, the Gecko-based web browser designed specifically for Mac OS X, has just released version 1.0… and among the release notes it mentions that it’s a universal binary.

As far as I know, this makes it only the third released web browser to work natively on both PowerPC and Intel Macs, after Safari and Shiira. The Opera 9 previews have been universal binaries, and Firefox plans to have them for their next bugfix/stability release (1.5.0.2, probably sometime next month).

Firefox 1.5

The waiting is over!

Most of the changes since 1.0 have been under the hood. The most noticeable are probably the vastly-improved update system, rearrangeable tabs, a one-button function to clear all private data, and a new preferences setup. There are also improvements to Mac OS X integration (though not as much as one might have hoped for), performance, pop-up blocking, etc. From a web developer’s POV, there’s a lot of neat stuff including partial SVG support and the new <canvas> element from WHATWG (and of course improved HTML/CSS/JavaScript support).

If you’ve already installed Firefox 1.5 Release Candidate 3, this is exactly the same program. Nothing’s been changed except the name on the installer.

On the annoying side, they’ve temporarily closed Spread Firefox to prep for their video marketing campaign. I hate it when people close down a site to prep for a relaunch. It’s not like a building, where you have to keep people away so you can remodel. You can do all the remodeling on a copy, and just drop it into place when it’s done.

Then there’s the drag-n-drop/save-as bug in Linux, where the first time you try to rearrange tabs or bring something up with a file picker, it decides the GTK theme has changed and hangs while it redraws everything. They’ve fixed it for the long-term, but the fix just went in yesterday, so it’s not in the 1.5 release. I’d guess the Linux distros will apply the patch when they build their own packages, and with luck the fix will show up in 1.5.1.

And on a completely unrelated note, this is the 1,000^th post on this site. *whew*!

How Thunderbird’s Scam Detection Works

Since upgrading to Mozilla Thunderbird 1.5 beta 2, I’ve seen a number of messages slapped with a warning label that “Thunderbird thinks this message might be an email scam.” It appears at the top of the message, in the same style as the junk mail notice bar or the warning that remote images have been blocked, and there’s a button to mark the message as “Not a Scam.”

There’s only one problem. Since SpamAssassin and ClamAV do such a good job of catching the phishing scams before they reach my inbox, Thunderbird has yet to catch any actual phish. But there’ve been a lot of false positives. It’s hit LiveJournal reply notices, newsletters from IEEE and Golden Key, a Spam Karma notice from my own blog, and I’ve seen it on both outbid notices and updates to saved searches from eBay.

I found myself wondering just how Thunderbird’s phishing detection decides that a message is suspicious—and how to teach it that the next LJ notice isn’t a scam.

The Thunderbird support website doesn’t seem to have been updated yet. Most of the articles I’ve found only talk about TB adding the feature, not how it works. The best information I found was this Mozillazine forum thread, which included a link to the actual code that makes the decision, in phishingDetector.js. Thunderbird looks at the following:

• Links that only use an IP address, including dotted decimal, octal, hex, dword, or some mixed encoding.
• Links that claim to go to one site, but actually go to another. (Phishers do this to fool you into going to their site. Legit mailing lists sometimes do this with redirectors for tracking purposes.)
• Forms embedded in the email. (This explains the LiveJournal notices.)

It also appears to trap text URLs containing HTML-escaped characters, which explains the Spam Karma reports. In this case the report includes a spammer’s link with ​ in the hostname. The message is plain text, so Thunderbird leaves the entity as-is when displaying it…but decodes it when it creates the link. Result: a link where the text and URL don’t match.

The easiest way to prevent it from freaking out over the next message? Add the sender to your address book. I’m not sure that’s a great idea, since a phisher could guess which addresses you have saved and spoof them, but it’s at least simple. I guess I’ll find out whether it works the next time I get a reply notice from LJ. Update: Adding the sender to your address book doesn’t seem to have any effect.

Update 2 (July 12, 2006): The comment thread’s gotten long enough that I can see people might miss this, so here’s how to disable it:

1. Open Options or Preferences (this will be under the Tools menu on Windows, Thunderbird on Mac, or Edit on Linux).
2. Click on Privacy (there should be a big padlock icon).
3. Click on the E-mail Scams tab.
4. Disable the “Check mail messages for email scams” option and click on Close.

That’s it.

75m Firefoxes!

Whew! The Mozilla Foundation has logged 75,000,000 downloads of Firefox!

Take that number with a grain of salt, of course. At least some of those are manual upgrades (from people who don’t want to wait for the auto-update to kick in), and some are one person downloading it in three places. But it can’t count the copies pre-installed with Fedora Core or Mandriva Linux, or downloaded via P2P—and some of those downloads are immediately pushed across a LAN or stuck on a USB keychain to be installed on a dozen or more computers.

It does show that Firefox continues to hold people’s interest, and the continuing rise in Gecko percentage in web traffic stats shows that, Bill Gates’ comments notwithstanding, people do use it.

(via Mozillazine)

Spinning Beach Balls of Death!

The Mozilla-based Camino web browser for Mac OS X has just launched 0.9 alpha 1, and the release notes* include this item:

Rarely see “beach balls of death”.

I don’t remember whether I’d heard the term before (I recall the “spinning pizza of death,” or maybe of doom), but I knew exactly what it meant.

*In spring 2007, they restructured the website. The release notes for the 0.9 series have been incorporated into the notes for 1.0.

Last of the Lazy Lizard

While cleaning the apartment this weekend, we found a long-forgotten bag of “Lazy Lizard” Mozilla Coffee. RJ Tarpley’s, the company which sold it (and donated a percentage of profits to the Mozilla Foundation) disappeared last summer. By September, I couldn’t even find a whois record. The domain name has since been picked up by a link farm.

It was decent coffee, and it helped support some good software. And I got a nifty mug while they were still in business. There was maybe half a pound left, but 12-month-old decaf coffee just isn’t fit to drink anymore, so instead of brewing one last pot in salute, we tossed what was left.

Simple Browser Categorization

Sometimes you want to know exactly what software people (or bots) are using to view your website. Sometimes all you want to know is which rendering engine’s quirks you need to cater to. To that end, I have here the ultra-simple browser detection algorithm. Just check the User-Agent string for each of the following words, in order:

1. Opera — they spoof IE by default, so check here first. If they ever change this to something else, you’ll be glad you started here.
2. KHTML — this will catch Safari, Omniweb and Konqueror. They mention Gecko, so if you need to treat them differently, check for KHTML first.
3. Gecko — this will catch Mozilla, Firefox, Camino, Netscape 6+, etc.
4. MSIE — this should Internet Explorer and anything else that uses its engine.
5. bot, spider, crawler, or compatible — filter out robots and anything unknown.
6. Mozilla — just about everyone uses Mozilla in their UA string these days, but the rules above should filter most of them out and leave only old-school Netscape.

Of course, Mozilla, Opera and Safari have put much more effort than IE into following the standards, so most of the time you can write your code using the spec and just build in work-arounds. The way I look at it, there are three main categories:

1. Standards-compliant(ish) browsers: Gecko, Opera, KHTML
2. MSIE
3. Everything else

I write for group 1, work-around for group 2 (and sometimes other browsers in group 1), and figure that group 3 (with the exception of Netscape 4, which has a tendency to do things like make links unclickable or hide entire chunks of the page if it doesn’t like your CSS) should at least be able to figure out how the text and graphics break down. It may not look perfect in randombrowser, but it should at least be comprehensible.