How internet communities change: a reading framework

Internet communities are a bet that a group of strangers can be made to behave like neighbors. Some bets hold; others do not. The interesting question is not which software they ran but what changed between the day the place felt alive and the day it did not.

This page describes the parts a community is made of, the sequence most of them pass through, and the questions to ask before trusting anything written about one, including this.

What to take away

The parts

A population that returns. Traffic is not a community. A page can have enormous numbers of readers and no community at all, because nobody comes back and nobody recognizes anybody. The threshold is recognition: enough of the same people appearing often enough that a name means something. Online community is the general term, and it is a term about people, not about a site.

Norms. What gets you thanked, what gets you ignored, what gets you removed. The norms are mostly unwritten, learned by watching, and different from the rules page in ways that only members can see.

Enforcement. Someone, or some mechanism, that makes the norms bite. This can be a moderator with a ban button, a voting system, a reputation score, or plain social pressure. Every community has one of these, including the ones that insist they do not; the enforcement there is informal, and informal enforcement is usually harsher.

A container. The forum, the chat server, the mailing list, the group. It is the part people name when they name the community, and it is the part most easily swapped out. Communities move containers and survive. Containers lose their community and become empty rooms with the lights on.

The sequence

The stages below are a way to read community histories, not a claim that every community follows the same sequence. They have no fixed timing, and this article does not assign a duration to any stage.

The wave is the stage most written about, because it produces the most visible complaints. An argument about purpose can decide what happens next. A split is easy to miss: a community may move, in smaller form, while the surviving record shows only the abandoned container.

The wave, dated: Usenet's Eternal September

One wave is documented well enough to read against the table, because it happened to a whole container rather than to one community. During the 1980s and early 1990s, new Usenet users joined slowly and in small numbers and learned the conventions without much impact on experienced users; that is the good period. The one exception was every September, when large numbers of first-year university students from North America gained access through their campuses, and each year the tide abated as newcomers assimilated or left.

Then the arrival rate changed for good. Once internet service providers began offering Usenet access to many new users, from around late 1993 and early 1994, the flood of inexperienced users swamped the existing culture of those forums and their ability to self-moderate and enforce existing norms. AOL began its Usenet gateway service in March 1994, which produced a constant stream of new users. To early users the influx that began in September 1993 seemed endless, and the period got its name: the September that never ended.

Every element of the wave stage is there: an arrival rate that outran teaching by example, irritable old members, and norms that could no longer be enforced informally. It also shows why exact dates mislead. The change is placed variously in September 1993, late 1993 to early 1994, and March 1994, depending on which event a writer counts.

Why the rules page is a history book

A community's written rules are a list of things that went wrong once. Each rule marks an argument that somebody lost badly enough for the outcome to be written down. Reading the rules therefore tells you the community's past conflicts in some detail and its present character hardly at all.

The present character lives in three places a newcomer cannot see on the first day:

Containers and what they decide

The container is not neutral. It decides how conversation is shaped, and a community that moves containers changes in ways its members rarely anticipate.

A threaded forum keeps every discussion findable and lets a slow conversation continue for years. It rewards careful writing and punishes speed. The Usenet newsgroups were built this way, and the web forums that followed kept the shape.

A live chat room is the reverse: it rewards presence and wit, produces nothing findable, and a member offline for a day has missed everything. IRC servers are the long-running example, and Discord servers are the current one.

A mailing list sits between the two. It adds a property neither has: every member holds a complete copy of the record. Listserv and Mailman are the usual software behind it.

Feed-based containers, where a community exists as a group inside a larger service — a subreddit inside Reddit, a group inside Facebook, a server inside Discord — add a different force: the host decides what members see, in what order, and can change that without asking. Communities living in these containers are borrowing the room, and the landlord's interests are not theirs.

The distinction between a community and its container is the same one that separates a social network from the systems that came before it; the guide to reading early social networks takes that apart in detail.

Reading anything written about a community

Where the private ones went

Public communities left the best records, because a public archive can be crawled and copied.

Private ones, which include most of the small and most of the intimate, left almost nothing.

A history of internet culture built from archives will describe the large and the public, then wrongly conclude that this is what community online mostly was.

Nothing corrects that bias except remembering it. The absence of a record is the normal condition for most of what happened, not evidence that it did not.

Common questions

Is a large audience the same as a large community?

No. Audience is people who read. Community is people who return, recognize each other and are recognized. A place can have the first in huge numbers and the second not at all.

Why do communities get worse as they grow?

They do not always, but the common mechanism is simple: norms are taught by example, and example only works when newcomers are few enough to watch before they post. Past a certain arrival rate, teaching by example fails and the community has to choose between written rules and drift.

Can a community survive its container closing?

Sometimes, if the members knew each other well enough to find each other again, and usually in smaller form. The archive almost never survives, which is why so much community history is memory rather than record.

Why does this page not name any examples?

A named community would require claims about its founding, size and sequence. The containers named above — Usenet newsgroups, IRC, mailing lists, subreddits, Discord servers — are types, not case studies. This page stays with the reading framework rather than making claims about a particular community without contemporary evidence. The one dated event it uses, Eternal September, is a documented change across Usenet as a whole rather than a claim about any single community's founding or size.