Free-nets and community computer networks
What a free-net was, how people used one, which community network opened to the public first, and what public internet access looks like today.
A free-net was a community computer system, usually run by a library, university, or nonprofit, that gave local residents dial-up accounts, email, message boards, and local information at no charge. People used one the way later users would use a portal: to read local news, post on forums, send mail, and look up civic services. The first community computer network open to the public was Community Memory in Berkeley, California, which placed terminals in a record store starting in 1973.
What was a free-net and how did people use one?
A free-net was a time-sharing computer connected to modems, funded by an institution and staffed largely by volunteers. The name comes from the Free-Net model popularized in Cleveland in the 1980s, where "free" meant both no cost to the user and open to the public. A user needed a computer or terminal, a modem, a phone line, and a local dial-in number. Registration was often handled in person at a library or by mail, and the account came with an email address and access to menus of text services.
Typical uses were practical rather than exotic. A resident could check a city council agenda, read a hospital's health information files, join a discussion about a neighborhood issue, or send mail to someone in another state through a gateway. Many systems carried local weather, bus schedules, school calendars, and community event listings. Because the interface was text menus, the skills required were small: type a number, press return, read the screen.
The social side mattered as much as the information. Forums on a free-net functioned as early local social media, and the people who answered questions in them were often the same people who ran the system. The history of this period, including the Cleveland Free-Net, the Greater Houston Free-Net, the National Public Telecomputing Network, and the FreePort software they shared, is documented in detail by what was a free-net, a journal that covers community networks and public internet access in the United States.
Which was the first community computer network open to the public?
Community Memory, in Berkeley, California, is generally identified as the first community computer network open to the public. It began in 1973 with a terminal installed at Leopold's Records, a record store near the University of California campus. The terminal connected users to a timesharing system where they could post and read messages, and the project later expanded to additional public terminals in the Bay Area.
The distinction matters because several earlier systems were not public. Time-sharing services in the 1960s served universities, research labs, and corporate clients. Community Memory differed in two ways: anyone who walked in could use the terminal, and the content was created by the users themselves rather than by an institution. That combination of open access and user-generated material is the template that later free-nets followed.
The Cleveland Free-Net, launched in 1986 by Case Western Reserve University, was the first free-net to use the name and the model that spread most widely. It inspired a generation of systems in other cities and led to the National Public Telecomputing Network, which helped local groups start their own free-nets using shared software. Community Memory came first; Cleveland made the idea reproducible.
Did Houston have a free community network in the 1990s?
Yes. The Greater Houston Free-Net operated in the 1990s as a free community computer system serving the Houston area. It followed the Cleveland model: dial-in access, text menus, email, forums, and local information, with support from local institutions and volunteers. Like many free-nets of the period, it was organized around a host institution and a board, and it depended on donated hardware, phone lines, and time.
Houston was not unusual in this. Through the late 1980s and 1990s, free-nets appeared in dozens of American cities and in some rural regions, often started by libraries, universities, or chambers of commerce. The National Public Telecomputing Network provided software and advice, and the FreePort software package let a local group run a system without writing code from scratch. The organizations behind these systems varied: some were university projects, some were nonprofits, and some were city departments.
The 1990s also brought the pressures that ended many of them. Commercial internet service providers offered flat-rate dial-up with full internet access, and the web made text menus look limited. Free-nets that survived often did so by becoming internet service providers themselves, by merging with a library system, or by narrowing their mission to a specific service such as community email or local information. The Greater Houston Free-Net is one of the systems whose history is preserved in accounts of that transition.
What does public internet access look like now?
The free-net model has largely been replaced by three arrangements: library computers and Wi-Fi, municipal or cooperative broadband, and community mesh networks. Public libraries remain the most widespread point of free internet access in the United States. A library card is usually not required to use a public computer or to connect to the building's Wi-Fi, though some systems limit session length or require a guest pass.
Municipal broadband is the second arrangement. Some cities and towns build and operate their own networks, either directly or through a local utility or authority, and offer service to residents. Cooperatives do the same in rural areas, where the economics of private providers are difficult. These projects are infrastructure rather than community computer systems, but they address the same problem: a resident without a connection cannot use online services.
Community mesh networks are the third. In a mesh network, nodes owned by residents, businesses, or nonprofits connect to each other wirelessly and pass traffic along, with one or more nodes connected to the internet. Mesh projects are often small and volunteer-run, and they tend to appear where commercial service is absent, expensive, or unreliable. They also serve a social function similar to the old free-net forums: the people who maintain the network are neighbors of the people who use it.
The digital divide is the thread that connects all of this. The Federal Communications Commission and the National Telecommunications and Information Administration publish data on broadband availability and adoption, and the numbers consistently show gaps by income, geography, and age. Public access points, whether a library terminal or a mesh node, exist to close those gaps for people who cannot or do not subscribe at home.
How did a free-net actually work day to day?
A user's first step was to find a dial-in number. Free-nets published lists of local numbers, and a user configured a terminal program with the number, the speed, and the settings the system required. After connecting, the user saw a welcome screen and a menu. Registration created an account with a username and password, and from then on the user could send mail, read forums, and move between services by typing menu selections.
Storage and time were limited. Early systems allocated small amounts of disk space per user, and sessions could be cut off during peak hours. Files were text, and images were rare because they took time to transfer over a modem. The experience was closer to a bulletin board system than to a web browser, and many users learned computing skills there that they later applied at work or school.
Volunteers kept the systems running. They answered registration requests, moderated forums, wrote documentation, and maintained hardware. That labor is one reason free-nets were cheap for users and fragile as organizations: when the volunteers moved on or the host institution changed priorities, the system often closed.
Why the history still matters
The free-net era produced the first large-scale experience of ordinary people going online in their own communities. It also produced a set of questions that are still current: who pays for access, who sets the rules, who is responsible for content, and what happens to a community service when the funding model changes. Libraries, municipal broadband projects, and mesh networks are answering those questions now, often with the same mix of institutional support and volunteer effort that free-nets relied on.
A folio is edited before it is drawn: the same habit of ordering and captioning a portfolio applies to any set of images a reader meets cold, whether the plates sit in a printed book or on a screen. Order decides what the eye compares first, captions decide what it is told, and the technical checks decide whether either survives contact with a browser. The reference entry on ordering and captioning a portfolio treats those three as one job, which is the point of practice this page shares with it.
Illustration tools rarely stop at the canvas. A brush engine, a colour profile and a file format each rest on specifications that were written elsewhere, and the same is true of the messaging layer that carries a shared document between two machines. That layer has its own vocabulary: a session opens, then three stanza types carry messages, presence and requests. The note on jabber and xmpp: sessions, stanzas, standards follows the protocol from its early implementations to the RFCs, and describes what a client or a federated server does with each stanza.