Posted on

Ancient Web: The UUCP Project Mapped a Network Before the Internet Looked Like One

Before Internet routing became invisible infrastructure, one very practical problem was simply figuring out how to get from one Unix machine to another through a chain of dial-up connections.

Visit The UUCP Project, 1984

The Stargate Internet Museum’s page explains the problem neatly. Steve Bellovin had written pathalias, a program that could create routing information if it had a map of the network.

The problem was that no complete map existed.

UUCP networks were built from relationships between individual systems. One machine knew the machines it called directly. Those machines knew others. Mail and files could move hop by hop, but finding a good route across the larger network required knowledge that no single operator automatically possessed.

In January 1984, a birds-of-a-feather session at the USENIX conference in Washington, D.C. recruited more than thirty volunteers to build and maintain a map.

The resulting effort became known as the UUCP Project.

The network had human maintainers

The project divided responsibility among regional volunteers who supplied and maintained connectivity information. The maps were distributed through Usenet, eventually in the comp.mail.maps newsgroup, where other systems could collect them and generate routes.

Initial funding came from USENIX. When that funding ended, the work continued on a volunteer basis.

The museum page names Mark Horton as the person who ran the project, with major contributions from Mel Pleasant, Tim Thompson, Berry Kercheval, Steve Morenberg, Karen Summers-Horton, and a much larger collection of regional coordinators.

That structure is worth remembering because modern networking makes topology feel automatic.

In the UUCP world, the network map was partly a social artifact. Humans knew which systems existed, which links worked, who was responsible for which region, and how changes should be published so everyone else could calculate a path.

It was infrastructure maintained through cooperation and text files.

The Stargate Museum continues from this page into surviving 1984 map entries, which makes the exhibit more than a summary. It points directly at the kind of data that made the system work.

CacheRat’s 1,967 Ancient Web Domains research list includes pages like this because network history is easy to flatten into a straight line from ARPANET to today’s Internet.

The real history contains a lot more phone calls, volunteers, hand-maintained maps, and machines asking their neighbors for directions.

Explore the UUCP Project exhibit

Posted on

Ancient Web: Daniel Stenberg’s History of IRC

IRC history is messy in exactly the way real Internet history usually is: university machines, borrowed code, network splits, arguments, improvised fixes, and people naming infrastructure after whatever was happening around them.

Read Daniel Stenberg’s History of IRC

Daniel Stenberg’s page pulls that history into one long chronological account. He says he gathered information from multiple sources to verify stories and dates, and the page remains open to corrections through email, issues, and pull requests.

The story begins in Finland in summer 1988.

Jarkko “WiZ” Oikarinen wrote the first IRC client and server while working at the University of Oulu. The first server was tolsun.oulu.fi. Other universities began running servers, and by November 1988 IRC had spread across the Internet.

The network immediately became a network problem

By the middle of 1989, Stenberg’s history records about 40 servers worldwide. Then came disagreements, experiments, splits, reconnects, and the recurring discovery that letting humans share a network generates administrative problems almost immediately.

The page walks through EFnet, early splinter networks, Undernet, RFC 1459, and DALnet.

Some details are especially good because they explain why features appeared.

Undernet worked on timestamps, routing changes, and channel services partly because netsplits and channel takeovers were a recurring headache. DALnet pushed further into nickname and channel ownership and user protections.

Those features were not theoretical protocol decoration. People were annoying one another at scale, so somebody wrote software.

Stenberg also records IRC’s use during the Gulf War in early 1991, when live reports drew more than 300 concurrent users. That number looks tiny in 2026 and enormous when you remember what a distributed real-time Internet chat system looked like at the time.

For modern network builders, the history is useful because it shows protocol development under social pressure. Identity, moderation, routing, naming, abuse, and governance problems did not suddenly appear with social media.

We have been arguing with strangers through network software for a very long time.

This page is one of 1,967 sites in CacheRat’s broader Ancient Web research corpus.

Explore the 1,967 Ancient Web Domains research list

If you have ever typed /join, watched a netsplit, or wondered why IRC has so many oddly named historical networks, Stenberg’s account is worth the detour.

Read the full History of IRC