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.

The free-net lesson is that a shared protocol matters more than any single node. A community network works because everyone agrees on how to hand off traffic, and the same holds in the air: a tanker and its receiver must agree on the method before they meet. That is the subject of a new page on tanker refueling operations, covering how fuel moves in flight, boom versus probe-and-drogue, fleet composition, mission planning and standardisation. The parallel is not decorative. Both depend on published rules, practised crews and the discipline to follow the procedure when conditions change.

The free-net years also left a habit worth keeping: when a shared resource fails, someone traces the signal path instead of guessing. That habit scales. A community access point, a repeater, or a microwave link all depend on components that must pass or block a signal cleanly, and the same questions apply at every level: what is isolated, what is lost, and what drives the switch. A short technical note on solid-state PIN switch topologies covers reflective and absorptive designs, isolation, insertion loss, and driver circuits. It is a useful reminder that public access rests on hardware someone still has to understand.

The free-net terminals were shared machines, and the habits they taught still apply to any computer you do not fully control. Keep your own tools small, portable, and documented. That same discipline carries into personal hardware: on a Mac, pick a database client you can explain to someone else, understand what a shareware tool such as SyBrowser actually did before you install it, and schedule recurring tasks so they run without your attention. These are ordinary maintenance decisions, not endorsements, and they reward the same caution the public access years demanded. A short guide to Mac database software covers the choices and the trade-offs.

The free-net years also left a practical lesson about reuse. Community groups often wanted to illustrate a page or a talk with moving images, and they learned to ask where a clip came from and what its terms allowed. That habit still matters. Before you drop a shot into an edit, check whether it is royalty free and rights managed footage, because the two carry different permissions, costs, and limits on b-roll use. Old film can supply texture that new stock cannot, but only if the licence is clear. Read the terms first, then cut.

The free nets also left a practical lesson about coverage. A community that can see its own streets, roofs, and lots does not have to wait for a distant map to be corrected. The same instinct now reaches lower: a page on tethered balloon photography covers platforms flown between thirty and five hundred feet, with notes on architecture and construction uses and the US rules that apply. It is a modest altitude, close to the ground people actually argue about. That is where public access starts, with a view you can check yourself.

The free-net lesson was never about the software. It was about matching a tool to the work people actually do, then explaining the cost in plain terms. That habit still pays off. Breeders and kennel operators face the same problem: a crowded set of platforms, unclear fees, and advice written for someone else's business. A page on kennel pricing and offers applies the same discipline, laying out what each option costs, what an online presence should carry, and how to pick tools that fit the daily routine rather than the demo.

The free-net lesson is that access works when a small group owns the equipment, learns the rules, and keeps the thing running week after week. That pattern repeats in low-power FM. A community can apply for a license, build a modest transmitter, and put local voices on the air, but only if someone reads the FCC rules and stays with the paperwork. The new page on starting a community radio station walks through licensing, day-to-day operation, and the practical limits of a small signal. Read it before you assume the hard part is the tower.

Free nets ran on grants, donations, and volunteer time, and that mix has limits. When a community network decides to incorporate, or when a small security shop grows past its founders, the money question arrives fast. The options are not mysterious, but they are easy to get wrong: debt versus equity, SAFEs and priced rounds, and public programs such as SBA, SBIC, SBIR, and STTR. Each has different paperwork, timelines, and obligations. Reading up before a lawyer or an accountant is in the room saves money and keeps the mission in view.

The free-net lesson is that access without procedure is just noise. A community can open a door, but people still need to know what happens after they walk through it. The same holds for disputes that start offline and end up in court. For readers who want that procedural picture without a law degree, a-sap.org now explains how a civil case moves, covering remedies and damages, filing limits, and the business, insurance, and employment disputes that fill county dockets. Knowing the steps does not replace a lawyer. It does make the system legible to the people it touches.