We explored how technologies stay with us in the previous article and how certain systems continue to matter long after they disappear from everyday use. That persistence does not stop at individual machines. It extends into the networks people used, and the communities built around them.

Before the Internet became a single connected system, online communication existed as separate networks. They overlapped, competed, and eventually merged into what became the modern Internet.

The familiar story of the Internet is a straight line toward TCP/IP and the Web. The reality was messier. Bulletin Board Systems, FidoNet, commercial services, and early Internet access all coexisted, each shaping how people experienced being online.

What follows is that overlap period: how people connected, how messages moved between systems, and how dial-up Internet bridged isolated communities into a shared network.

Bulletin Board Systems

“Each BBS was its own world, reachable only by dialing into it directly.”

Bulletin Board Systems were where online life first felt local. Each system ran on a single machine, usually in someone’s home or office, connected through dial-up modems and telephone lines.

There was no central platform. Each BBS stood alone.

Finding a BBS

Discovery was simple and uncertain. Listings in magazines or local newsletters provided only a name and a phone number. In Sacramento, California Computer News listed nearby systems in the back pages. You dialed first and learned what the system was.

That uncertainty shaped the experience more than anything else.

Tip: Early online discovery was not search-based — it was trust-based dialing.

Local Systems and Identity

Systems like Colossus and Third Rock were discovered through repetition rather than description. They became familiar only after repeated visits. Colossus later turned out to be run by a teacher at a local high school, which blurred the line between online space and real life in a way that felt natural at the time.

Participation

Use often became involvement. For a time, I helped manage user uploads on a local BBS, organizing files and maintaining system flow. Users were often part of the system’s operation rather than separate from it.

Sysop Control

Every system reflected its operator. Some were strict, others informal, but all of them were personal in a way modern platforms rarely are. The sysop defined structure, tone, and culture more than any software layer.

The personality of a BBS mattered as much as its features. Some systems felt open and conversational, while others were tightly moderated or focused on specific communities. You did not learn “the BBS experience” once—you learned a different version every time you dialed a new number.

FidoNet and Store-and-Forward Networks

“Messages did not travel instantly — they moved on schedules, not demand.”

As BBS systems expanded, they began exchanging messages through scheduled dial-up connections. That coordination became FidoNet.

How FidoNet Worked

Each system acted as a node in a larger chain. Some systems functioned as hubs, collecting messages and forwarding them onward. Messages moved from local systems to regional hubs and then across broader networks, eventually reaching other countries.

Nothing traveled instantly. Everything moved in batches shaped by timing.

Scheduled Connectivity

Transfers happened during scheduled windows, often overnight when phone rates were lower and lines were free. Connectivity was not continuous — it was planned.

Human Routing

Routing was configured by sysops who determined who called whom and when. The network scaled through coordination rather than centralized infrastructure.

In practice, message delivery varied depending on geography and timing. Local messages might appear within hours, while international transfers could take days. Communication followed rhythm rather than immediacy.

Tip: FidoNet scaled like a postal system made of phone calls — delay was part of the design.

Commercial Online Services

Commercial services developed alongside BBS culture but followed a more centralized model. Systems like CompuServe, AOL, Prodigy, and GEnie created structured environments where messaging, forums, downloads, and content libraries lived inside a single controlled boundary.

Controlled Environments

These systems were easier to access, but far less flexible. Everything existed inside a managed ecosystem rather than a distributed network.

“The platform was the boundary — everything happened inside it.”

Even within these controlled environments, communities formed that felt distinct from the platform itself. Users often identified more with specific forums or groups than with the service as a whole.

Transition to the Internet

Over time, gateways connected these services to email and Usenet. The separation between closed services and open networks gradually dissolved.

Dial-Up Internet and Shared Connectivity

Dial-Up Internet still relied on telephone lines, but the model shifted. Instead of calling a specific system, users connected to an Internet Service Provider that acted as a gateway into a larger network.

Session-Based Internet

Connections were temporary. A session began with a dial-in, a handshake, and a short window of use before disconnection. The Internet only existed while the line was active.

Tip: “Always-on Internet” did not exist yet. Being online was an intentional act, not a background state.

Constraints of the Line

Dial-up shaped usage in practical ways. Pages loaded slowly, downloads took time, and interruptions were normal. In many homes, the phone line could not be used for anything else while online.

“Being online meant occupying the phone line — and everything else paused.”

Workarounds and Fragility

Connections dropped without warning, and busy signals were part of everyday experience. Even installing early Linux distributions, including Red Hat releases, often required repeated attempts over unstable connections.

The modem handshake itself became recognizable—a sequence of tones marking the shift from a private phone line into a shared network. Some users could tell from the sound alone whether a connection would hold.

Some users combined multiple modems or accounts to increase speed. It worked, but only as an adaptation to constraint rather than a designed feature.

The Internet as Convergence Layer

The Internet did not emerge as a single invention but through convergence. Separate networks gradually adopted shared protocols, especially TCP/IP, allowing them to interconnect.

Network Evolution

ARPANET evolved into NSFNET, and commercial providers expanded access. Standardization created compatibility, but not immediate unification.

The Web Layer

The Web later simplified everything into pages and links, hiding most of the underlying network structure from everyday users.

Tip: Convergence did not erase older systems — it made them interoperable until they gradually faded from use.

Overlap Instead of Replacement

For a long period, older and newer systems existed at the same time. BBS networks, AOL, Usenet, IRC, email, and the early Web all operated in parallel.

Parallel Use

Users moved between systems depending on need, cost, and access. No single system replaced the others immediately.

“For years, ‘the Internet’ was not one thing — it was a collection of ways to connect.”

Gradual Transition

Some BBS systems persisted into the Internet era, while others adapted by adding Internet connectivity while preserving their original structure.

Change happened through overlap, not replacement.

The Legacy of Early Networks

Many modern communication patterns come directly from these systems. Forums carry forward the structure of BBS message boards. IRC shaped real-time chat. File areas became the foundation for modern sharing systems. Even usernames and handles reflect earlier identity systems.

Communication was slower and more deliberate, and systems shaped interaction as much as users shaped them.

Tip: Many modern patterns are not inventions — they are compressions of older network behavior.

Modern BBS Revival

BBS systems still exist today. Modern software such as Synchronet and Mystic BBS runs on current infrastructure while preserving the original structure of message boards, file areas, and sysop-controlled communities.

Continuity, Not Simulation

These systems are not recreations. They continue the same model using modern transport layers like telnet, SSH, and web access.

One example is bbs.excalibursheath.com, a modern BBS modeled after 1980s and 1990s systems. It preserves structure while running on modern infrastructure.

“A modern BBS is not nostalgia — it is the same architecture running on different wires.”

Summary

Online communication developed through overlapping systems rather than a single unified design.

BBS networks, commercial services, academic systems, and early Internet access all coexisted before converging into a shared structure.

Dial-Up Internet acted as the transition layer between isolated systems and always-on connectivity. It was slow and unreliable, but it connected systems that previously did not interact.

Many of the patterns established during that period still shape modern communication. Some systems continue to operate today, preserving the structure of early online communities in updated form.