inside risks: a few old coincidences  computer puns considered harmful: presented here are two old examples of harmful input sequences that might be called computer puns. each has a double meaning, depending upon context.  xerox parc's pioneering wysi-wyg editor bravo [1] had a lurking danger. in edit mode, bravo interpreted the sequence edit as "everything deleted insert t," which did exactly that--- transformed a large file into the letter 't' without blinking. after the first two characters, it was still possible to undo the 'ed,' but once the 'i' was typed the only remaining fallback was to replay the recorded keystroke log from the beginning of the editing session (except for 'edit') against the still-unaltered original file.  a similar example was reported by norman cohen of softech: he had been entering text using the university of maryland line editor on the univac 1100 for an hour or two, when he entered two lines that resulted in the entire file being wiped out. the first line contained exactly 80 characters (demarcated by a final carriage return); the second line began with the word "about." cohen said: "because the first line was exactly 80 characters long, the terminal handler inserted its own cr just before mine, but i started typing the second line before the generated cr reached the terminal. when i finished entering the second line, a series of queued output lines poured out of the terminal.  it seems that, having received the cr generated by the terminal handler, the editor interpreted my cr as a request to return from input mode to edit mode. in edit mode, the editor processed the second line by interpreting the first three letters as an abbreviation for abort and refused to be bothered by the rest of the line. had the editing session been interrupted by a system crash, an autosave feature would have saved all but the last 0-20 lines i had entered. however, the editor treated the abort request as a deliberate action on my part, and nothing was saved.  two wrongs make a right (sometimes):a somewhat obscure wiring fault remained undetected for many years in the harvard mark i. each decimal memory register consisted of 23 ten-position stepping switches (plus a sign switch). registers were used dually as memory locations and as adders. the wires into (and out of) the least significant two digits of the last register were crossed, so that the least significant position was actually the second-to-least position and vice versa with respect to memory. no problems arose for many years during which that register was used fortuitously only for memory in the computation of tables of bessel functions of the nth kind; the read-in error corrected itself on read-out. the problem finally manifested itself on the n + 1st tables when that register was used as an adder and a carry went in the wrong direction. this was detected only because it was standard practice in those days to difference the resulting tables by hand (using very old adding machines).  things have changed and we have learned a lot; however, similar problems continue to arise, often in new guises.  discussion:today's systems have comparable dangers lurking, with even more global effects. in user interfaces, we have all experienced a slight error in a command having devastating consequences. in software, commands typed in one window or in one directory may have radically different effects in other contexts. programs are often not written carefully enough to be independent of environmental irregularities and less-than-perfect users. search paths provide all sorts of opportunities for similar computer puns (including triggering of trojan horses). accidental deletion is still quite common, although we now have undelete operations. in hardware, various flaws in chip designs have persisted into delivery.  many of you will have similar tales to tell. please contribute them.  conclusions:  designers of human interfaces should spend much more time anticipating human foibles.  crosschecking and backups are ancient techniques, but still essential.  computers do not generally appreciate puns.  peter g. neumann