Culture
The unwritten rules of the message bases
Handles, introductions, upload/download ratios, and why the SysOp really did mean it.
PLEASE READ THE BULLETINS
╚══════════════════════════╝
A BBS was not simply a collection of files. It was a community with expectations, and on a small board those expectations could be quite personal. You were using a machine that somebody owned, a telephone line somebody paid for and a shared space where regular callers recognized one another. Good etiquette mattered.
Read the welcome bulletins
Many systems displayed announcements and rules before the main menu. They might specify acceptable content, forbidden uploads, message-area purposes, calling hours and time limits. Ignoring them was a quick way to attract the SysOp's attention. So was repeatedly asking a question answered in the first screen.
Respect the clock and the phone line
Single-line boards generally could not take a second call while someone was connected. A daily limit spread access across the community. Callers learned to prepare messages offline or compose efficiently rather than tie up the system thinking of what to say.
Make your messages worth reading
Unlike instant chat, BBS messages were often read hours or days after posting. It helped to write a descriptive subject, quote only what was relevant, distinguish fact from opinion and resist posting the same text to every conference. A useful answer to a novice's technical question could become a reference people consulted for months.
The handle and the human behind it
Pseudonyms were common on hobby systems, but they did not make reputation unimportant. A recognizable handle accumulated goodwill or irritation over time. Some SysOps required verified real names for registration while allowing handles on screen; others favored complete anonymity. Neither approach removed the need to treat other callers as people.
Uploads came with responsibility
A good upload had an accurate filename, useful description and permission to redistribute. On a file-heavy board, a malicious or broken upload could cause real trouble. Many SysOps reviewed files or scanned for malware, but callers still carried responsibility for the material they shared.
When a SysOp told everyone not to call during a scheduled maintenance or mail window, they really meant it. Some BBSs used specific intervals for their FidoNet links, backups or other housekeeping.
The rule that still applies
Appreciate the labour behind the platform. If you enjoyed a board, offer useful advice, contribute a file you could legally share, welcome a new caller or simply thank its operator. That spirit is as relevant to modern online communities as it was to a PC and modem in a spare bedroom.