Johnny leaves the airport by taxi, ending up in a disreputable part of town. During his ride we see another video phone call with a different interface, and the first brief appearance of some high tech binoculars. I’ll return to these later, for the moment skipping ahead to the last of the relatively simple and single-use physical gadgets.
Johnny finds the people he is supposed to meet in a deserted building but, as events are not proceeding as planned, he attaches another black box with glowing red status light to the outside of the door as he enters. Although it looks like the motion detector we saw earlier, this is a bomb.
This is indeed a very bad neighbourhood of Newark. Inside are the same Yakuza from Beijing, who plan to remove Johnny’s head. There is a brief fight, which ends when Johnny uses his watch to detonate the bomb. It isn’t clear whether he pushes or rotates some control, but it is a single quick action.
This demonstrates an interesting difference between interface design for the physical world and for software systems. Inside a computer, actions are just flipping bits in storage and thus easy to undo. Even supposedly destructive actions such as erasing files can often be reversed. In the real world, the effects of, for example, explosions tend to be much more permanent.
We generally don’t want destructive actions to be too easy to perform, from guns and other things that go boom to formatting computer disks.
A widely used solution in the real world is the safety catch, as with guns, or arming switch, seen in countless thriller films with nuclear weapons. Another example are the two-hand safety switches used in high voltage electrical distribution panels. Activation of these requires two individual actions, separated in time and at least a short distance in space. Some systems, both real and in film, go even further and have covers on the arming switches, so even just preparing for activation requires two separate physical actions.
While the bomb is on his belt, Johnny doesn’t have to worry about accidentally pressing the “explode” button on his watch because the bomb is not active. Only after he has armed it and placed on the door can the watch activate the bomb, so he can take his time and verify whether or not it is necessary before doing so. And when it is active, he can do so very quickly even though he is in the middle of a fight.
But safety catches and arming switches introduce modes to an interaction, which have a bad reputation in interface design. Had the watch-bomb designers followed most conventional GUI design guidelines, there would be no arming switch on the bomb. Instead the watch would have popped up a “Do you really want to explode the bomb (Y/N)?” dialog, possibly with a short delay to ensure Johnny thought about his decision before answering. He would have been decapitated.
Compare to LoTek
Later on in the film we see an example of a poorly designed system without a safety catch. The LoTeks in their bridge home have a defensive “bug dropper”, so called because it drops ancient Volkswagens from a great height.
The bug dropper can be activated by pushing just a single handle. Because there is no safety switch, a guard accidentally drops a flaming VW Beetle onto the lead characters, nearly killing them.
Conclusion
From the description above it would seem that safety catches are the obvious solution. But of course it’s more complicated than that. Consider what would have happened if Johnny had met friends instead of enemies and settled down for a conversation. Thirty minutes later they’ve agreed on another meeting, and Johnny taps his watch to bring up the reminders app. Oops!
Should the bomb have disarmed itself after a given time period? If it did, how would Johnny be notified of this?
Most of us do not design interfaces for lethal hardware and life or death situations. There are however an increasing number of drones and other physical devices which are now remotely controlled from phone or tablet apps rather than dedicated hardware controllers as in the past. The “Internet of Things” will bring even more real world actions under computer interface control. In the future, we will most likely see more of these safety catches and arming switches in computer interfaces, and we need to figure out how to use them properly.
Once Johnny has installed his motion detector on the door, the brain upload can begin.
3. Building it
Johnny starts by opening his briefcase and removing various components, which he connects together into the complete upload system. Some of the parts are disguised, and the whole sequence is similar to an assassin in a thriller film assembling a gun out of harmless looking pieces.
It looks strange today to see a computer system with so many external devices connected by cables. We’ve become accustomed to one piece computing devices with integrated functionality, and keyboards, mice, cameras, printers, and headphones that connect wirelessly.
Cables and other connections are not always considered as interfaces, but “all parts of a thing which enable its use” is the definition according to Chris. In the early to mid 1990s most computer user were well aware of the potential for confusion and frustration in such interfaces. A personal computer could have connections to monitor, keyboard, mouse, modem, CD drive, and joystick – and every single device would use a different type of cable. USB, while not perfect, is one of the greatest ever improvements in user interfaces.
Why not go wireless? Wireless devices remove the need for a physical connection, but this means that anyone, not just you, could potentially connect. So instead of worrying about whether we have the right kind of cable, we now worry about the right kind of Bluetooth pairing and WiFi encryption password scheme. Mobile wireless devices also need their own batteries, which have to be charged. So wireless may seem visually cleaner, but comes with its own set of problems.
As of early 2016 we have two new standards, Lightning and USB-C, that are orientation-independent (only fifty years after audio cables), high bandwidth, and able to transmit power to peripherals as well. Perhaps by 2021 cables will have made a comeback as the usual way to connect devices.
2. Explaining it
Johnny explains the process to the scientists. He needs them to begin the upload by pushing a button, helpfully labelled “start”, on the gadget that resembles an optical disk drive. There’s a big red button as well, which is not explained but would make an excellent “cancel” button.
It would be simpler if Johnny just did this himself. But we will shortly discover that the upload process is apparently very painful. If Johnny had his hands near the system, he might involuntarily push another button or disturb a cable. So for them, having a single, easily differentiated button to press minimizes their chance of messing it up.
1. Making codes
He also sticks a small black disk on the hotel room’s silver remote control. The small disk is evidently is a wireless controller or camera of some kind. The scientists must watch the upload progress counter, and as it approaches the end, use this modified remote to grab three frames from the TV display, which will become the “access code” for the data. (More on this below.)
None of the buttons on this remote have markings or labels, but neither Johnny nor the scientist who will be using it are bothered. Perhaps this hotel chain tries to please every possible guest by not favouring any particular language? But even in that case, I’d expect there to be some kind of symbols on the buttons and a multilingual manual to explain the meaning of each. Maybe Johnny spends so much time in hotel suites that he has memorised the button layout?
Short of a mind reading remote that can translate any button press into “what the user intended”, I have to admit this is a terrible interface.
(There is a label on the black disk, but I have no idea what it means or even which script that is. Anyone?)
0. Go go go
Johnny plugs in his implant, puts on a headset with more cables, and bites down on a mouthguard. He’s ready.
The scientist pushes the start button and the upload begins. Johnny sees the data stream in his headset as a flood of graphics and text.
Why does he need the headset when there is a direct cable connection to the implant? The movie doesn’t make it explicit. It could be related to the images used as the access code. (More on this below.) Perhaps the images need to be processed by the recipient’s own optic nerve system for more reliable storage?
Still, in the spirit of apologetics we should try to find a better explanation than “an opportunity for 1995 cutting edge computer generated graphics.” Perhaps it is a very flashy progress indicator? Older computer systems had blinking lights on disk drives to indicate activity, copied on some of today’s USB sticks. Current-day file upload or download GUIs have progress bars. As processing and graphics capabilities increase, it will be possible for software to display thumbnails or previews of the actual data being transferred without slowing down.
Unfortunately there is an argument against this, which is that the obvious upload progress indicator is a numeric display counting gigabytes down to zero, and it makes a fast chirping sound as a sonic indicator as well. The counter shows the data flowing at gigabytes per second, the entire upload lasting about a minute. There’s also the problem that it’s not Johnny who is interested in knowing whether the upload is scientific data rather than, say, a video collection; but the scientists, and they can’t see it.
As the counter drops below one hundred, the scientist points the remote with black disk at the TV display, currently showing a cartoon, and presses the middle button. The image from the TV appears overlaid on the data stream to Johnny. This is a little odd, because Johnny assured the scientists that he wouldn’t know what the access codes were himself. Maybe these brief flashes are not enough time for him to remember these particular images among the gigabytes of visual content. But the way they’re shown to us, I’ll bet you can remember them when they come up again later in the plot.
Two more images are grabbed before the counter stops. When the upload finishes, the three images are printed out. (In the original film this is shown upside down, so I have rotated the image.)
Tagged:
So what are the images for? The script isn’t clear. I suggest that the images are being used as the equivalents of very large random numbers for whatever cryptography scheme protects the data against unauthorised access. Some current day systems use the timing of key presses and mouse movements as a source of randomness because humans simply can’t move their fingers with microsecond precision. Here, the human element makes it impossible to predict exactly which frame is chosen.
Humans also find images much easier to recognise than hundred digit numbers. Anyone who has seen the printout will be able to say whether a particular image is part of the access code or not with a high degree of confidence. In computer systems today, Secure Shell, or ssh, is a widely used encrypted terminal program for secure access to servers. Recent versions of ssh have a ‘randomart’ capability which shows a small ASCII icon generated from the current cryptographic key to everyone who logs on. If this ASCII icon appears different, this alerts everyone that the server key has been changed.
There’s one potential usability problem with the whole “pick three random images” mechanism. The last frame was grabbed when the counter was very close to zero. What would have happened if he had been too slow and missed altogether? Wouldn’t it be more reliable to have the upload system automatically grab the images rather than rely on a human? Chris suggests that maybe it secretly did grab three images that could have used without human input, but privileged the human input since it was more reliably random.
Quick aside: You may be asking, if images would be so wonderful, why aren’t we using them in this way already? It’s because our current security systems need not just very large random numbers, but very large random numbers with particular mathematical properties such as being prime. But let’s cut Johnny Mnemonic some slack, saying that by 2021 we may have new algorithms.
OK, back to the plot.
-1. Sharing the codes
The access codes are to be faxed from Beijing to Newark, although this gets interrupted by the Yakuza intruders. This is yet another device with unmarked buttons.
This device makes the same beeps and screeches as a 1990s analog fax machine. Since we’ll later learn that all the fax messages and phone calls are stored digitally in cyberspace, this must be a skeuomorphism, the old familiar audio tones now serving just as progress indicators.
As with other audio output, the tones allow the user to know that the transmission is proceeding and when it ends without having to pay full attention to the device. On the other hand, there is potential for confusion here as the digital upload is (presumably) much faster. Most current day computer systems could upload three photos, even in high resolution, well before the sequence of tones would complete. Users would most likely wait longer than actually necessary before moving on to their next task.
-2. Washing up
During the upload Johnny clenches his fists and bites his mouthguard. When the upload finishes, he retreats to the bathroom in considerable pain. At one point blood flows from his nose, and he swipes his hand over the tap to wash it down the drain. The bathroom announces that the water temperature is 17 degrees. We’ll come back to this later.
As Make It So emphasises in the chapter on brain interfaces, there is nothing in our current knowledge to suggest that writing or reading memories to or from a human brain would be painful. On the other hand, we know that information in the brain isthe shape of the neurons in the brain. Who knows what side effects will happen as those neurons are disconnected and reconnected as they need to be? We don’t know, so can’t really say whether it would hurt or not.
-3. Escaping the Yakuza
As mentioned in a prior post, while he is in the bathroom, the motion detector Johnny installed on the hotel door isn’t very effective and the Yakuza break in, kill everyone else, and acquire the second of the three access code images. Johnny escapes with the first image and flies to Newark, North America.
After the gravitic distortion is discovered, Barcalow flips a toggle switch upwards with his thumb. As Ibanez confirms that “Gravity is 225 and rising,” the light on the bridge turns red, and Barcalow turns to a monitor.
The monitor (seen above) features a video window in the top center. Along the left side of the screen 11 random numbers report the COMM STATS INTERSHIP. Along the right side of the screen 11 other random numbers report the COMM STATS INTRASHIP. Beneath the video some purple bars slide in and out from a central column of red rectangles. One of these rectangles is bright yellow. Beneath that a section reports SCANNING FREQUENCIES as 21 three-character strings, some of which are highlighted as red. At the bottom of the screen blue and yellow-green smears race back and forth across a rectangle. Everything is in Starship Troopers‘ signature saturated colors and a block font like Microgramma or Eurostile.
These details are almost immediately obscured, as Deladier looks up from her laptop (looking presciently like a modern Macbook Air with its aluminum casing) to look at the video monitor to demand a “Report,” and the video grows larger to fill the screen.
Here the snarky description must pause for some analysis.
Analysis
The red alert mechanism is actually pretty good. Both the placement of its switch at shoulder level and the fact that it must be flipped up help prevent against accidental activation. The fact that it’s a toggle switch means it can be undone with ease if necessary. The red light immediately provides feedback to everyone on the bridge (and throughout the ship?) that the system has gone into a red alert. No other action is necessary to alert the person who needs to be informed, i.e. the Captain. The only other improvement might be a klaxon warning to alert others who are sleeping, but it’s entirely possible that very thing is happening elsewhere on the ship, and the bridge is spared that distraction. So full marks.
The user interface on the monitor seems pretty crappy though. If someone is meant to monitor COMM STATS—intership or intraship—I cannot imagine how a column of undifferentiated numbers helps. A waveform would be more useful to track activity across a spectrum. Something. Anything other than a stack of numbers that are hard to read and interpret.
The SCANNING FREQUENCIES is similarly useless. Sure, it’s clear that the ship’s systems are scanning those frequencies, but the three-character strings require crew to memorize what those mean. If those frequencies are defined—as you imagine they must be to be at all useful as static variables—then you can remove the cognitive weight of having to memorize the differences between JL5 and LQ7 by giving them actual names, and only displaying the ones that have activity on them, and what that activity means. Does someone need to listen in? Shouldn’t that task be apparent? And why would that need to be shown generally to the bridge, rather than to a communications officer? And I’m not sure what those purple squiggles mean. It’s nice that they’re animated I guess, but if they’re meant to help the user monitor some variable, they’re too limited. Like the sickbay display on the original Star Trek, knowing the current state is likely not as useful as knowing how the information is trending over time. (See page 261 for more details on this.) So trendlines would be better here. The little sweeping candy colored smears are actually okay, though, presuming that it’s showing that the system is successfully sweeping all frequencies for additional signal. Perhaps a bit distracting, but easy to habituate.
It’s nice that the video screen fills the screen to match the needs of the communicators. But as with so many other sci-fi video calls, no effort is made to explain where the camera is on this thing. Somehow they can just look at the eyes of the other person on the monitor, and it works. This feels natural to the actors, looks natural to the audience, and would be natural in real life, but until we can figure out how to embed a camera within a screen, this can’t work this way, and we’re stuck with the gaze monitoring problem raised in the Volumetric Projection chapter of the book with the Darth Vader example.
So, all in all, this interface is mostly terrible until it becomes just a videophone. And even then there are questions.
Snarky description continues
Picking up the description where I left off, after the Captain demands a report, Barcalow tells her quickly “Captain, we’re in the path of an unidentified object heading toward us at high speed.” Ibanez then looks down at her monitor at the gravity well animation, to remark that the “Profile suggests an asteroid, ma’am.” You know, just before looking out the window.
Honestly, that’s one of the funniest two-second sequences in the whole movie.
