afongen

New three-column design. I made the “mistake” of implementing it without testing in IE/Windows. 8 hours later, settled in at work, I give it a shot in IE6/Win and a couple sections overlap. Stupid friggin’ browser.

I should not be so quick to judge. As I keep pointing out to a colleague of mine who criticizes what Mozilla does to his designs, just because a browser does not act as you expect does not mean that it is wrong. It’s quite possible — probable, even — that in my tweaking here and there I broke something. It’s also possible, of course, that I need some weird workaround for a bug in IE6. I very much would like to avoid ugly hack workarounds, so I may end up having to go to a simpler design.

Just as well, because while thinking about how to fix it I realized that I’m not sure I want a three-column design. So after a quick workaround, back to the drawing board…

Update: for the record, it’s a problem with IE. So there.

Reading about <link>ed RSS feeds, I’m interested. Good idea. “Say, Sam,” I tell myself, “why don’t you check that out with Mozilla’s Site Navigation Toolbar?” A fine idea. But I can’t find it. In vain I methodically check through the preferences. Oh, great. It’s not in the Mac builds. I thought I remembered it there, but maybe not. Hm, maybe on OS X. Nope. Rats.

Wait! Release notes! Maybe I can dig through the release notes and find out whether it’s available for the Mac. Hey, there it is:

The Site Navigation Bar, also known as the Link Toolbar, is not available for this release. (Bug 138496)

Ah. No one has it in RC3. Bummer.

Fink, a project for bringing open source Unix software to Mac OS X, is making KDE available for OS X. Oh yeah. It’s still experimental, though (that is, “There are no guarantees that it won’t delete your hard drive, kill your dog, put water in your gas tank, or make parts of your body randomly explode.”). Doesn’t mean it isn’t good for a lark.

The State of Minnesota will soon stop printing and mailing paper copies of our paystubs (for those of us who do direct deposit) and is making paycheck information available on the Web. Great! I’m glad to see this, and especially glad that the site isn’t blocking browsers other than Internet Explorer on Windows. They’ve been known to do that. There are some minor issues with how it interacts with Mozilla, but nothing that prevents my access to the content.

Well, there is one thing: the site is receiving more traffic than they anticipated and it’s unresponsive. Connections are sometimes just outright refused. They say that they didn’t expect the traffic. Excuse me?! They didn’t anticipate heavy traffic? Why in the world would they not think that some 15,000 50,000 State employees would be hitting this thing on the day that it’s announced? Or on payday?

Sigh.

I’m trying to be polite because these people are my colleagues. But I’m sure you can imagine what I’m thinking.

Optimizing PHP, in which

we explain why optimizing PHP involves many factors which are not code related, and why tuning PHP requires an understanding of how PHP performs in relation to all the other subsystems on your server, and then identifying bottlenecks caused by these subsystems and fixing them. We also cover how to tune and optimize your PHP scripts so they run even faster.

This includes tips for PHP on IIS and Windows, as well as (of course) Apache and Unix.

Not to say that there’s nothing about writing code, either. I learned, for example, that references don’t provide performance benefits for non-object variables. In fact, they may hurt performance. Whaddya know.

Minnesota weblogs.

I was chatting with a coworker yesterday and mentioned my weblog. He wrote, “I hadn’t even heard of blogs before last months wired mag … now I’m bein’ referred to a colleague’s.” Well, here are a few more.

Weblogs have been so much in the news lately that I forget that not everyone knows what they are, much less follows several (or several dozen). It does make me question whether the Powers That Be will be interested in the idea of blogging the MnSCU IT conference, since they may not even know what weblogs are in the first place. I suspect that if there’s enough interest in it from a few people like our college webmasters, we’ll just have to do it to show 1) that it can be done, and 2) whether it’s worthwhile. There’s a strong chance that I’m the only one who’d be interested.

Last night we went to a CD release concert for local jazz vocalist Debbie Duncan. She is arguably among the top 10 reasons to live in Minnesota. Phenomenal talent. Sadly, her CDs have been really hard to get. Hopefully that will be different with this new one, Travelin’ at the Speed of Love.

Dr. Dobb’s Technetcast has MP3s of keynotes and other interesting things from the O’Reilly’s recent Emerging Technology Conference. One of these days I have to find a way to make it to one of these things.

It’s exciting to see the conference being blogged by a whole slew of attendees. The “official” coverage is interesting enough, but I will be interested to see how O’Reilly integrates blogging in its future conferences. I’ve been wondering, too, if it would be worthwhile trying to do something like that at the next MnSCU IT conference. Donno who’d read it, though.

Update: Dave Winer writes about blogging conferences, and points to a weblog devoted to it.

I’ve talked about Jabber enough that I feel that I should give a brief overview for those who aren’t inclined to dig too far beyond the simple links that I’ve provided.

Jabber (jabber.org, jabbercentral.com) was originally set up as an instant messaging service that allows people on different IM networks (AIM, ICQ, MSN Messenger, etc.) to communicate. Otherwise, for example, AIM users can’t chat with ICQ users. Jabber is an open source, standards-based, XML-based IM framework — all messages, routing, etc. is handled with XML. There are Jabber clients for most platforms that people use in real life, and all the sorts of things you’d hope to find in an IM system: basic IM, chat, group chat, even whiteboard. Pretty slick, really.

Ah, but wait. That’s not all. Because Jabber is in essence a system for routing XML messages, there’s nothing that says that those messages need to be restricted to IM and chat. Jabber users don’t even have to be people. Any system that uses XML to exchange data can do so using Jabber — with all the built-in benefits of presence management, security framework, etc. Quick example: an app that tracks stock prices or network traffic, then notifies you when you come online of anything interesting — or sends you a text message, or communicates with a web service via XML-RPC, or whatever.

That’s why it’s cool for users and developers. Another advantage is that it’s free, open source, and extensible. An organization can set up its own Jabber server. Messages can also be encrypted with SSL and/or PGP. Instead of relying on an external service like AIM (perhaps a problem for security or reliability reasons), an organization could have its own self-contained IM system. Most Jabber development to date has been on Unix, but there are Windows and Java versions available, as well. For those who aren’t comfortable with free software, there is a commercial version and support available (jabber.com). And hey, get over it.

On the IM side, AOL has historically been antagonistic to Jabber, periodically changing the AIM protocols and necessitating a frantic couple days of reverse engineering (something that I’m no longer sure is legal under the DMCA, at least in the US). AOL has even blocked access from the jabber.org server, so if you want to communicate with AIM users you need to use another server. Perhaps set up your own.

That’s it in a nutshell. Peter Saint-André (whose name you’ll start to recognize) has written a very good user guide, which you should read if I’ve piqued your interest. Then install a Jabber client and send me a message. I don’t really feel like publishing my Jabber ID on the Web, so send me email first (sam@afongen.com). Ah what the hell. It’s afongen@myjabber.net afongen@jabber.org. I look forward to hearing from you.

I was chatting with someone today (she was using AIM, I was using Jabber) when it struck me that it’d be interesting to see how all chat slang’s changed since I was a heavy IRC user back in the day. brb, gtg, l8r, LOL, etc. What’s new, what’s old? I have a sneaking suspicion that the evolution is driven by teenage AIM users, which is why I’m unlikely to do any serious research. I’m sure some grad student somewhere’s already doing this.