Remember the internet when it was weird? When Comic Sans wasn’t a crime, and chat rooms were pixelated playgrounds where you could be a cartoon robot with a neon afro? I do. I never got over Microsoft Comic Chat from 1996. So when the source code was released last week, I did something that sounds insane: I rebuilt it. In one HTML file. With end-to-end encryption. And I cannot write a single line of code.
I’m the proverbial product manager. The person who draws boxes on whiteboards and asks engineers to ‘make it pop.’ But I had a secret weapon: GPT 5.6 and Fable 5 / Opus 4.8. I fed them the original source, described what I wanted, and watched them translate a 28-year-old chat engine into a modern, secure, single-file web app. You don’t need to write code to bring back the dead. You just need to remember why it mattered in the first place.
Let me be clear: this isn’t some emulated museum piece. It’s a living, breathing chat room. One link, up to ten friends, everyone typing into the same comic strip live. Your names, your lines, even your uploaded backdrops are encrypted with AES-GCM before they ever leave your browser. The relay — a Cloudflare Durable Object — can’t read a single word. Keys live in the URL fragment, which browsers never send to servers. Microsoft’s silly 1996 chat app is now more secure than most messaging apps you use today. That’s the kind of plot twist the internet deserves.
I’m not a security researcher. I’m a nostalgic guy with a laptop and a subscription to an AI service. But I knew enough to ask: ‘Can we make it so no one can spy on the conversation?’ The AI said yes, and showed me the code. I didn’t understand half of it, but I tested it. It works. The critical skill isn’t writing code — it’s deeply understanding the original product’s essence and what your users actually need. That’s a lesson every product manager and founder should tattoo on their arm.
Yes, it’s one HTML file. No WASM, no emulation, no compilation. The constants are reproduced by hand from the source because I wanted it to feel exactly like 1996 — right down to the geometry of the characters. There’s a ‘For Nerds’ tab that explains the crypto routines and the rendering engine. But here’s the thing: I didn’t write those explanations either. I asked the AI to document its own work. The tools have become smart enough to explain themselves. The only barrier left is the courage to ask.
Oh, and Comic Sans is optional. Barely.
Try it. Send a link to a friend. Be a cartoon character again for five minutes. Because the internet used to be fun, and it doesn’t have to be a hyper-optimized, algorithm-driven machine. Sometimes the best thing you can build is a time machine that also happens to be encrypted. And you don’t need to know how to code to build it. You just need to remember what made you smile.
FAQ
Q: Is a single HTML file really secure enough for private chats?
A: Yes, because the encryption happens in the browser, not on the server. The Cloudflare relay only orders events and can't read them. Keys are non-extractable, stored in the URL fragment, and never transmitted. AES-GCM with WebCrypto is a proven standard. The app is as secure as the browser's crypto implementation.
Q: What does this mean for preserving old software?
A: It means anyone — not just coders — can resurrect and modernize legacy digital artifacts. AI can translate source code, add security, and even document the process. The bottleneck shifts from technical skill to understanding the original product's essence and user needs. This democratizes software preservation.
Q: Isn't this just a gimmicky toy? Why would anyone use it?
A: The contrast between a playful Comic Sans aesthetic and enterprise-grade encryption is exactly the point. It proves that security doesn't have to be boring. It also shows that the 'toy' of 1996 can be a fully functional, ephemeral group chat that's more secure than Slack. Sometimes the best ideas are the ones we abandoned too soon.