Pimp My IDE / garage dispatchBack to the garage
October 7, 2026 / typography / artifact custody

The font opened. The license did not.

A beautiful C64 keycap reconstruction landed with working font files, editable outlines, build scripts, and no license file at the commit we inspected. That is enough to study. It is not enough to ship on somebody else's site.

A download button proves access. It does not grant permission.

The artifact is real.

The C64 Keyboard repository describes a photo-based reconstruction of classic Commodore 64 keycap lettering. It ships TTF, OTF, and WOFF2 files, editable outlines, build tools, a web preview, and a package archive. The project says lowercase input maps to uppercase because it recreates printed key legends rather than the screen bitmap font.[1]

We checked commit 5b04391. Each font opened with FontTools. Every format reported version 1.107, 203 glyphs, 262 mapped characters, and complete printable ASCII coverage. The package archive contained 291 entries and passed its CRC test. The three direct font routes and the ZIP route resolved to downloadable files.

Artifact proof answers "does it run?" Permission answers "may we ship it?" Keep both questions.

The release gate still stays shut.

At the inspected commit, the repository had no LICENSE or COPYING file. GitHub's repository metadata also returned no detected license. The README calls the work an independent, unofficial reconstruction, but that sentence is not a reuse license.[1]

A Hacker News commenter reported that the download links seemed broken soon after the story appeared. Our later HTTP checks reached the font files and archive.[2] Both observations can be true at different times. A release card should record the exact route, commit, result, and check time instead of turning one click into a permanent claim.

A webfont needs a failure design.

If permission is clarified, the next decision is where the font belongs. This one is a strong display face for a poster, badge, or keycap label. It is a poor default for long body copy because its lowercase input displays as uppercase and its special mappings depend on the font.

MDN says font-display controls what the browser shows while a downloaded font is unavailable. The fallback value gives the font a very short block period and a short swap period. The optional value allows almost no block period and no swap period.[3] Pick the behavior on purpose. Then test the fallback at the same width, line length, and control size.

Keep the good weirdness inspectable.

The repository deserves credit for more than a novelty screenshot. It keeps the SVG outlines, mappings, build scripts, validation scripts, specimens, and provenance notes together. The build notes separate reconstructed geometry from the private source photographs and say the shapes are interpretations, not exact manufacturing artwork.[1]

That is the right kind of weird hack. The missing permission record is also real. We did not copy the font into this site. The customs bay below creates a release-card template for the day the paperwork, fallback, and stress checks are ready.

Interactive makeover / typeface customs bay

Build the release card.

Traditional purpose replaced: a font picker and a hopeful refresh. Better version: choose the real use, select the records the release needs, and copy a review card that keeps artifact access separate from permission and browser behavior.

Set the intended use

These controls select fields for a review template. They do not verify a font, grant a license, or approve a release.

Typeface job
Fields to include
1 of 4 release fields is selected.

The template has an artifact slot. Permission, fallback, and stress-check fields remain open. Evidence is still required for every selected field.

Sources read / October 7, 2026

Source log

Open the evidence boundary
  1. C64 Keyboard repository at commit 5b04391. Read and exercised October 7, 2026. The repository supplies the font files, package, README, build notes, outlines, mappings, and validation scripts. Pimp My IDE parsed all three font formats and tested the package archive. No license file was present at this commit.
  2. Hacker News item 49990224. Read October 7, 2026. The item maps the discussion to the exact repository URL. One early commenter reported broken download links. Pimp My IDE later checked the direct routes and found them resolving.
  3. MDN, "font-display". Read October 7, 2026. MDN defines the block, swap, fallback, and optional display periods used in the webfont failure plan.

Evidence boundary: this page verified file structure and current download access. It did not reproduce the private photographs, establish ownership of the reconstructed designs, or obtain reuse permission. The interactive card selects review fields. It does not inspect a font or approve a release.