“I never wanted to simply use technology. I wanted to understand what was happening inside it.”

GRAPHIC: Crystal Set icon PHOTO: childhood / early electronics, if any survive

Long before there was a blue box, there was a kid with a screwdriver and no patience for being told how something worked. I took apart radios. I built crystal sets — no battery, no amplifier, just a coil, a crystal detector, and a single earpiece, pulling a signal straight out of the air. That was the first time I understood, physically, that information was just riding on a wave, waiting for someone curious enough to go find it.

By the early 1960s, while I was still in high school, that same restlessness had turned into a ham radio license and my own call sign: WB6EWU.

PHOTO: young John, ham radio gear — callsign WB6EWU

GRAPHIC: Service Roundel icon — generic, not the official DoD seal PHOTO: military service photo, if available

The Air Force is where "take apart radios in your bedroom" turned into "work on radar and communications systems at a scale most people never see." It's where curiosity about signals stopped being a hobby and started being training — and where I got comfortable with the idea that big, complicated electronic systems are still just systems. They can be learned.

I joined by choice, not by the draft. It was the height of the Vietnam era, and just about everyone my age was headed into the Army whether they wanted to be or not. I went to my recruiter and asked for the Air Force instead, and told him exactly what I wanted: electronics, radio communications, radar — anything that put me inside the equipment instead of just carrying it.

Basic training turned out to be its own kind of test. I made it through on the shape I'd kept myself in through high school, but basic is also where I found out I had a degenerative spine condition, painful enough that standing for more than half an hour was rough. I wiggled my way through anyway.

When it came time to fill out my "dream sheet" — the wish list that was supposed to help steer where the Air Force sent you next — I put down the half year of college I'd already done toward an electronics engineering degree. I even tried for Officer Candidate School as a pilot, but my eyesight wasn't good enough, so that door shut fast. I went in enlisted instead, trained in electronics at Keesler Air Force Base, and spent my final two and a half years actually on the job.

PHOTO: USAF service — Keesler Air Force Base training

That job ended with orders to Alaska, which, as far as I was concerned, was about the worst assignment the Air Force could have handed me. If someone had told me Vietnam would have been the easier posting, I'd have believed them.

PHOTO: Alaska duty station, if any photos survive

From there it was on to Maine — one of the coldest states in the continental U.S., and not much of an improvement over Alaska. I spent the first half of that assignment working radar systems, then got reassigned to GATR (Ground Air Transmitter Receiver): routine testing and maintenance on a large bay of radios that served as ground stations, keeping airborne pilots and ground operations in contact. That's where my four years in the Air Force came to a close.

PHOTO: GATR site / Maine assignment, if any survive

GRAPHIC: Tone on the Line icon PHOTO: the actual Cap'n Crunch whistle VIDEO: if a demonstration clip exists — whistle to tone

After the Air Force, the telephone network became the next enormous machine to figure out. It was — and still is — one of the largest engineered systems humans have ever built, and almost nobody who used it every day understood what was actually happening underneath.

Here's the part everyone already knows: a toy whistle, free in boxes of Cap'n Crunch cereal, happened to produce a tone at exactly 2600 Hz. That frequency wasn't random — it was the tone AT&T's long-distance network used internally to signal that a trunk line was free and ready for a new call. Blow the whistle into the right part of a call, and you could talk to the switching equipment directly, the same way an engineer would.

Once I realized how central those tones were to the switching equipment, I started noticing how extensively the phone company relied on them — and the most interesting discovery was how many of them were still running on very old switching equipment. That became something of an obsession: studying the older systems, and how they'd been adapted to use standard multi-frequency tones.

That obsession is what got me out on the road. I'd take phone trips to track down old phone systems, dialing in and just listening — the clicks, beeps, and chirps of a call actually being set up, one piece of switching equipment talking to the next. My home base at the time was Mountain View, and from there I'd head out to small, remote towns in the Central Valley, places near Stockton and similar spots.

One of the most interesting exchanges I found was in Blaine, Washington. I'd dial 9-1, wait for a mechanical "chunk," then use the Cap'n Crunch whistle to pulse out 2-1, wait for another chunk, and outpulse the rest of the number from there. Blaine was just one of many exchanges worth the trip.

PHOTO: phone-trip material — notes, old exchange photos, if any survive

Almost every pay phone back then had a number where the last four digits started with a 9 — that was intentional, so operators were trained to refuse a collect call to any number matching that pattern. In Death Valley, though, I found a payphone where substituting a 3 for that leading 9 still rang through to the exact same number, but the operator had no way of knowing it was a payphone. So it wasn't just the whistle — it was understanding how the exchange number and those last four digits actually worked that made things like that possible.

Here's the part that matters more: none of it — not the whistle, not Blaine, not the Death Valley trick — was really the discovery. Anyone can learn a trick. The real discovery was realizing that a nationwide phone network — something that felt as fixed and untouchable as the weather — was actually just a system with rules, and that if you learned the rules, you could have a conversation with the machine instead of just using it.

That distinction is the whole reason this chapter is worth telling at all.

GRAPHIC: Box & Coupler icon PHOTO: an actual blue box, cord, and acoustic coupler VIDEO: blue box demonstration, if one exists

I wasn't the only one who'd figured out the phone system had a back door. There was already a small, scattered community of technically curious people — phone phreaks — trading what they'd learned about tones, trunk lines, and switching equipment, mostly by word of mouth. It was early hacking culture before anyone called it that.

The blue box was the tool that grew out of that community: a small electronic device that could generate 2600 Hz and the full set of in-band signaling tones on demand, no whistle required. You'd dial a number, play a tone through an acoustic coupler pressed against the handset, and the network would respond exactly the way it would to its own switching equipment — because as far as the system could tell, that's exactly what it was talking to.

According to a number of attorneys I've talked to over the years, technically, sending blue box tones into the phone line isn't illegal by itself. What crosses the line is intent — using a blue box with the intention of actually placing a call and talking to someone on the other end. It comes down to how it's interpreted. My own intention was usually to reach certain operators inside the phone company and talk with them directly, which isn't illegal in itself — but the only way to reach them was by coming in on certain lines and trunks that were normally off-limits to ordinary subscribers.

GRAPHIC: Garage & Chip icon

Some of that couldn't have happened without what was already brewing nearby. In Menlo Park, a small outfit called the People's Computer Company — started in 1972 by Bob Albrecht — was built on the radical idea that ordinary people, and especially kids, should get hands-on access to computers. School groups would come through on field trips, and every Wednesday night PCC hosted a potluck dinner; a lot of the first ideas for building your own computer got talked through at those tables.

The hardware caught up fast. Intel released the 8080 chip in April 1974 — the first true computer on a chip — priced at $360 apiece, more than most hobbyists could justify. Ed Roberts of MITS couldn't have built an affordable machine at that price, but by committing to buy about a thousand of them, he got Intel down to roughly $75 a chip. That's what made the Altair 8800 kit possible at under $400 — around $2,400 in today's money. The following September, MOS Technology went even further, introducing its 6502 processor at WESCON in San Francisco (September 16–19, 1975) for just $25 a chip.

The Altair 8800 made the cover of Popular Electronics in January 1975, and less than three months later — on March 5, 1975 — the Homebrew Computer Club held its very first meeting: about 32 people packed into Gordon French's garage in Menlo Park, growing directly out of that same scene. That's arguably the moment home computers went from hobbyist dream to mainstream reality — so if you're a computer historian, mark that date. It's also the meeting Steve Wozniak attended, after I told him about a club he'd never even heard of. By then, though, he and I already went back a couple of years.

That story starts with a radio interview. In October 1971, Esquire ran Ron Rosenbaum's article “Secrets of the Little Blue Box,” still readable here. A couple of years later, in 1973, KPFA invited me on the air to talk about it, and on live radio I demonstrated exactly what a blue box could do — hopping from trunk to trunk through switching equipment in cities all over the world, and finally ringing a phone sitting right next to me in the studio.

A young Steve Wozniak happened to be listening. Around the same time, Steve Jobs had a copy of that Esquire article sitting on his coffee table — Woz called him up and told him to tune in, though Jobs, at first, assumed the whole thing had to be fiction.

Wozniak contacted the radio station, the station called me, and I ended up with Steve's phone number at his dorm at UC Berkeley. That dorm-room phone call has been told and retold since; there's even a documentary about it, The Secret History of Hacking.

LINK: YouTube — recent Zoom reunion with Steve Wozniak and others from the original Homebrew crowd

We've been close friends ever since. I remember visiting Steve at his house once and finding he'd taken in a couple of white mice as pets — he was allergic to them the whole time, but kept them anyway because of the way they wiggled their noses.

Steve ended up building his own blue box, too, though his was a digital design. The catch was that its output was a square wave, while the phone network ran on sine waves — a mismatch that, indirectly, may have led to my arrest.

One of the closer calls came early on. Steve was driving from Cupertino up to Berkeley when his car broke down, and he pulled into a gas station to try the box out. Back then you couldn't dial an 800 number directly from a payphone, so he asked an operator to place the call — and I hadn't briefed him on the social engineering that goes with an operator-assisted 800 call, where she checks back in partway through to ask if you're done. Steve was right in the middle of that exchange when a police car happened to pull into the station.

The officer wasn't there for Steve — he was just checking the lot for anything that looked out of place — but Steve was the only one around, so he walked over. Steve, thoroughly paranoid by then, slipped the box behind his back and passed it to Jobs. The cop noticed anyway and asked what it was, right as Steve was still pressing buttons. “It's a music synthesizer,” Steve told him. “It's a little out of tune,” the cop said. “It's not calibrated yet,” Steve answered, and the cop handed it back. “A guy by the name of Moog beat you to it,” the cop said — Moog being the company known for its music synthesizers.

Whew. That was a close one. The police hadn't been briefed yet on what a blue box even was, let alone what one looked like. Obviously, that's changed since.

I didn't build Apple. But I was part of the world that helped produce the people who did, and that's a thread worth pulling on.

GRAPHIC: not yet designed PHOTO: not yet gathered

Steve sold his boxes for $150 apiece, and tucked a note inside each one: “He's got the whole world in his hands.” One of my phone-phreak acquaintances, a guy named Richard, bought one. Trying to fit a square wave into a network built for sine waves was like fitting a square peg into a round hole — most of the calls it attempted got rejected, and every rejection printed out a trouble card, the kind phone company technicians used to flag a problem line. Eventually the phone company traced one of those cards back to Richard. Despite everything I'd told him about never writing my number down anywhere, he apparently had — and that became the first documented link between the “Captain Crunch” of the Esquire article and me. That's what started the FBI's investigation.

The full story of that investigation is told in far more detail in Phil Lapsley's book, Exploding the Phone, first published by Grove Press in February 2013.

Eventually, I built my own blue box — one that outpulses digits at the exact rate the phone company's switching equipment expected. The tones it produced were also far more accurate, accurate enough that I could send a full sequence in a little over a second.

That let me do some social engineering of my own. On payphone calls, I'd convince the operator she was listening to a data call rather than a person dialing. When I dropped 2600 Hz onto the line to seize the trunk, the network would register a momentary on-hook and off-hook — and a distracted operator would just assume the call was over. Sometimes I'd send KP-017-ST, a sequence that routed to a telex number, and tell the operator to ignore the “false supervision” she was seeing on her end. Every so often one would ask how I knew that, and I'd just tell her it happens a lot. It was convincing enough, most of the time.

Eventually, though, it caught up with me. On my way home from class one day, the FBI picked me up and arrested me. It came after a long investigation, with grand jury subpoenas going out to people in my circle — Richard among them — to testify. I was released on my own recognizance and given a public defender's number. In the end, that first case cost me five years of probation and a $5,000 fine.

This is as far as the chapter goes for now — John is planning to write the rest himself: what came later, and his time at Lompoc Federal Prison.

GRAPHIC: Terminal & Floppy icon PHOTO: EasyWriter-era screenshots, packaging, or press material, if they survive

Somewhere in there, I stopped only exploring technology and started building it. EasyWriter was one of the first word processors available for personal computers — real, shipped software that people used to actually get work done, at a moment when "personal computer" itself was still a new and slightly ridiculous idea to most people.

That's the point of this chapter: the same person who spent years figuring out how to talk to a phone network by ear turned around and wrote software real people relied on. Exploring and building were never two different phases of my life. They were always the same instinct pointed in different directions.

GRAPHIC: Signal Globe icon PHOTO: conference and travel photos VIDEO: conference talks, interviews, if available

The small, scattered phone-phreak community didn't stay small. It grew into something much bigger — a hacker culture with its own conferences, its own gatherings, its own arguments about ethics and curiosity and where the line should be. I've spent a lot of years on planes and in conference halls because of it: interviews, talks, hacker gatherings on more continents than I expected to see when I was a kid with a soldering iron.