Reviving the 90s internet: meet FlameNet

Bringing AIM, IRC, BBSes and dial-up back to life on modern infrastructure.

Reviving the 90s internet: meet FlameNet

I miss the old internet. I do not mean the nostalgia-filtered version. I mean the actual texture: the screech of a modem handshake, “You’ve got mail”, BBS door games at 2am, IRC channels that felt like neighborhoods.

Most of that infrastructure is gone, so I have been rebuilding it. FlameNet is my attempt to bring deprecated, abandoned and beloved services back to life. It runs on modern infrastructure but still speaks the old protocols, so vintage clients can connect.

What is running

  • A BBS reachable over telnet or SSH. You dial in, in spirit, and get ANSI art and a login prompt.
  • AIM. I re-created AOL Instant Messenger servers. Point an old AIM client at them and the buddy list lights up.
  • IRC, with a web frontend for people who do not want to install a client.
  • Forums.
  • A fax line.
  • Windows 2000 and Windows XP guests, run as virtual machines you open in a browser tab, for the committed.

Three of these have their own posts. The AIM post and the BBS post follow this one:

This post kicks off a series documenting each service.

Old protocols, modern plumbing

None of this runs on period hardware. Everything is containerized with Docker. The services sit on one OVH VPS, behind a single Traefik reverse proxy, and they are backed up like any modern service.

The 90s experience is the interface. The 2020s reliability is underneath. I like that split. A BBS that goes down at 2am because a 30-year-old disk died is authentic and no fun at all.

What Traefik covers, and what it does not

Traefik with automatic TLS covers the web parts: the IRC web frontend, the forums and the browser access to the retro machines. Those speak HTTP, so Traefik terminates TLS and Let’s Encrypt certificates renew without my help.

The old protocols are different. Telnet, the AIM protocol and similar services are not HTTP. I publish their ports directly on the host. Traefik does not sit in front of them, and nothing wraps them in TLS.

A warning about passwords

Telnet and old AIM clients send credentials unencrypted. Anyone on the network path between you and the server can read what you type at login. That is how both protocols work, and nothing about my setup changes it.

So use a throwaway password on FlameNet. Do not reuse one from your email, your bank or anywhere else. If you want a safer connection to the BBS, use SSH instead of telnet. The AIM clients that FlameNet exists for have no such option, so the throwaway password is your protection.

I would rather say this plainly up front than have someone find out the hard way.

Why bother

The old services were small in a way modern ones are not. A BBS had one sysop and a few phone lines. An AIM server did one job. You could understand the whole system, and you could run your own.

That is part of what I am rebuilding. The other part is that a lot of these protocols are still documented, and people in the community have reimplemented the servers. I get to stand on that work and plug it into containers.

Try it

For now the best place to start is the BBS, since it works with any telnet or SSH client you already have. The AIM post explains how to point an old client at the server.

To connect in the meantime, go to flamenet.io.

Subscribe to Just another Geek

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe