Nora
Listed in the GPN23 orga table for the Badges area.
SourceGulaschprogrammiernacht 23 · Germany · 2025
Printed attendee badge, lanyard, and safeR badge workflow
A source-backed non-electronic GPN23 badge record for the printed attendee badges and lanyard workflow documented by Entropia's FAQ and badge how-to.
People
Listed in the GPN23 orga table for the Badges area.
SourceListed in the page metadata for the badge how-to source.
SourceGPN23 shows the mature, low-tech side of hacker-event badge infrastructure: badges as social identity, pronoun/name/DECT surfaces, lanyard reuse, awareness signals, and logistics rather than a PCB.
The badge how-to documents ordered paper badges, badge punching, markers, lanyards, and a 105 x 74 mm A7 landscape, 450 g matte double-sided print specification for GPN23. It records that 1300 of 2500 badges and about 600 lanyards were used.
No badge firmware is source-backed for this record. The relevant systems are operational: registration/capacity control, FAQ guidance, DECT numbers written on badges, and the wiki/orga process for badge design and distribution.
The FAQ asks visitors to bring or donate lanyards to reduce waste, the awareness page asks people to use names and pronouns written on badges, and the orga page names Badges as the area responsible for participant name signs.
Lifecycle
The badge how-to records a hidden pattern concept in the printed design and preserves print-production details for A7 landscape badges.
SourceThe badge how-to and orga notes preserve safeR, orga, participant-name-sign, and area-owner context for different visible badge roles.
SourceThe FAQ asks visitors to bring a reusable lanyard or donate lanyards so the event can reduce waste while still issuing wearable badges.
SourceOperational history
The record remains image-free rather than copying wiki images, badge-design screenshots, attendee photos, placeholder art, or generated approximations.
The dossier keeps GPN23 discoverable while preventing false firmware, microcontroller, app-store, or hardware claims.
Badge pickup and identity workflow should be read alongside the event's registration and capacity-control model.