ITEMInformation Transmission Evolution MapA visual history of human information
Big-picture essay

How networks turned computers into communication systems

A connected explanation of the historical systems, trade-offs and transitions behind this part of ITEM.

1. Batch Scope

This study examines four transitions:

  • Computer networks and ARPANET Computer Networks and ARPANET;
  • Internet and TCP/IP Internet and TCP/IP;
  • Email Email;
  • Bulletin-board systems, Usenet and Internet chat Bulletin-Board Systems, Usenet and Internet Chat.

The cluster begins below the application layer with operational host networking, rises through internetworking, then examines two families of human communication built above those layers.

2. Central Finding

A network carries traffic among connected hosts. An internetwork joins independently designed networks. Email addresses messages to mailboxes. Boards, newsgroups and chat turn infrastructure into social places.

The four topics form a layered sequence:

Packet switching ↓
Computer networks and ARPANET ↓
Internet and TCP/IP ↓
Email ───────── Shared communities ├─ BBS ├─ Usenet └─ IRC

This is not a simple replacement chain. Email developed on shared hosts and ARPANET before the mature Internet. BBSs could operate through telephone dial-up without Internet access. Usenet could propagate over several transports. IRC later depended more directly on Internet server networks. The map therefore records dependencies as historically variable rather than pretending every application was born on the modern Internet stack.

3. Four Distinct Units of Coordination

| Topic | Primary unit | What is coordinated | |---|---|---| | Computer network / ARPANET | Host and network service | Remote machines, processes and resources | | Internet / TCP/IP | Internetwork datagram | Heterogeneous networks and end systems | | Email | Addressed message and mailbox | Asynchronous senders, relays and recipients | | BBS / Usenet / IRC | Board post, news article or channel message | Persistent or synchronous communities |

4. Boundary Corrections

4.1 Packet switching is not ARPANET

Packet switching is a method of dividing and forwarding traffic through shared links. ARPANET was a specific operational network using IMPs, leased circuits, host interfaces, NCP, applications, operators and participating sites.

4.2 ARPANET is not the Internet

ARPANET initially coordinated communication inside one network. The Internet architecture connects multiple networks while preserving their internal differences.

4.3 TCP is not IP

IP forwards datagrams across network boundaries. TCP provides reliable ordered transport between endpoints. A protocol suite may include both, but their jobs are different.

4.4 Addressing is not naming

Addresses support delivery inside a network architecture. Names provide human-facing or application-facing reference and require resolution. A name can remain stable while an address changes.

4.5 Routing is not forwarding

Routing computes or distributes path information. Forwarding applies that information to an individual packet at one device.

4.6 Email is not SMTP

SMTP transfers mail. Email also requires message formats, addresses, user agents, mailboxes, delivery agents, retrieval, relays, non-delivery handling and governance.

4.7 The visible To field is not the delivery envelope

A message header may describe intended readers while the transfer system carries a separate recipient set. Mailing lists, blind copies and redirects make the distinction unavoidable.

4.8 BBS, Usenet and IRC are not interchangeable

A BBS is typically one host controlled by a sysop. Usenet replicates persistent articles among federated servers. IRC relays live messages through server networks and channels.

5. Temporal Architecture

| System | Requires simultaneous presence? | Default persistence | Main social rhythm | |---|---:|---|---| | Email | No | Mailbox copy | Correspondence | | BBS | No | Local message database | Return visits | | Usenet | No | Replicated news spool | Distributed threaded discussion | | IRC | Usually yes | Optional logging | Live conversation |

Persistence changes who can participate. Synchronous communication privileges those who are present at the right moment. Asynchronous systems widen temporal access but create queues, backlogs and archives.

6. Topology and Power

| Architecture | Typical authority | Main concentration risk | |---|---|---| | ARPANET | Programme managers, network operator and site administrators | Funded-site access and subnet operation | | Internet | Standards, registries, network operators and carriers | Backbone, exchange, DNS and cloud concentration | | Email | Domain and mailbox providers | Provider lockout, filtering and identity dependence | | BBS | Sysop | Absolute local control | | Usenet | Site and feed administrators | Backbone peering and propagation policy | | IRC | Network, server and channel operators | Server hubs, operator privilege and splits |

Open protocols distribute implementation authority, not necessarily infrastructure ownership. Federation distributes hosting, not necessarily moderation power. Pseudonyms distribute expression, not necessarily privacy.

7. New Comparison Dimensions

This study adds the following dimensions to the map:

  • network scope: link, local network, wide-area network or internetwork;
  • host/subnet function split;
  • protocol layer and service layer;
  • address, name, route and identity separation;
  • gateway role and network autonomy;
  • specification, implementation, deployment and adoption status;
  • message format, envelope, transfer and mailbox layers;
  • asynchronous persistence and notification model;
  • community topology: local, federated or server-networked;
  • propagation model: delivery, replication or live relay;
  • presence requirement;
  • operator and moderator powers;
  • access-cost geography;
  • protocol decentralisation versus service concentration.

8. Constraint Cascade

Expensive isolated computers ↓ computer networking
Remote hosts and resources become reachable ↓ internetworking
Unlike networks become mutually reachable ↓ email
People can correspond asynchronously across hosts and networks ↓ boards, news and chat
Network users form persistent and live communities

Each reduction creates a new scarcity:

  • connectivity creates protocol compatibility problems;
  • internetworking creates global naming and routing problems;
  • cheap mail creates attention and abuse problems;
  • shared communities create moderation and governance problems.

9. What Survived

Modern systems still use:

  • layered protocol stacks;
  • routers between networks;
  • endpoint transport;
  • user@domain addresses;
  • message headers and bodies;
  • mail queues and relays;
  • boards, threads and replies;
  • channels and presence;
  • moderators, bans and operator privileges;
  • federated server relationships;
  • asynchronous and synchronous modes inside one application.

The polished interface changed. The bones are still visible.

10. Content Thesis

A strong public-facing synthesis would reject the idea that “the Internet invented online communication” in one step. The historical sequence is messier and more interesting:

Engineers first connected machines, then connected networks, then built mailboxes, boards and rooms inside the resulting space. Every new room required somebody to keep the keys, sweep the floor and throw out the occasional digital arsonist.

11. Batch Verdict

This study completes the networking and online-communication core of Era V. It shows that transmission infrastructure becomes socially transformative only after identities, addresses, storage, protocols, interfaces and governance are layered above it.

The cable and packet created reach. The mailbox, board, newsgroup and channel created somewhere to meet.