Summary

  • Wellington City Council opened part of City Net to the public on 1 January 1992, offering dial-up users email, Usenet, chat, Internet file access and council information.
  • By April 1993, Richard Naylor reported about 1,200 registered users, while registration delays and connection difficulty already constrained the service.
  • A dated Gopher menu independently shows council by-laws, committee papers and election results, but the surviving records do not prove that Gopher and City Net were one system or that every listed item was retrieved.

The most revealing line in Wellington City Council’s early Internet history is not a claim to be first. It is a practical admission: staff needed convincing that the small effort of putting council information online was worthwhile.

In April 1993, Richard Naylor, the council’s Computer Services manager, described City Net as a public trial that had begun on 1 January 1992. Residents could dial into part of the council’s computing system and use electronic mail, the council’s NOTES bulletin board, Usenet news, Internet chat, file copying and databases. The arrangement did not begin as a polished civic portal. It grew out of computers and a data circuit the council already used for work.

A separate view survives in a 1993 conference paper by Steve Cisler. Its Gopher screenshot is dated 28 November 1992. Under a Wellington City Council menu, it lists by-laws alongside CityNet, committee papers, a meeting timetable, election results and policy. That menu shows civic records being organized for readers on the Internet. It does not show precisely how each item was fetched, or prove that the Gopher server and the dial-up service shared one interface.

Two paths through municipal computing

Naylor’s account describes City Net as a place a resident reached by modem. Its NOTES area held the Transitional District Scheme and the by-laws. The system also carried routine public notices, library book listings, event information, facts about the city and New Zealand, email, discussion and file-transfer services.

Gopher offered a different route. The protocol, described in RFC 1436 in March 1993, let a reader move through menus while documents could remain on separate servers. The Wellington screenshot makes the council’s information appear as a navigable Internet menu, available beyond the users who dialed the council directly. It is a snapshot of organization, not a usage log.

This distinction matters. City Net was a public-access system with local services and Internet functions. The Gopher menu exposed council material through the wider network. They belonged to the same civic computing effort, but the available record does not establish that one was simply another name for the other.

The records also complicate the word “free.” Naylor said basic access would remain free and that the public called the council, so the council incurred no telephone charges. Yet the service used a computer doing other municipal work and a data circuit to Victoria University that the council paid for. Public access was a by-product of that work, not a costless network.

A document could travel farther than its office

The council posted the Transitional District Scheme and by-laws in NOTES. The Gopher screenshot separately lists by-laws and policy under the council menu. That made local rules reachable without asking an office to mail a paper copy. Naylor also described monthly information postings, including notices, event listings and library material. Readers abroad sometimes requested email delivery because the ordinary news cycle took three or four days.

This was not automatic transparency. Naylor said staff still had to be persuaded to make council documents available. The technical system could carry a file, but each division had to prepare and release it. The same paper says council minutes and reports had been tried, while broader publication remained an educational task for the public and an organizational task for staff.

A February 1993 Usenet directory gives the dial-up service a less ceremonial portrait. It lists CityNET as a general-audience system, with a Wellington phone number, registration requirement, VAX menus, Usenet, email, FTP and Telnet. The compiler notes congestion on a single line, with at least seven modems stepping on it. The listing is not a council performance report, but it shows that availability could be harder than the menu suggested.

The ceiling was organizational as well as technical

Naylor counted about 1,200 users in April 1993, with roughly 100 more joining each month. He identified registration processing as the largest bottleneck and noted that some people had trouble connecting, depending on how they accessed the system. Those figures count registered users, not active sessions, households or successful calls.

The economics were unusually local. The computer served other council work; the Internet circuit already served daily business; and staff time was described as minimal. Naylor said the council registered users and encouraged them to help one another. That arrangement made an experiment possible without building a separate consumer network, but it also tied access to spare capacity, limited modem lines and a human registration queue.

The expansion plan exposed another boundary. Public terminals in branch libraries were considered as a way to reach people without home modems, but funding constraints delayed the work. Access to the public library catalogue was also blocked by legal questions. Meanwhile, Naylor said clearly commercial information might eventually carry a charge, while basic services would stay free. These were proposals and constraints in a 1993 account, not proof of later policy or implementation.

The surviving sources therefore support a grounded conclusion. Wellington made a municipal computer system useful to residents and used Internet menus to distribute civic records. It did so by reusing infrastructure and organizing staff work, not by eliminating the costs of access. The system’s reach depended on who knew to register, whether a line was free, whether a modem could connect and whether the relevant council office had prepared its information.

Heng Lu’s Note 65, “Running-Code Primacy,” informs one narrow editorial test here: separate what the record shows operating from what an institution says it may do next. On that test, the public trial, listed services, Gopher menu and user count are evidence. Branch-library terminals and future commercial charges remained plans in the cited account.

Sources