Week 2: Lurking as method

Every community runs on rules that are written down and rules that are not, and the gap between them is where newcomers are lost

1 March 2027

A subreddit’s sidebar has eight rules. Its moderators enforce about thirty. The other twenty-two are real, consistently applied, and discoverable only by watching what gets removed — which is to say, discoverable only by reading the record of other people’s mistakes.

This is not a failure of documentation. Some of the twenty-two are too embarrassing to write down. Some are contested inside the mod team. Some were never articulated at all, and exist as a shared instinct about what this place is for, which is precisely the thing a written rule cannot hold.

Anthropologists have a word for the method that recovers them, and it is not a word that makes the practice sound as passive as it looks from outside. Lurking, done properly, is fieldwork: you read the modlog, you read the deleted contributions, you read the talk-page archives, and you build a description of the norms that the community itself could not have given you.

You do this before you post. Every contributor who ever complained that a community was hostile to newcomers skipped this step, and some of them were right anyway.

Outline#

• written rules, enforced rules, and the delta
• where the public record actually lives: modlogs, deletion logs, talk archives, closed pull requests
• reading a removal for the rule behind it
• legitimate peripheral participation, and why the reading is the joining
• the limits: what lurking cannot tell you, and when to just ask