Rebel videoscope

Talking to Luke

Hidden behind a bookshelf console is the family’s other comm device. When they first use it in the show, Malla and Itchy have a quick discussion and approach the console and slide two panels aside.

SWHS-rebelcomms-02

The device is small and rectangular, like an oscilloscope, sitting on a shelf about eye level. It has a small, palm sized color cathode ray tube on the left. On the right is an LED display strip and an array of red buttons over an array of yellow buttons. Along the bottom are two dials.

SWHS-rebelcomms-03

Without any other interaction, the screen goes from static to a direct connection to a hangar where Luke Skywalker is working with R2-D2 to repair some mechanical part. He simply looks up to the camera, sees Malla and Itchy, and starts talking. He does nothing to accept the call or end it. Neither do they.

We also see the conversation from Luke’s perspective as well. It’s even more oscillioscopey, with lots of dials, switches, and sliders to either side.

SWHS-rebelcomms-06

So this all might be intriguing (and right in line with agentive design) but before we start to investigate, we need to look at another instance of its use. Just like the Imperial-issie Media Console, this functions differently later in the same show.

Talking to Leia

SWHS-rebelcomms-08

After Itchy’s SFW living room masturbation chair sequence, the camera cuts to Leia and C-3PO in an unspecified office somewhere. The droid works at a console for a moment and finally turns a dial. In the Wookie household, a loud dee-DEEP dee-DEEP sounds until Malla rushes to the console, and slides the panels aside. C-3PO sees Malla’s face, and turns to Leia saying, “Ah. I have made the connection. You may speak now if you wish.

SWHS-rebelcomms-10

They do, and when the conversation is over, the feed just shuts off, with neither party doing anything to make it happen.

So. Yeaaaaah.

Activation

How is it turned on? One possibility is an architectural switch activated by sliding the panels. It would be a good design decision, as it is an action that needs to be undertaken anyway to use it. But that doesn’t explain Luke’s use.

Connection

How does Malla’s device know to call Luke once it’s on? It could be that it’s a fixed connection, like an intercom, that only calls that one other device. But it’s a Rebel garage. That doesn’t make sense. Why would Malla need to only call there? And of course they receive a call from Leia, who isn’t in that same garage, so it’s not exactly fixed.

Security

The device contains incriminating evidence, i.e. the direct connection to the Rebel base, and so it needs some sort of security. Why is that not in evidence?

Secret agent?

One technological concept that would answer a lot of these questions is that of agentive technology, i.e. artificial narrow intelligence that does things on behalf of its users.

It could explain how the device turns on and (some of) the security: the camera has hairy face recognition and persistently watches for authorized users, turning on when it sees one of them. Conceptually that would be far beyond common sci-fi tropes of the time, but in keeping with the New Criticism stance of the blog, should be considered.

It could explain how it knew to call Luke: It understands Shyriiwook and listened to the conversation that Itchy and Malla had before they opened the panel, knew they wanted to call Luke, and found him in the garage.

It could explain how it turns off: It’s smart enough to understand the linguistic, social, and physical cues that the conversation has ended.

The world of Star Wars even has this technology in evidence. The droids all exhibit artificial general intelligence, and it is only a failure of imagination that this intelligence should not be incorporated into important devices, or spaceships, or architecture.

This would also explain why c-3PO is managing the interface on his end but nobody else has to bother: An AI does not need another AI, just an API.

It would even explain why the damned thing rings. Take a moment to appreciate that. This is an illegal device on the Empire-controlled Kazook. We know this because it’s deliberately hidden, and our protagonists really work to avoid the Empire’s finding it. Yet when an unexpected call comes in, it shrilly announces the fact of itself to everyone within screeching range. The only way this is not the most moronic feature possible of an illegal object is if it can scan the surroundings and verify that it’s OK to ring. Because otherwise, it would be the most stupid feature of a stupidly stupid technology made in haste for a stupid show slopped together in haste and without any respect for a logical or consistent diegesis.

Whew.

Thank The Maker for apologetics.

Starnav

STARNAV

To travel to Jupiter, navigator Zander must engage the Star Drive, a faster than light travel mechanism. Sadly, we only see the output screens and not his input mechanism.

Captain Deladier tells Ibanez, "Steady as she goes, Number 2. Prepare for warp."
She dutifully replies, "Yes m’am."
Deladier turns to Barcalow and tells him, "Number 1, design for Jupiter orbit."

In response, he turns to his interface. We hear some soft bleeping as he does something off screen, and then we see his display. It’s a plan view of the Solar system with orbits of the planets described with blue circles. A slow-blink yellow legend at the top reads DESIGNATING INTRASYSTEM ORBITAL, with a purple highlight ring around Earth. As he accesses "STARNAV" (below) the display zooms slowly in to frame just Jupiter and Earth.

StarshipT-STARNAV07

STARNAV

As the zoom starts, a small box in the lower right hand corner displays a still image of Mars with a label LOCAL PRESET. In the lower left hand corner text reads STARNAV-0031 / ATLAS, MARS. After a moment these disappear replaced with STARNAV-3490 / ATLAS, NEPTUNE, STARNAV-149.58 / ATLAS URANUS, STARNAV-498.48 / ATLAS, SATURN, and finally STARNAV-4910.43 / ATLAS JUPITER. The Jupiter information blinks furiously for a bit confirming a selection just as the zoom completes, and DESIGNATING INTRASYSTEM ORBIT is replaced with the simpler legend COURSE. Jupiter has a yellow/orange ring focus in on it as part of the confirmation.

Some things that may be obvious, but ought to be said:

  1. How about "Destination" instead of "Local preset"? The latter is an implementation model. The former matches the navigator’s goals.
  2. Serial options are a waste here. Why force him to move through each one, read it to see if that’s the right one, and then move on? Wouldn’t an eight-part selection menu be much, much faster?
  3. The serial presentation is made worse in that the list is in some arbitrary order. It’s not alphabetical: MNUSJ? It’s not distance-order either. He starts at 4, he jumps to 8, 7, and 6 before reaching 5, which is Jupiter. Better for most default navigation purposes would be distance order. Sure, that would have meant only one stop between Earth and Jupiter. If you really needed more stops for the time, start at Mercury.
  4. planets_iau (1)

  5. What are those numbers after "STARNAV-"? It’s not planet size, since Uranus and Neptune should be similar, as should Saturn and Jupiter. And it’s not distance, since Jupiter has the largest number but is not the fathest out. Of course it could be some arbitrary file number, but it’s really unclear why the navigator would need to know this when using the screen. If a number had to be there, perhaps a ranking like Sol-V Best would be to get rid of any information that didn’t help him with the microinteraction.
  6. How about showing the course when the system has determined the course?
  7. NUI would be better. When he looks at that first screen, he should be able to touch Jupiter or its orbit ring.
  8. Agentive would be best. For instance, if the system monitors the conversation on the bridge, when it heard "design for Jupiter," it could prepare that course, and let the navigator confirm it.

StarshipT-STARNAV08

Sneakily agentive?

Regular readers of my writing know that agentive tech is a favorite of mine, but in this case there is some clue that this is actually what happened. Note that the zoom to frame Earth and Jupiter happens at the same time as he’s selecting Jupiter. How did it know ahead of time that he wanted Jupiter? He hadn’t selected it yet. How did it know to go and frame these two planets? Should he select first and this zoom happen afterward? Did it actually listen to Deladier and start heading there anyway?

No.

It would be prescient if this throwaway interface was some secret agentive thing, but sadly, given that the rest of the interfaces in the film are ofttimes goofy, powered controls, it’s quite likely that the cause and effect were mashed together to save time.

STARNAV fuigetry

Though I can’t quite make sense of them (and they don’t change in the sequence), for the sake of completeness, I should list the tabs that fill the top and bottom of the screen, in case its meaning becomes clear later. Along the top they have green tab strokes, and read from left to right POS, ROLL, LINE, NOR, PIVOT, LAY. Tabs at the bottom have orange and purple strokes and read SCAN M, PLACE, ANALYZE, PREF, DIAG-1 on the first row. The second row reads SERIAL [fitting -Ed.], CHART, DECODE, OVER-M, and DIAG-2.