Pim
Listed as the speaker on the media.ccc.de HackerHotel Badge talk page; design-author attribution still needs deeper source recovery.
SourceHackerHotel 2025 · Netherlands · 2025
Badge-team workflow and challenge badge record
A HackerHotel 2025 badge record anchored by the public badge talk, preserving badge-team workflow, challenge integration, production handoff, and lessons learned rather than unsupported component-level details.
People
Listed as the speaker on the media.ccc.de HackerHotel Badge talk page; design-author attribution still needs deeper source recovery.
SourceThe record captures the human and operational side of Badge.Team-adjacent event badges: how a hotel-format hacker-event badge moves from concept and puzzles toward manufacturing, talks, and attendee play.
The current source pass does not provide a full public bill of materials or schematic. Hardware claims are therefore limited to a conservative Badge.Team-style electronic badge record pending official docs or repository recovery.
The public talk context supports challenge and badge-workflow coverage, but the page intentionally avoids naming specific launcher, firmware, or app-store details until durable sources are recovered.
HackerHotel badge talks are part of the event's own lore: the badge team explains what they built, what worked, and what hurt, turning badge production into a shared postmortem rather than a black box.
Lifecycle
The talk and schedule context preserve the badge as a HackerHotel challenge surface, even though component-level firmware and app-store records remain open.
SourceThe public HackerHotel Badge talk captures the badge-team process, challenge integration, and lessons learned as part of the badge's post-event record.
SourceOperational history
The image archive should stay empty for this badge until an original licensed photo can be attributed and processed.
The dossier preserves the public badge talk while avoiding unsupported component-level claims.