WHYcast history episode 10

Episode 10 – Fiber-Dragging Dogs and Metal Detectors: Tales from What the Hack 2005

In this milestone tenth episode of WHYcast, the hosts celebrate both their own decennial podcast journey and the tenth iteration of Dutch hacker camps, with WHY2025 approaching as the latest in a storied tradition. The heart of the episode is the historical segment, where Walter—a veteran of the scene—returns to recount a trove of vivid anecdotes from What the Hack 2005, an event remembered for its ingenuity, camaraderie, and sometimes soggy circumstances.

The Setting: Liempde and the Spirit of Volunteerism

What the Hack 2005 took place in Liempde, a small town in the Dutch province of Brabant. Walter reminisces about the pleasure of not only attending but also participating in the physical preparation—“the build-up”—where putting up tents and working shoulder-to-shoulder with kindred spirits was as rewarding as the event itself. This hands-on, communal ethos is a recurring tradition at Dutch hacker camps, reinforcing their reputation as gatherings by and for the community.

Blue Hair and Network Tributes

A charming tradition marked this event: Walter dyed his hair blue in tribute to Aldert Hasenberg, a fellow network team member who had sported the same color at the previous camp. This tongue-in-cheek homage encapsulates the playful culture of hacker camps, where visual quirks and inside jokes become emblems of team identity and continuity. It’s a simple, human detail that threads together generations of volunteers and reminds us that culture at these camps is as much about personality as it is about technology.

The Great Fiber Pull: Dogs, Ditches, and Dutch Railways

Network connectivity—always a logistical feat at large field events—was at the center of one of the most memorable stories. For What the Hack 2005, the organizers secured a sponsor who could provide fiber-optic connectivity to the field, but the infrastructure needed to cross multiple farmers’ fields. While local farmers were accommodating, the Dutch Railway was less so, refusing permission to lay cable across their tracks.

Here, the legendary hacker spirit of improvisation shone: someone apparently brought a small dog, and the team leveraged existing drainage pipes beneath the railway. The dog was sent through the pipe, trailing a string, which was then used to pull the fiber cable through to the other side. This anecdote—whether firsthand or passed down—epitomizes the pragmatic creativity and willingness to “hack” any problem, blending technical necessity with a touch of folklore.

Disaster Strikes: Severed Fiber and Farmer Follies

No good hack goes unpunished, and the story soon took a turn: on the eve of the event, the entire network went down. The organizers split into search parties to walk the length of the cable, only to discover two calamities: in one spot, a farmer had tied the cable in a knot around a pole, oblivious to fiber’s fragility; elsewhere, a grass mower had sliced straight through the cable near the railway. The team scrambled to find the right splicing equipment, and miraculously, everything was restored in time for the event’s opening. The tale underscores the precariousness and resourcefulness that have so often defined Dutch hacker camp infrastructure.

Coexistence and Cultural Contrasts: Sharing the Field

Walter recalls that What the Hack immediately preceded a large event organized by the Evangelical Broadcasting Corporation—a Christian youth gathering. The two groups negotiated over logistics, particularly what to do with the freshly-installed fiber and event fencing. The religious organizers declined both, expressing disbelief that fences or network cables would be necessary, since “people don’t touch each other’s stuff normally.” The contrast in expectations and needs between the two communities—one rooted in openness and trust, the other in more conventional event management—offered a quiet commentary on the unique ethos of hacker camps, where theft is rare and trust is high.

Security, the DIY Way: Metal Detectors and Self-Policing

One whimsical innovation at What the Hack was the deployment of a metal detector at the entrance as a tongue-in-cheek security check. Attendees passed through the device, not for real screening but as a playful nod to airport security. For Walter, it became an unexpected educational moment: he realized that metal detectors respond to changes in magnetic fields, not to the mere presence of metal. If you move slowly, you’re less likely to trigger an alarm—a fact that suddenly made sense of airport staff urging travelers to “move quickly.” This do-it-yourself approach to security, where the process is as much about learning and fun as protection, is emblematic of the hacker camp philosophy—volunteer-driven, participatory, and irreverently practical.

The Dataklo and Pinball Machines: Shelter from the Storm

That year, the infamous Dutch weather made its presence felt. The organizers’ field, lacking proper drainage, turned into a swamp after heavy rains. Walter recalls waking up to a tent so sodden that he risked electrical shock from his gear. Fortuitously, he lived nearby and could sleep at home, but others had to cope with the mud and wet. The Dataklo—a German-inspired data restroom tent—was present, providing dry shelter for equipment. Meanwhile, a tent filled with mechanical pinball machines (including one brought from a host’s own home) served as a retro gaming lounge, a testament to the eclectic amusements that dot these events.

Community, Trust, and Tradition

Walter emphasizes that despite the lack of fences and minimal policing, almost nothing was stolen—a laptop, perhaps, but little else. This trustworthiness is a hallmark of the Dutch hacker camp tradition and a point of pride across decades of gatherings. The ethos of openness, mutual respect, and volunteer stewardship continues to define these camps and sets them apart from mainstream festivals.

Personal Connections and Serendipity

Adding a personal note, one host shares that What the Hack was where she met both a student and her future husband. The camp thus becomes more than the sum of its technical and organizational feats—it’s a crucible for lasting friendships, professional collaborations, and, sometimes, even love.

Other Historical Mentions and Notes

• The episode reiterates the lineage of Dutch hacker camps: starting with the Galactic Hacker Party (1989), Hackers at the End of the Universe (1993), Hacking in Progress (1997), Hackers at Large (2001), What the Hack (2005), Hacking at Random (2009), Observe Hack Make (2013), Still Hacking Anyway (2017), and May Contain Hackers (2022, after a COVID delay).
• A brief discussion touches on the possible first use of the Dataklo at What the Hack 2005, inspired by similar facilities at German hacker camps, though the exact timeline remains uncertain.
• The tradition of bringing personal or unusual equipment (such as pinball machines) to the camp, and the DIY spirit in all aspects, from network infrastructure to event security, are repeatedly highlighted.

Community Story: Open Source Bach at SHA 2017

A secondary historical story, recounted by Jos from Team Content, comes from SHA 2017. Jos tells of how they invited Kimiko Ishizaka, a classical pianist who led a Kickstarter to record and release Bach’s music into the public domain (“open source Bach”). This required not only inviting her to give a talk, but also figuring out how to host a classical piano concert—outdoors, in a tent, at a hacker camp. The audio and stage teams had to rise to the occasion, sourcing and tuning a grand piano, upgrading sound equipment, and navigating the logistics of field conditions. The result was a unique hacker camp experience, blending high culture with technical improvisation—a perfect example of “stupid and awesome” ideas that define the creativity and audacity of these events.

Historical Section Note

This episode is rich with detailed recollections from What the Hack 2005, and includes a brief but illustrative anecdote from SHA 2017. If any episode lacks a historical section in the future, that will be noted explicitly.