Port 23, Still Open: The Tinkerers Turning Telnet Into Something Beautiful

Telnet was supposed to be dead. Security folks buried it years ago — no encryption, no authentication worth trusting, a relic from an era when the internet was a small room full of people who mostly knew each other. And yet, if you crack open a terminal right now and type the right address, you'll find something unexpected on the other end: art, games, poetry, community. Alive. Waiting.

Port 23 never really closed. It just stopped being the kind of place most people looked.

What Telnet Actually Is (And Why Anyone Still Cares)

For the uninitiated: telnet is a network protocol that lets one computer talk to another over a raw text connection. No browser. No graphics pipeline. No JavaScript framework arguing with itself in the background. You connect, characters appear on your screen, you type back. That's it. It dates to 1969, which means it's older than the floppy disk, older than the PC, older than most of the people currently using it ironically — and some using it completely sincerely.

In its heyday, telnet was how you dialed into university mainframes, accessed library catalogs, played MUDs, and poked around systems that were, in retrospect, shockingly open to the public. The protocol didn't assume bad actors because the network itself didn't have many yet. That trust was eventually weaponized, and SSH replaced telnet for anything serious. But "serious" isn't really what this crowd is chasing.

What they're chasing is the texture of that old connection. The slight delay. The monospace font. The feeling that you're actually somewhere when you arrive.

The Servers That Never Went Dark

Some telnet destinations have been running continuously for decades. Towel Day enthusiasts probably know about towel.blinkenlights.nl — a server that's been streaming Star Wars Episode IV in ASCII art since 2000. It still works. You can still watch it. Every year, a few thousand people apparently do.

But that's just the most famous example. The broader telnet landscape is stranger and more varied. There are MUD servers — multi-user dungeons — that have been running the same fantasy world since the early '90s, with player characters older than some of their current users. There are weather services, chess servers, and at least one telnet endpoint that just reads you the King James Bible, line by line, as fast as you can scroll.

None of these are accidents. Someone set them up. Someone keeps paying for the hosting. Someone is, on some level, committed to the bit.

New Builders, Old Protocol

What's shifted recently is who's building new telnet experiences — and why. The people spinning up fresh telnet servers in 2024 aren't, for the most part, gray-bearded sysadmins keeping the flame alive out of professional obligation. A lot of them are younger developers who discovered the protocol through retro computing communities, BBS nostalgia rabbit holes, or just sheer curiosity about what the internet looked like before it became a shopping mall.

Take the small but active community around "text-mode art servers" — telnet destinations that serve up ANSI art, ASCII animations, and interactive text experiences that feel closer to experimental theater than anything you'd find on a normal website. These aren't recreations of old content. They're original work, built with the protocol's limitations baked into the creative process from the start.

One developer based in the Pacific Northwest, who goes by the handle Phosphor_88 in the communities where he's active, described his approach this way in a forum post that made the rounds earlier this year: "When you strip out everything the modern web assumes you need, you're left with the question of what actually matters. Turns out a lot of people just want words and maybe some color. The rest is overhead."

That sentiment — that modern web development has drifted toward solving problems it created for itself — shows up constantly in conversations around telnet revival projects.

The Poetry Machines and Experimental Edges

Some of the most interesting new telnet work is happening at the weirder fringes. There are generative poetry servers that spit out procedurally assembled verse when you connect, styled to look like something you might have found on a 1987 university terminal. There are collaborative fiction spaces where multiple users type into a shared document in real time, the whole thing unfolding in plain text with no formatting beyond what ASCII allows.

One project that got some attention in retro computing circles is a telnet server that presents itself as a fictional 1983 research institution's internal network — complete with fake memos, simulated file directories, and occasional "system messages" that play into an ongoing alternate history narrative. It's part game, part art installation, part love letter to a computing aesthetic that most of its visitors never actually lived through.

There's something genuinely interesting happening at the intersection of constraint and creativity here. When you can't use images, you think harder about words. When you can't use animation, you think harder about timing. When you can't track users or serve ads or A/B test your button colors, you're left with nothing but the experience itself.

Why the Constraints Feel Like the Point

This is the part that's hard to explain to people outside these communities, but it's worth trying. The argument isn't that telnet is better than the modern web in any practical sense. Nobody's suggesting hospitals should switch their patient portals to port 23. The argument is that deliberate constraint is a useful creative and philosophical tool — and that sometimes the best way to understand what something is for is to strip it down to nothing and rebuild from there.

The web in 2024 is extraordinary in its capabilities and genuinely exhausting in its complexity. A simple webpage now involves dozens of third-party scripts, tracking pixels, CDN negotiations, and rendering pipelines that would have seemed like science fiction to the people who invented telnet. All of that infrastructure exists for real reasons. And yet.

When you telnet into a server and a haiku appears on your screen — just text, just characters, just the thing itself — something about the directness of it lands differently than reading the same poem on a website surrounded by cookie consent banners and autoplay video ads.

The Community Holding It Together

Like most retro tech communities, the telnet revival runs on a mix of mailing lists, Discord servers (the irony is not lost on anyone), and the occasional IRC channel. People share server addresses, troubleshoot connection issues, debate the finer points of terminal emulation, and argue about whether using a modern SSH client to connect to a telnet server somehow breaks the purity of the experience.

It's a small world. But it's a real one, with its own culture, its own in-jokes, its own sense of what matters. And it's growing, slowly, as more people stumble into it from adjacent communities — BBS nostalgia, text game preservation, old-school Unix appreciation.

Port 23 is still open. The question is whether you remember how to knock.