FIDONET GOVERNANCE AND POLICY

The Governance Problem

FidoNet grew from Tom Jennings's two-node experiment in 1984 to a global network of tens of thousands of nodes within a decade. That growth created a governance problem that technology alone could not solve: how do you coordinate thousands of independent system operators across dozens of countries, spanning multiple time zones, without a company, a budget, or enforcement authority?

The answer was Policy 4.

FidoNet Policy 4

FidoNet Policy 4, ratified in 1989, is the foundational governance document of the FidoNet network. Before Policy 4, FidoNet operated on informal agreements and the personal authority of Tom Jennings. Policy 4 replaced that with a written framework covering:

• The network's hierarchical structure and the roles within it
• The rights and responsibilities of each level of the hierarchy
• The rules governing node membership, disputes, and removal
• Standards for conduct expected of FidoNet participants
• The authority of coordinators and the limits of that authority

Policy 4 was significant not because it solved FidoNet's governance challenges — it never fully did — but because it made the governance framework explicit. Arguments about what was and was not permitted could now reference a document rather than relying on precedent and the memory of long-term participants.

The policy remains controversial in retrospect. Critics argued it created a bureaucracy at odds with FidoNet's origins as a voluntarily connected community of hobbyists. Supporters maintained it was the minimum structure necessary to keep a global volunteer network functional. The tension between these positions defined much of FidoNet's internal politics through the 1990s and beyond.

Zone Mail Hour (ZMH)

One of FidoNet's key coordination mechanisms is Zone Mail Hour (ZMH): a designated window during which all FidoNet nodes are expected to leave their lines available to receive incoming mail.

During Zone Mail Hour, a node should not be accepting user calls. It should be answering incoming mailer calls and receiving whatever netmail or echomail other nodes are trying to deliver. This ensures every node on the network has a predictable receive window — you can schedule outbound mail deliveries knowing the destination node will be accepting calls.

Zone Mail Hour timing varies by zone. For Zone 1 (North America), the historical ZMH is 0900–1000 Eastern Standard Time. Other zones define their own windows according to local convention.

The concept arose directly from FidoNet's dial-up architecture. If your node was constantly busy with user calls, other nodes could never deliver mail to you. Zone Mail Hour was the social contract — backed by Policy 4 — that kept the mail flowing.

The Network Hierarchy

FidoNet's structure is hierarchical:

International Coordinator (IC)
└── Zone Coordinator (ZC) — one per zone (1–6)
    └── Regional Coordinator (RC)
        └── Net Coordinator (NC)
            └── Hub Host
                └── Node
                    └── Point (not in the nodelist)

Each level is responsible for the nodes below it within their region. Net Coordinators manage the nodelist entries for their net segment, compile the net nodelist, and maintain routing for their area. Zone Coordinators compile zone-level nodelists. The International Coordinator compiles the master nodelist from zone contributions.

This structure allowed FidoNet to function without central servers. The nodelist was compiled, distributed to every node, and each node used it to calculate its own routing. No central routing authority was needed at runtime — the intelligence was in the nodelist.