Skip to content
The Local Loopcommunity networks journal

Network History

What Signing Up for a Free-Net Involved

How registration worked on a 1990s free-net: the form, the volunteer review, the login name and the first dial-up session.

A paper registration form on a desk beside a telephone and an external modem with a coiled cable.
A paper registration form on a desk beside a telephone and an external modem with a coiled cable.

This address has a history. In the 1990s, the path /info/registration-info.html on ghofn.org was the page that explained how to join the Greater Houston Free-Net, the community system documented in its own guide. This restored page describes how registration typically worked on a free-net of that era, drawn from the systems whose procedures survive in the record.

The registration desk was a web page

Joining a free-net began with information, not software. A prospective member found the registration page, read what the system offered and what it asked, and started there. The page did the work a membership desk would do at a library or a club: it set expectations, listed the rules and explained what happened after the form.

On most systems the promise was the same. An account cost nothing, granted email and discussion access, and existed so that local residents could reach community information and, increasingly, the wider internet.

What the form asked

The typical form was short by modern standards. It asked for a name, a postal address and a telephone number, plus a requested login name, usually the member's initials or a short handle that would become the part before the at sign in their email address. Some systems asked how the member heard about the service or what equipment they had, which told the volunteers which modem speeds and terminal types to expect.

Identification mattered more than it might seem. Because accounts could post to public forums, many systems wanted a real name behind each one, and a few verified identity by postcard or by phone before activating full access.

Visitor access versus a registered account

Most systems split access in two. A visitor login, often a shared guest account, let anyone look around immediately with limited features: read the information sections, browse the calendar, see what the system was. A registered account unlocked the rest: a personal mailbox, posting rights in discussion groups, longer sessions and, on many systems, outgoing access to internet services like telnet, Gopher or early web browsing.

The split served a purpose beyond security. Modem lines were scarce, and the visitor account let the curious look without consuming a registration slot the volunteers would have to process.

What happened after the form?

Behind the page sat a manual process. A volunteer or staff member reviewed applications, checked that the requested login was free, created the account and sent back the credentials, sometimes by email to an existing address, sometimes by post or phone. Turnaround ran from hours to days depending on the volunteer queue.

Then came the first session: dial the number, log in, accept the usage terms, and arrive at a main menu organized like a town. New members were pointed at the help desk and the frequently asked questions page, the same sections that appear on the Greater Houston system's archived menu.

Time limits and fair use

Free did not mean unlimited. Systems typically limited session length or daily minutes so that the modem pool could serve everyone; some logged off heavy users during peak hours and allowed longer sessions late at night. Posting privileges came with conduct rules, and accounts could be suspended for abuse. The tone of these rules was closer to a library's conduct policy than a commercial contract.

The help desk behind it all

Every free-net rested on volunteers who answered the questions the form could not: forgotten passwords, garbled terminal settings, modems that would not connect. The help desk was usually an email address or a phone line staffed part-time. It was the most human part of the system, and the first thing that disappeared when a system could no longer recruit volunteers.

What the account actually opened

It is worth being concrete about what a new member received. An email address on the system's host, readable through the menu or a mail program. Access to discussion areas organized by interest, from local politics to hobbies. Entry to the information sections the information providers maintained. On systems with internet connections, a gateway out to services beyond the local machine. And on some systems, space for a personal page, which for many members was a first act of publishing rather than reading.

Why registration asked so much

Modern readers sometimes find the process heavy for a free service, and the era had its reasons. Modem capacity was finite, so each account represented a real share of a scarce resource. Public posting meant the system carried responsibility for what members wrote, which made identity worth a verification step. And the volunteers processing applications were doing it by hand, one form at a time, which kept the process deliberate. The friction was not a defect of the system; it was the visible price of a resource that belonged to everyone.

The modern equivalent

The closest living relative of free-net registration is the public library card sign-up, often now followed by a hotspot loan or a computer card, a process covered in the library access guide. Community networks covered in Community Builds run their own versions: a short form, a volunteer install, a first login. The paperwork shrank, but the structure of joining a community network has changed remarkably little.

It is also a reminder that access was once granted person by person, form by form, by volunteers who knew most of the membership by name. The scale has changed; the question of who verifies, who decides and who helps has not.