What the free-net years still teach about public access

A free-net was a community computer system that gave the public free dial-up access to local information and to the early internet, usually through a library, a university or a civic body, and usually for the price of a telephone call. People used one to read local notices, to post on discussion boards, to send mail, and in time to publish the first pages of a club or a charity. The model answered a question that is still current: who builds the network when nobody is selling one.

The history is worth a security desk's attention because the free-nets settled several questions early. They ran shared terminals in public places, they registered users by name, and they hosted pages for organisations that had no budget for hosting. Every one of those choices is now a routine part of public access, and every one of them created the same tension between openness and accountability.

What was a free-net and how did people use one?

In practice a free-net was a modem bank and a text menu with a civic service at the other end of the line. A user dialled in, registered locally, and reached local information, discussion boards, mail and, later, web pages hosted for community organisations. Access was free at the point of use, which meant the cost sat with the institution running the machine rather than with the reader.

The Local Loop, an independent journal on community networks and public internet access, documents that period from the archived record, and its explanation of what was a free-net covers the systems, the people who built them and the community pages they carried. The same publication follows what replaced them, from the digital divide to the library access points and low-cost options that serve the same purpose today.

Which was the first community computer network open to the public?

Cleveland Free-Net is the usual answer. It grew out of a medical question-and-answer board into a public system used by tens of thousands of residents, and it became the model that other cities copied. The federation behind the name, the National Public Telecomputing Network, licensed the Free-Net label and shipped the FreePort software that let a new city start from a working system rather than from scratch.

That combination is why the idea spread quickly and then faded quickly. A licensed name and shared software lowered the cost of starting, while the funding and the volunteer effort needed to keep a modem bank running were local and uneven.

Did Houston have a free community network in the 1990s?

Yes. The Greater Houston Free-Net offered residents free access from 1997 and hosted pages for local nonprofit organisations, which is how many churches, charities and clubs first appeared on the web. At the time, publishing a page was not a product anyone could buy cheaply, so a community system that hosted pages for its members was the practical route onto the network.

Those pages are also the reason the period still matters to anyone auditing a small organisation's online history. A club's first address was often a path inside somebody else's system, and the record of it survives in archives rather than in a domain registration.

What carried over into public access today

Libraries are still the access point of last resort, and shared machines still raise the questions the free-nets had to answer: who signs in, what a session leaves behind, and what happens to a document after the terminal is closed. The funding and the policy that keep a public terminal open are argued in the open, and the American Library Association publishes its current position on library broadband policy where the terms of that argument are set out. The habits are modest and worth stating. Sign out rather than closing the window, do not save credentials on a public machine, print or transfer a file deliberately rather than leaving it on the desktop, and treat any document copied on a shared system as published.

Verification follows the same line. A public record is useful when it can be traced to its source, whether that source is a community archive or an image archive, as in our note on checking satellite imagery sources.

What limits the exposure

Public access is a compromise by design: an open terminal is less private than a device you carry, and that trade is usually worth making. The sensible position is to keep the account you care about off the shared machine and to use one you can afford to lose. The free-net years are a reminder that access and accountability have to be designed together, not in sequence.