Before the familiar hacker story
Technical communities developed their own languages and ways of learning. No single club, medium, or invention accounts for everything that followed.
Independent research index / First release
Follow the practices.
Overlapping communities and tools, not one inevitable chain of progress.
Connections are labeled as documented artifacts, shared tools, or editorial comparisons. Temporal sequence alone does not establish influence.
Turing & Bell Labs Explore contributors
Phone phreaking: learning the network
Telephone experimentation is a central thread here, with earlier engineering and later computing connections kept in view.
Radio, packets, and practical electronics
Radio experimentation joins signals, protocols, hardware, and communities. The documented bridges are more useful than a tidy origin myth.
BBSs, modems, and text culture
Text files traveled with communities. Their titles, author credits, dates, and surviving copies help reconstruct that movement.
Discarded documentation and material reuse
A manual, discarded object, and public technical journal can all teach a system—but they have different origins and access conditions.
Wardriving and wireless discovery
Wireless surveying creates observations of infrastructure. A historical account should distinguish discovery from unauthorized access.
Hardware, from the board to the chip
Follow a concrete artifact through its components, documentation, and behavior. This is a learning path, not a single historical chronology.
Optional historical context
Public institutions and hacker communities · Reports, secrecy, and evidence · Annie Jacobsen bibliography