Start with the takeaway in each heading. The claim being examined is labeled separately and is not this archive’s endorsement. Some entries concern historical facts; others examine ideals, ethics or membership rules that evidence alone cannot settle. The sources show particular voices and traditions, not one universal definition of a hacker or phreak. Hacker and phreak myths Who gets to call themselves a hacker or a phreak—and who gets to decide? Here, myth means a story that explains identity, status or belonging. It does not automatically mean a false statement. Some claims are useful aspirations; others become stereotypes, excuses or tests of loyalty. The belief headings are editorial formulations, not quotations or measured prevalence claims. Sources establish particular voices and traditions; the analysis is our interpretation, not a universal membership test. Understanding matters; tool choices alone do not prove it. Claim being examined: A real hacker understands the system, not just the tool. Editorial standard, not a universal membership rule What the evidence supports: Competence matters: explaining a result, testing its limits and noticing failure are different from merely repeating a command. But tool use alone cannot tell us how much someone understands. A novice can learn through tools; an expert can depend on other people’s work. The useful standard is demonstrable understanding. The gatekeeping move is to substitute a preferred editor, language or workflow for evidence of it. Discuss: What explanation or experiment would demonstrate understanding here? Read alongside (relevant positions, not endorsement of the heading): https://tmrc.mit.edu/old/hackers-ref.html Hacker identity is not evidence of an inborn trait. Claim being examined: A real hacker is born different, rather than taught. Unsupported identity inference What the evidence supports: A story of the misunderstood outsider can express real frustration and help readers find belonging. It does not establish an innate category of person. Turning that story into an entrance requirement makes teaching, ordinary practice and asking for help seem less authentic. Read the manifesto as a voice with a situation and an audience. Do not use it as a personality test or diagnose strangers from it. Discuss: What work disappears when the story centers exceptional talent? Read alongside (relevant positions, not endorsement of the heading): https://phrack.org/issues/7/hackers-manifesto A break-in is not a test of authentic hacker identity. Claim being examined: You have to break into something to prove you are real. Contested membership rule What the evidence supports: Capability, authorization, harm and reputation are separate questions. Neither a breach nor a conviction measures the whole range of technical creativity. Conversely, defining a favored identity as harmless does not establish that every person using the label acted harmlessly. Ask what happened and who was affected before using identity labels to praise, excuse or condemn it. Discuss: Would the same technical insight count if demonstrated in an authorized setting? Read alongside (relevant positions, not endorsement of the heading): https://tmrc.mit.edu/old/hackers-ref.html https://stallman.org/articles/on-hacking.html Curiosity does not erase harm or responsibility. Claim being examined: Curiosity makes every intrusion morally innocent. Ethical judgment, not a factual definition What the evidence supports: Curiosity can explain a motive without settling the effects of an action. Someone else may bear the privacy loss, disruption or cost. A compelling first-person story can leave those people outside its frame. The editorial distinction is motive versus consequence. Neither should be erased by a sympathetic or hostile portrait. Discuss: Whose perspective is absent from the account? Read alongside (relevant positions, not endorsement of the heading): https://phrack.org/issues/7/hackers-manifesto Sharing knowledge and protecting privacy can coexist. Claim being examined: A real hacker believes all information must be public. Ethical tension; traditions disagree on boundaries What the evidence supports: Openness can mean access to knowledge, accountability or reusable work. Publishing private personal information is a different act. Treating every secrecy boundary as the same hides the competing interests being discussed. The CCC’s privacy principle makes the tension visible within this tradition itself. A slogan needs a subject, an audience and limits before it can guide a decision. Discuss: Public information about whom, and private information belonging to whom? Read alongside (relevant positions, not endorsement of the heading): https://www.ccc.de/en/hackerethik Respect for skill does not remove barriers to participation. Claim being examined: Skill is all that matters; status and background do not. Ideal versus evidence of inclusion What the evidence supports: Judging work instead of pedigree can open a door. An examination of actual inclusion must also ask who gets equipment, time, mentoring, recognition and a chance to demonstrate work. A stated ideal is evidence of a norm, not proof that a community consistently achieved it. This is an analytical test of the ideal, not a demographic claim about every hacker group. Discuss: Who can participate in the supposedly neutral test? Read alongside (relevant positions, not endorsement of the heading): https://www.ccc.de/en/hackerethik A legendary device does not define a real phreak. Claim being examined: A real phreak must master a legendary box or tone. Artifact-based membership rule What the evidence supports: A famous device can preserve a period’s engineering and become a badge of belonging. Possessing it does not establish broad knowledge; lacking it does not settle someone’s interest in telephone systems. Historical equipment also belongs to particular networks and periods. Separate an artifact’s role in a documented episode from a timeless membership rule. This section provides history, not instructions for service theft. Discuss: Are we measuring knowledge, access to an artifact, or nostalgia? Read alongside (relevant positions, not endorsement of the heading): https://www.historyofphonephreaking.org/faq.php Phreaking included exploration and community, beyond free calls. Claim being examined: Myth: phreaking was only about free calls. Historical reduction contradicted by the cited accounts What the evidence supports: Phreaking was not just about free calls. It included exploring telephone switching and signaling, listening to understand call routing, mapping network behavior, studying technical documents, experimenting with tones and hardware, and sharing knowledge through conversations and newsletters. These activities supported curiosity, technical craft and community as well as, in some episodes, obtaining unpaid service. Lapsley’s history and Rosenbaum’s reporting also describe fraud, intrusion and harm. Neither reducing phreaking to toll avoidance nor portraying every participant as an innocent explorer captures that varied history. Use episode-specific evidence. Neither a celebratory label nor a criminal label supplies an individual’s motive by itself. Discuss: What does the source actually show about this participant’s goal? Read alongside (relevant positions, not endorsement of the heading): https://explodingthephone.com/hoppdocs/rosenbaum1971.pdf https://www.historyofphonephreaking.org/faq.php Individual discoveries also depend on shared knowledge. Claim being examined: A real hacker does everything alone and from scratch. Historical interpretation of collaboration What the evidence supports: Rosenbaum’s 1971 reporting describes phreak conference-line companionship and exchanged knowledge. Our interpretation is that social infrastructure belongs in the history alongside devices. An individual breakthrough can be worth crediting without making manuals, collaborators, hardware makers, maintainers and earlier publications disappear. Independence is not the absence of dependencies. This is an editorial question to ask of any hero story. Credit a particular contribution while tracing the infrastructure and people it relied on. Discuss: Which named contributions and uncredited dependencies made this result possible? Read alongside (relevant positions, not endorsement of the heading): https://explodingthephone.com/hoppdocs/rosenbaum1971.pdf No single politics, appearance or toolset defines every hacker. Claim being examined: A real hacker must share one politics, appearance or toolset. Universal membership rule not established What the evidence supports: A community may have explicit values and participation rules. That does not turn every preference into a universal technical qualification. Agreement, competence, conduct and identity are distinct dimensions; a single label cannot answer for all four. Distinguish a specific group’s expectations from a claim about everyone who uses the word. Discuss: Is this a declared community rule, a preference, or a claim about ability? Read alongside (relevant positions, not endorsement of the heading): https://www.ccc.de/en/hackerethik Peer recognition can help assess work; it is not a universal license. Claim being examined: You only count when established insiders say so. Editorial judgment about authority What the evidence supports: Peer evaluation can expose weak claims and recognize difficult work. It can also make existing networks the only route to recognition. The question is what the evaluator can demonstrate and whether the criteria can be challenged. A community’s self-definition is evidence about its boundaries. This archive does not appoint that community—or itself—as a licensing authority for identity. Discuss: Can an outsider meet the stated standard without first becoming an insider? Read alongside (relevant positions, not endorsement of the heading): https://tmrc.mit.edu/old/hackers-ref.html Hacker and phreak ethics vary across communities and time. Claim being examined: There is one timeless hacker or phreak ethic. Historical diversity of stated positions What the evidence supports: A single creed makes a complicated history easier to tell. It can also collapse disagreement, changing technologies and different settings. A manifesto, club statement and historical account answer different questions. Samson’s 2005 annotation of the 1959 dictionary describes an originally morally uncommitted usage; TMRC’s later statement draws a constructive boundary. Neither should silently replace the other. Compare named positions and dated revisions. This section discusses their tensions without replacing them with a new “real hacker” checklist. Discuss: Which source, place, period and participants does this claim actually describe? Read alongside (relevant positions, not endorsement of the heading): https://www.gricer.com/tmrc/dictionary1959.html https://tmrc.mit.edu/old/hackers-ref.html https://www.ccc.de/en/hackerethik https://phrack.org/issues/7/hackers-manifesto Cultural interpretation: The network answered back The personification and descriptions of beauty below are our interpretation, not historical quotations. The named experiences are attributed to their sources. Pick up the receiver and something was already there: a hum, an invitation from beyond the room. Behind the dial tone lay clicks, pauses, recordings and signals. In this telling, the network feels alive. A distant exchange has a voice; a busy signal is a door that will not open. These are metaphors for a responsive machine, not claims of consciousness. Lapsley’s history describes people listening to telephone sounds to understand how calls traveled, studying documents, building devices and finding one another through the network. Sometimes the beauty lived in the imperfections: a little hiss, an uneven rhythm, an echo that made distance perceptible. A clean connection could disappear into its purpose; an imperfect one invited you to notice the apparatus. Not every noise was a clue, and not every fault was welcome. But listening could turn an inconvenience into texture, or a puzzling sound into a question worth following. Blind young people were important explorers, not magical exceptions. Touch and sound made telephone interaction accessible without sight; that helps explain its possibilities, not every person’s motives. Radiolab’s account describes Joe Engressia, later known as Joybubbles, as having perfect pitch and discovering in childhood that his whistle could interrupt a connection. He tried the effect again. We omit an exact age and call type because retellings differ. The discovery was not simply a special talent: an unexpected response became something to investigate. It does not establish that all blind people had exceptional hearing or that blind children made every tone discovery. Imagine the change in scale: a child makes a sound in one room and equipment somewhere else responds. A system that seemed sealed has an edge within reach. Its apparent limits become questions. This is the romance of accomplishing the impossible: finding that what looked impossible was an assumption, then patiently learning what the machine could actually do. Ma Bell could inspire affection as well as opposition. Rosenbaum’s 1971 reporting describes Engressia’s wish to work for the telephone company and his appreciation of its system; another participant expresses love and resentment together. Admiration for the machinery was not necessarily approval of its owner. Radiolab includes a recording in which Engressia remembers taking comfort in the steady dial tone during frightening childhood nights. For him, the machine could be company. That personal account should not be made into a universal story about blindness or childhood. Discovery also became fellowship. Rosenbaum describes improvised conferences and technical knowledge circulating in Braille. Evan Doorbell’s recording catalog names exchanges, routes and conferences, preserving a geography of equipment and people; we reviewed the catalog, not every recording. The attraction could be knowing a machine closely enough to notice its habits, and meeting someone else who wanted to listen. Free calls were part of some episodes. They do not exhaust the curiosity, craft or affection, just as affection does not erase the documented intrusion and harm. Phil Lapsley: History of Phone Phreaking FAQ https://www.historyofphonephreaking.org/faq.php FAQ reviewed Radiolab: Long Distance (2012), transcript and attributed archival recollections https://radiolab.org/podcast/187724-long-distance/transcript Relevant transcript passages reviewed; not independent verification of every recollection Ron Rosenbaum: Secrets of the Little Blue Box (1971) https://explodingthephone.com/hoppdocs/rosenbaum1971.pdf Relevant reporting reviewed; theatrical passages and broad origin claims not adopted Evan Doorbell: Group 1 recording catalog https://evan-doorbell.com/group-1-playlist/ Catalog reviewed; recordings not audited SOURCE POSITIONS Peter Samson: TMRC Dictionary, June 1959 / annotations September 2005 Contemporary dictionary with later participant annotations https://www.gricer.com/tmrc/dictionary1959.html Samson dates the dictionary to June 1959 and separates his September 2005 commentary. His retrospective note says the original usage implied neither benevolence nor maliciousness. Compare that account with TMRC’s later constructive boundary: definitions changed and their dates matter. Ron Rosenbaum: Secrets of the Little Blue Box, October 1971 Contemporary reporting, hosted by a historian https://explodingthephone.com/hoppdocs/rosenbaum1971.pdf Rosenbaum describes technical fascination, shared knowledge, handles, conference-line companionship and blind participants, alongside fraud and impersonation. It is evidence about reported participants and episodes, not a census of phreaking. The linked historical article includes material this archive does not reproduce. TMRC: Hackers Community self-definition https://tmrc.mit.edu/old/hackers-ref.html TMRC defines hacking around ingenious, clever results and explicitly contests the criminal meaning. Its claim to the original meaning is part of the historical argument, not an impartial ruling over every community. CCC: Hacker Ethics Institutional ethical statement https://www.ccc.de/en/hackerethik The CCC presents access, learning, decentralization and judging conduct over credentials alongside privacy and non-damage principles. It describes these ethics as evolving guidelines for discussion, not a completed universal code. Richard Stallman: On Hacking Participant interpretation https://stallman.org/articles/on-hacking.html Stallman emphasizes playful ingenuity, including activities outside computing. He disputes equating hacking with security breaking and acknowledges that impressive cleverness can still raise ethical problems. The Mentor: The Conscience of a Hacker Dated first-person manifesto https://phrack.org/issues/7/hackers-manifesto The text identifies its author as The Mentor and its writing date as January 8, 1986. Published in Phrack 7 in September 1986, it frames curiosity, institutional alienation and belonging through a defiant first-person voice and explicitly justifies unpaid service use. It should not be recast as a modern authorized-security pledge. It is not a survey of hackers or proof that every reader shared its values. Phil Lapsley: History of Phone Phreaking FAQ Historian’s synthesis https://www.historyofphonephreaking.org/faq.php Lapsley distinguishes enthusiasm for understanding telephone networks from the later service-theft meaning. His account includes study, devices, conversation and newsletters, as well as abuse and consequences. It supplies a historical framing, not a universal membership test.