On Air
Free-nets: the public computer networks that came first
A free-net gave dial-up users email, forums and local information before the web. Cleveland, Houston and the NPTN built the model that libraries still echo.
Pieces in this section
-
How an emergency alert interrupts a song
The header burst, the two-tone attention signal, the relay chain that predates the internet, and why the system is deliberately built to survive the failure of everything modern.
13 minute read4 notes
-
How far a station is allowed to reach
Height above average terrain, the class table, the protected contour, and why a low-power station on a hill can beat a high-power station on a plain.
13 minute read4 notes
-
Why the AM band changes at sunset
Ground wave by day, sky wave by night, and the whole apparatus of power reductions, directional patterns and sign-off times that exists because of it.
12 minute read4 notes
-
What is actually riding on an FM carrier
The baseband, layer by layer: mono sum, pilot tone, stereo difference channel, station text, and the digital sidebands that sit outside all of it.
14 minute read5 notes
A free-net was a community computer system that anyone in a city could dial into at no charge, usually through a library card or a local phone number, to read mail, post on forums and look up local information. The first one open to the public at large was the Cleveland Free-Net, which went live in 1986 at Case Western Reserve University. Houston had its own version, the Greater Houston Free-Net, running by the early 1990s.
What was a free-net, and how did people use one?
The term covers a specific kind of machine: a Unix host, a bank of modems and a menu-driven interface that a beginner could navigate with arrow keys. The user connected from a home computer, a terminal at a library or a school lab, and landed in a text world organized like a small town. There were "buildings": a post office for private mail, a courthouse for public notices, a schoolhouse for courses, a town hall for discussions, and a newsstand for wire copy and local bulletins.
The account was free. The costs were carried by a university, a hospital, a library system, a city government or a mix of them, sometimes with donations and grants. Users paid only the phone call, and many free-nets published local dial-in numbers so the call stayed inside the local exchange. That detail mattered: in 1990 a long-distance modem call cost real money by the hour.
Use was mundane and practical. A resident could send mail to a neighbor who had no other address, ask a question in a health forum moderated by a hospital librarian, read a city council agenda posted the day before the meeting, or leave a message for a teacher. Community organizations used the same system to publish meeting minutes and calendars. For readers who want a fuller account of what was a free-net and how the model spread across the country, the history is well documented in the same tradition of independent community networking writing.
Which was the first community computer network open to the public?
The Cleveland Free-Net is the usual answer. It grew out of an earlier experiment, St. Silicon's Hospital and Information Dispensary, a medical question-and-answer service started in 1984 by Dr. Tom Grundner at Case Western Reserve University. The dispensary let the public leave medical questions for volunteer physicians. When the service expanded into general civic topics in 1986, it took the name Free-Net and opened registration to anyone in the Cleveland area.
The National Public Telecomputing Network, known as the NPTN, was founded in 1989 to spread the idea. It functioned as a clearinghouse: it published a how-to manual, ran a conference for operators, and licensed a software package called FreePort so that a new city could stand up a free-net without writing its own code. FreePort was built on Unix and presented the familiar building-and-menu metaphor, which meant a volunteer in another state could learn the system quickly.
By the mid-1990s the NPTN counted dozens of affiliated systems in the United States and a few abroad, from Ottawa to Wellington. The organization also ran a national backbone that let users on one free-net send mail to users on another, an early taste of what a public network could be.
Did Houston have a free community network in the 1990s?
Yes. The Greater Houston Free-Net served the Houston area in the early and middle 1990s, following the Cleveland template with local forums, mail and information pages. It was one of a cluster of Texas systems, alongside efforts in Austin and other cities, that gave residents a dial-up route into a shared civic space before commercial internet accounts became cheap.
These systems depended on institutional hosts. A university, a public library, a medical center or a municipal department supplied the machine, the room and the phone lines. Volunteers staffed the help desk and moderated forums. When the host's priorities changed, or when the volunteer core aged out, the service could end quickly. That fragility is the pattern behind many free-net closures in the late 1990s.
What happened when the web arrived?
Two pressures arrived at once. The first was the graphical web, which after 1993 made text menus look dated to new users. The second was the commercial internet service provider, which by 1996 offered unlimited dial-up access for a flat monthly fee and a browser in the box. A free-net could not match the content, and it could not match the marketing.
Some systems adapted. They added web gateways, moved their forums to web pages, and kept the community. Others folded. The NPTN itself ceased operations in 1996, and its affiliated systems either closed, merged into university services or became small independent providers. The Cleveland Free-Net ran until 1999, when Case Western Reserve University shut it down.
What survived was not the software but the arrangement: a public institution providing a computer, a connection and a person who can help. That arrangement is still visible.
What does the same idea look like today?
Public library terminals are the direct descendant. A library card still gets a resident onto a machine with internet access, and staff still help with the first steps: creating an email account, filling out a form, printing a document. The difference is that the library no longer runs the mail server or the forum. It supplies the door.
Community broadband projects carry another part of the inheritance. Municipal and cooperative networks in places without reliable commercial service build the physical link, often with public meetings and volunteer boards that would look familiar to a 1990s free-net organizer. Neighborhood mesh networks do something similar at a smaller scale, sharing a connection across rooftops and apartment buildings.
The forums moved too. Where a free-net hosted a town hall, a modern equivalent might be a local email list, a library-hosted calendar or a community group on a commercial platform. The medium changed; the wish for a shared local space did not.
Why the free-net still matters to organizers
The free-net era produced a set of practical lessons that community technology projects keep rediscovering. One is that the host institution matters more than the software. A library, a university or a city department that treats public access as part of its mission will keep a service alive through hardware changes; a project without that backing depends on the energy of a few people.
A second lesson is that training is part of the service. Free-nets ran help desks and printed guides because a menu system is not self-explanatory to a first-time user. The same is true of any public access point today.
A third is that local content draws local users. A city council agenda, a school calendar or a clinic schedule posted where residents can find it gives a network a reason to exist beyond the connection itself.
A fourth is cost transparency. Free-nets published their dial-in numbers and their funding sources, and users understood what was free and what was not. Modern projects that explain who pays for the fiber, the router and the staff tend to earn more trust than those that do not.
The free-net was not a precursor to the commercial internet so much as a parallel attempt to answer a different question: what does a community do with a network once it has one? Cleveland answered with a town square. Houston answered with a local version of the same. The answers changed, but the question has not gone away.
The free-net model stopped at the modem, but the same question of how a link comes up before any data moves reappears in modern hardware. A serial bus must agree on width, speed and encoding before traffic flows, and how PCI Express lanes are trained covers the LTSSM states and the PIPE interface between controller and physical layer. Readers who followed Cleveland and Houston dial-up ports will recognize the pattern: negotiation first, payload second.