Old hat, but thought I’d throw a monkeywrench into the spammer’s game with a local dose of wpoison. Back in ’97, a spammer told Wired that this stuff didn’t work – that his Extractor bot could add 4,000 – 5,000 bounces an hour to a rejects list. But this script is infinitely recursive — unless the spambots are sufficiently clever, they should get caught in it indefinitely. And if enough people ran similar pages, surely it would make some difference. Yeah, I know, wishful thinking. Ah well, it’s free and can’t hurt.
iPhoto’s Lame-Oh Randomizer
Shot over 300 images over the Minnesota vacation, then whittled down to 120. The Achilles’ heel of digital photography is that there’s no risk/no expense, which encourages you to shoot five variants of everything, rather than one well-conceived shot. Nobody has any time, so the collections never get edited properly and you end up with mountains of superfluous bits to surf through in the future. With analog, each shot costs (financially, environmentally), so the image is conceived in the mind before being committed to film. Analog images are somehow less disposable.
It’s kind of like the difference between composing at the typewriter vs. the word processor (I wrote most of my college papers with a typewriter, only started using the UCSC mainframe during my senior year). When typing, mistakes are costly. So you roll your eyes, lick your lip, scratch your head, and conceive an entire paragraph mentally before committing to paper. Work from an outline so the pages come out in the right order. With word processing, you enter the process of infinite revision, spray your thoughts all over the page and let god sort ’em out (or do it yourself). Thoughts are more malleable with a word processor.
Anyway. Discovered last night that if you set iPhoto‘s slide show feature to randomize the images in an album, you’ll start seeing the same images over again very quickly.
– Displayed images are not dropped from the random queue
– The algorithm clearly favors some images, skipping others
Above: Miles at 11 months on the shores of Gull Lake, MN. Cousin Roya with famous goofy elastic mug.
Biodiversity
In the BeOS days there was a fair bit of argument (no doubt repurposed from Linux turf) analogizing the healthy necessity of biodiversity in nature and platform diversity in the computing world. This line of thought beautifully re-played in Martin Price’s recent piece on Platform Diversity.
Personally, I’m sick of hearing about keeping systems secure from so-called “security experts.” All they ever talk about is patching Windows. You never hear one suggest that it might be a good thing if we weren’t all running the same stupid software. Of course they don’t. The lack of security in Windows is their bread and butter.
Thanks baald.
BeOS Zettel
Three bits of BeOS-related stuff bubbled to the surface today.
* Ludovic Hirlimann contacted me looking for a shout-out. He scored one of the really early AT&T Hobbit-based BeBoxen at an auction a while ago. Here is the version of BeOS it runs. Recently the hard drive died, and Ludovic needs to reinstall, and therein lies the problem — the machine won’t take any of the “recent” versions of BeOS — he needs the antique Hobbit-system install floppies, or a disk image from another machine. Contact him if you can help. He’s looking for the GUI version, not the early-early CLI-only system.
* While prepping some content for matthewsperry.org, got to corresponding with Matt Ingalls, who wrote some cool BeOS software for computer/human improvisation back in the day. Turns out that Ingalls now runs the Transbay Creative Music Calendar, and hosts it on Robin Hood for BeOS — the same httpd server that drove betips.net for years. I’m just amazed that there are not only still so many active BeOS users out there, but that there are still BeOS-hosted web sites. Groovy.
* Congrats to ex-Be employee and blogging friend Dan Sandler for being one of the Slashdot T-Shirt contest winners. I really do like Dan’s design the best, and I’m not just saying that.
Mac Market Share
Daring Fireball makes some good points about the shrinking Macintosh market share.
Fifteen or 20 years ago, personal computers were generally only purchased and used by people who were “into” computers. Today, however, many computers are purchased for use as generic business machines, modern-day typewriters and adding machines.
It does seem that the more people are “into” computers, the more likely they are to be Mac users (not suggesting a direct correlation, only a perceived correspondence). And it is gratifying to see some journalists grok that comparing Mac and PC marketshare is comparing apples and oranges, so to speak. Apple doesn’t try to compete in all computing market segments. May as well critique sports cars or riding mowers for not having the same marketshare as SUVs.
End of the Road for SMTP?
CNET wonders whether SMTP has outlived its useful life. At first I assumed they were referring to the problem of open relays, but the gist is that SMTP is too trusting — it behaves as if you are who you say are. No accountability = spammer’s delight. In fact, the creator of SMTP is amazed it’s still around. I’m skeptical that a non-spoofable protocol could be developed, even in theory.
XServe Online
One distraction after another for weeks has kept me from spending much time prepping the XServe, but got to get cozy again with it this week. Today finally dropped it in the rack and went into production. The Win2K machine had become so fragile and unpredictable I really didn’t expect it to live this long – could no longer start or stop any services, drag files, or access any properties panels. Windows eats itself, scares the hell out of me sometimes (virus hunts turned up nothing). For the first time since I’ve been at the J-School, I feel 100% good about the server situation.
The dual 1GHz XServe is lightning fast, a dream to work with, but it was surprising to discover how different from OS X client it is. Lots of prefs panels moved to other locations or integrated into other functions, and lots of new utilities not found in X client. They’ve done a pretty good job of creating a workable GUI for the most-used Apache config options, including virtual hosts. This is tricky though, since it means a GUI panel reading and writing text files. So what they’ve done is provided a standard httpd.conf, which in turn has an include for httpd_macosxserver.conf. The latter is machine read/writable. You can hand-edit either of them, with a few caveats.
Other stuff present in OS X Server not found in client (though most anything can be installed in client, they’ve done a great job of integrating and providing interfaces for this stuff in Server): Tomcat (JSP), PHP/MySQL, QuickTime Streaming Server, LDAP / Active Directory integration, full user/group mountpoints/permissions controls (using either locally stored or directory users), WebObjects, MacManager (for remote management of lab Macs), NetBoot (lets you host a disk image that networked client OS X machines will seek out and boot from), POP/SMTP/IMAP mail serving (being overhauled for Panther), a full suite of server monitoring tools (CPU temp, blower speed, disk space etc. — will email or page notifications on problems), a full suite of remote control apps, fully configurable FTP server, SLP tools… the list goes on.
Migrating from Win2K was mostly a matter of transferring my httpd config options into the new arrangement, adjusting a bunch of PHP includes, appropriately unix-ifying permissions on the MySQL databases, setting up logins and shares parallel to what we had, locking things down as necessary. Still have some less-apparent work to do (most notably getting a replacement search engine set up), but it’s going to be great to not have to sit under the fans in the server room to do it!
Design Is the Art of Making Choices
User Interface Design for Programmers includes some great examples of terrible interface choices made by programmers. I like the point that any app’s Options panel is an anthropological record of arguments that took place inside the company.
Should we automatically open the last file that the user was working on? Yes! No! There is a two week debate, nobody wants to hurt anyone’s feelings, the programmer puts in an #ifdef in self defense while the designers fight it out. Eventually they just decide to make it an option.
And everyone can relate to his skewering of the wizard that appears when you first launch a Windows help file. Thanks Lars.
TiGutz
Had a great visit from an Apple rep yesterday, came to help us solve some persistent Final Cut Pro lab issues. When he booted his laptop, saw this great wallpaper — an x-ray of the very TiBook he was using. He sent me a copy. Higher-def version for posterity here. Something about this seems vaguely naughty, like it must have felt in the 1800s to catch a glimpse of a woman’s calf or something.
Remembering Netscape
A few people have asked how I feel about the death of Netscape, so thought I’d peck out (still one-handed) a browser evolution brain dump.
Netscape wasn’t the first browser I ever used — Max and I first turned on to the Web at ZiffNet via Cello, and later Spyglass Mosaic. Looking back, it’s almost impossible to imagine an interweb with no corporate presence, no ads, no porn, no spam, and no Internet Explorer. But that was the early web Netscape was born into — flat grey, plain text, blue links, and a few images. And yet, between around 1994 and 1996, Netscape became synonymous with the web itself.
Over the next few years web technology exploded and it was all developers could do to hang on. Netscape brought us background colors and tiles, tables, animated GIFs, frames, layers, and tons of other innovations now considered so fundamental we take them for granted. Netscape even brought us the almighty blink tag (if the word “blink” there isn’t blinking, consider yourself lucky). It seems almost ho-hum in retrospect, but it really was an exciting time. The sky was the limit, the ground was moving fast, the self-publishing door was wide open, and people were coining and abusing phrases like “the internet changes everything.”
For those reminiscing along with me here, bake your noodle on the memory that browsers were not always free. Navigator (and later, Communicator) cost around $30, only being forced to go free on later to respond to IE being free (keep in mind that Microsoft had other revenue streams, Netscape did not). How strange is it that Office still costs money while Explorer doesn’t?
What’s actually surprising is that Netscape held on as long as it did. Navigator has been losing share for a very long time, and Mozilla gets all the non-IE attention anyway. When AOL acquired Netscape, it seemed there might be enough non-IE momentum in the gigantic AOL userbase to re-ignite the browser wars, but that too fizzled when AOL decided to use IE at its core after all.
Let’s face it — Netscape may have innovated dozens of web technologies, but Navigator did not remain the best browser, and many of Netscape’s innovations were rejected by the W3C (e.g. OBJECT was accepted over EMBED, and Netscape’s weird, proprietary LAYER approach was rejected in favor of the much cleaner DIV/CSS model). In fact, Netscape 4.x’s CSS support was so half-baked that it single-handedly delayed broad CSS deployment at probably thousands of organizations for years. I personally excised it from dozens of J -School Macs rather than wrestle with CSS workarounds to accommodate its frustrating brokenness. Netscape 6 looked promising, but was ultimately a dud.
Anyway. The news itself isn’t that exciting — Netscape is already pretty much irrelevant, and has almost become synonymous in developers’ minds with “legacy browser.” Watching Apple choose the little-known KHTML over Mozilla for Safari was emblematic of Netscape’s current lack of relevance (not to mention performance). What’s interesting is that the rise and fall of a great company and such a successful innovator can occur in such a short period of time. That a single product can so fundamentally alter the way we interact with information, and that the creator of that product can be slaughtered in an anticompetitive marketplace with virtual impunity in the course of a few years.
But Mozilla lives on, with a user base that seems to be growing rather than shrinking. If there’s any silver lining here, it’s that Mozilla devs won’t have to compete for attention from Netscape. And while companies like Netscape, who are bound by the profit motive, may fail in the marketplace, open source projects are immune from the wiles of capitalism in its most raw form (though open source has other weaknesses, such as misdirection and ill communication).
Thanks for the good times, Netscape. I’ll never forget the original pulsing purple ‘N’ in Netscape 1.0.
