Today I found myself thinking of Terminator 3, specifically the plotline in which all kinds of random computer crashes are spreading across the internet.

For obvious reasons.

In today’s real world incident, it’s a bug in an auto-pushed update for widely-used security software by CrowdStrike, ironically used to protect mission-critical systems. In the two-decade-old movie (pardon me while I turn to dust), it’s Skynet spreading itself across the internet.

At the time, I thought the nuclear strike would wipe out a lot of internet infrastructure, destroying major nodes and leaving pieces of Skynet disconnected from each other. A commenter remarked that he’d been doing research for a novel and experts agreed that enough of the major nodes and infrastructure would survive the attack to keep the network functioning.

The interesting thing: Neither of us had heard the story that ARPANET (the internet’s predecessor) had been designed for that scenario. These days, it’s pretty much repeated as gospel… but apparently it wasn’t a design goal, and the idea that it was can be traced back to a 1991 article in Network World magazine that conflated ARPANET with a different network design, which was never actually built. (via)

From there it took on a life of its own for the same reason many urban legends (and conspiracy theories) do: it made a better story.

A few weeks ago, Szczezuja asked the GeminiSpace community: How you were using the Internet in 1991-1995 and 1995-2005?

This may be a bit longer than asked for, and I thought about breaking it into smaller pieces, but I decided it would be more appropriate for a Gemini post to be one single unit.

1991-1995: Discovery

By 1990 my family had moved on from Atari’s home computer line to what was then known as an “IBM Compatible” PC. I missed out on the BBS era, except for one time we had to download a software patch. My first taste of being online came through walled gardens during my last year of high school:

Prodigy, which I seem to remember having a GUI frame around a mostly text interface (except for banner ads in the frame). I think it even ran under DOS. I remember looking at some message boards about theater, but that’s about it.

AOL, which at the time was much friendlier to use, ran on Windows, and had its own system of message boards, email, etc. But again I don’t remember much about what I did with it until later on.

September

Then I got to college and discovered “Mosaic” at the computer labs. This web thing was really cool! There was a database of movies that I could search, I could find all kinds of sites on this collection of categorized links called Yahoo!, and people were posting things like fan pages collecting all of the Animaniacs cultural references!

Egad! Keeper’s Cartoon Files is still online!

There was a campus-wide Unix network that you could connect to through a dial-up terminal app, or the WYSE terminals scattered around campus. Windows and/or Mac computer labs at major departments. The engineering, computer science, etc. labs also had bullpens full of graphical UNIX terminals (I think they were the classic Sparc “pizza boxes” running SunOS and later Solaris), which was how I first encountered Mosaic and Netscape.

Back at my dorm, though, I had to dial up to a terminal. I could use text-based applications like Lynx for web browsing, or PINE for email. Sometimes I’d check my email (a string of auto-generated letters and numbers based on my major at a fourth-level domain based on the department that handled student email) at a text-based terminal in one of the computer labs or scattered around campus.

Continue reading

The WaSP Buzz’ article on a new mobile web browser test made mention of phones that can read QR Codes—one of several types of 2-D bar codes that you see on things like shipping labels. In this case, the idea is that you can point your phone’s camera at the QR code and it’ll decode it and send you to the appropriate URL.

My first thought was that this was just like the CueCat, which was a bar code scanner that you could plug into your computer’s USB port, then scan bar codes in magazines, or on cans of soda, or whatever, and it would tell your computer to bring up relevant information. It was marketed in the late 1990s, during the tech boom… and it was a total flop. No one wanted them. The company went under and had millions of the little scanners sitting around unsold.

But now there are multiple schemes in use for object hyperlinking. In addition to graphical codes, there are RFID tags, GPS coordinates, and short text codes that you can easily type into an SMS message or a web portal.

So why is this sort of thing working now, 10 years later? Is it a societal change? Was the CueCat ahead of its time?

I think there are two reasons:

  • CueCat was a single-purpose device. All the applications listed involve smartphones or other multi-purpose handheld devices. No one wanted a device that would only scan bar codes, but a phone/camera/browser/MP3 Player/bicycle that also scans bar codes? Sure, why not?
  • CueCat was tied to the desktop. Sure, you could plug it into a laptop computer, but you’d still have to take the object over to your computer to scan the bar code. Unless you’re a lousy typist, swiping the CueCat across your can of Coke isn’t that much easier than typing in www.coke.com. As a home user, you’re not likely to be scanning a dozen objects in a row (unless you’re cataloging all of your books for LibraryThing).

All the applications listed on that page are mobile. A tagging scheme does give you an advantage when you’re out walking down the street and see something interesting. It’s much easier to punch in a short number than to try to type a URL on most phones, easier still to point your camera at a graphic, and dead simple to pick up an RFID tag or pull in GPS coordinates.

Update 2024: It’s funny: in the early 2010s I remember jokes about how no one outside of a marketing department had ever scanned a QR code, but now they’re all over the place, both for linking objects (a sign on a fast food door to go to their online ordering service, a code on an instruction manual to open a site with jump to a site with any changes since printing) and for sending data between devices (communications apps, 2FA apps, starting a download on a mobile device using a QR code shown on a desktop display).