Nytpu's curl site is a small, charming act of web craftsmanship: run curl nytpu.com and you get a full ANSI-colored terminal rendering of the site instead of raw HTML. It's a gimmick, the author freely admits, but it's the kind of gimmick that reveals how someone thinks about the web — as a place where multiple protocols and presentation layers can coexist without one dominating. The technique has two moving parts. First, generating ANSI-marked-up plaintext files — either by hand (as nytpu did for the index and about pages) or programmatically. Second, configuring Nginx to detect curl in the user-agent string and serve the terminal version instead of HTML. An X-Original: true header override lets users who actually want raw HTTP responses bypass the trick. The whole thing is static file serving with a conditional content-type switch. What makes nytpu's version distinctive is scope. Where predecessors trinkey and strongsand offered one or two hand-crafted pages, nytpu has curl versions of the entire blog — every post, auto-generated. This was only possible because of a decision made four years earlier: building a custom markup language (Gemroff) with ANSI plaintext as an output target, and a static site generator that already supported modular output formats for HTTP, Gemini, and Gopher. The curl site was a free lunch from years of architectural foresight. The author is refreshingly honest about this non-transferability. "This is the main thing that makes it hard to say it's easy," they write, acknowledging that the convenience was entirely contingent on bespoke tooling most people don't have. The hand-written approach — crafting a few fun pages with escape codes pasted from a Vim register and a Wikipedia reference page open — is presented as the realistic path for anyone else. There's a quiet lesson here about the relationship between personal infrastructure and creative possibility. The curl site exists because nytpu treats their web presence as a multi-protocol system rather than an HTML-first monoculture. Gemini, Gopher, HTTP, and now curl are all first-class output targets. That architectural pluralism is the actual interesting thing — the colored terminal output is just the visible symptom. The post ends with a genuine invitation: "It would be neat to see more sites doing this trick around!" And a spirited footnote defending their use of emdashes against accusations of AI-generated writing, which is both funny and a sign of the times. The emdash has been in their markup language since November 2022, thank you very much.
