How to hack your GitHub Universe 2025 badge

Key Concepts

• Conference Badge as a Mini-Computer: The central premise is that modern conference badges are not just static identification but are programmable devices.
• Disc Mode: A specific operational state for the badge that allows it to be accessed and modified by a computer.
• VS Code (Visual Studio Code): A popular source-code editor used for developing and modifying the badge's software.
• Python: The programming language used to develop the badge's application, highlighting its flexibility for customization.
• GitHub: A platform for version control and collaboration, used here to host and share the open-source code for the badge hacks.
• Secrets File: A configuration file within the badge's software where sensitive or user-specific information (like a GitHub handle) is stored.
• Badge App: The application running on the badge that displays information and can be interacted with.
• Open Source: The code for the badge hacks is publicly available, allowing for community contributions and modifications.

Hacking a Conference Badge: Adding Personal Information

This section details the process of customizing a conference badge to display personal information, specifically a GitHub handle. The core idea is to treat the badge as a mini-computer that can be reprogrammed.

1. Entering Disc Mode: The first step involves putting the badge into a special "disc mode." This is achieved by flipping the badge over and pressing the button labeled "disc" (indicated by two dots above the reset button) twice. This mode allows the badge to be recognized and accessed by a computer.

2. Connecting to a Computer and Accessing the Hack: Once in disc mode, the badge is plugged into a machine. The computer then recognizes the badge, and the user navigates to a specific website containing available "hacks." The example focuses on the "set your GitHub handle hack."

3. Modifying the Badge Software with VS Code: The hack's code is then opened in VS Code. The transcript highlights that the badge runs on Python, implying a high degree of flexibility for customization.

• Updating the Secrets File: The initial modification involves updating a secrets file. This file is where user-specific data, such as the GitHub username, is entered. The user is instructed to type their GitHub handle into this file.
• Replacing the Badge File: To implement the hack, the code from the main badge.py file on the user's device needs to be replaced with the code from the GitHub repository. This is done by copying the code from the online repository and pasting it into the local badge.py file on the device, followed by saving the changes. The transcript emphasizes that the code is open-source, meaning anyone can contribute.

4. Verifying the Hack: After saving the modified code, the user navigates back to the badge application to view their badge. The process involves the badge connecting to the computer and fetching user data. The demonstration shows the badge successfully displaying the updated information, confirming the hack's success.

Key Argument: The primary argument presented is that conference badges are increasingly sophisticated devices capable of running custom applications and displaying dynamic information, making them targets for simple "hacks" or customizations. The open-source nature of the provided hacks further democratizes this process.

Notable Statement: "This conference badge is a mini computer. Let's hack it together." This statement sets the stage for the entire demonstration, framing the badge as a programmable device.

Technical Terms Explained:

• Disc Mode: A state where the badge acts as a removable storage device, allowing file access and modification.
• VS Code: A free source-code editor developed by Microsoft, widely used for programming.
• Python: A high-level, interpreted programming language known for its readability and versatility.
• GitHub Repo: A repository (a project folder) hosted on GitHub, containing the source code and related files for a project.
• Secrets File: A file typically used to store sensitive configuration data, such as API keys or user credentials, separate from the main application code.
• Badge App: The software application that runs on the conference badge itself, responsible for its functionality and display.

Logical Connections: The process flows logically from preparing the badge (Disc Mode), to accessing the necessary tools (VS Code, GitHub), modifying the code (secrets file, badge file), and finally verifying the changes through the badge's application.

Data/Research Findings: No specific data or research findings are presented in this transcript, as it focuses on a practical demonstration.

Conclusion

The demonstration effectively illustrates how a conference badge can be reprogrammed to display personalized information, such as a GitHub handle. By entering "disc mode," connecting to a computer, and utilizing VS Code to modify Python code hosted on GitHub, users can customize their badges. This process highlights the increasing computational power and programmability of everyday devices like conference badges and the accessibility of such modifications through open-source initiatives.