Spoilers and etiquette

Why the rules are unwritten

Geocaching has guidelines about placement, permission and cache types. It has almost nothing formal about how cachers should behave toward each other.

That gap is not an oversight. The things that matter between cachers: what you photograph, what you write, what you give away, how long you keep a trackable, are matters of judgement that resist being codified. A rule precise enough to enforce would be either trivially avoidable or absurdly restrictive.

What fills the gap is social: people notice, people say something, and most people would rather not be the one who spoiled it. In a community with no membership, no fees and no authority, mild disapproval turns out to be a functioning regulator.

Spoilers

The clearest case is a photograph of the container in position. It is worse than a written description for two reasons: it cannot be partially absorbed, and it persists on the listing where every future finder sees it whether they wanted to or not.

The second case is a log that describes the hide. “Nice one, would never have thought to look under the third fence post” is well meant and completely destructive.

The third is subtler: a photograph of the place taken from an angle that identifies the container’s surroundings precisely. The intent was the view; the effect is a map.

The test is simple and worth applying before posting: could somebody find this without searching, on the strength of what I have just published? If yes, it is a spoiler regardless of what you meant.

What a good log contains

The default log is four letters and it is a small waste.

Owners read their logs (sometimes years later, often as the only feedback a cache ever gets) and a log with something in it is worth having.

Useful things to include: whether the coordinates were accurate and by how much they were off; the state of the container, the log and the seal; what the walk was like; whether anything has changed since the listing was written; something you noticed at the place.

None of that spoils anything. All of it helps the owner maintain the cache and helps the next person decide whether to go.

The rule of thumb: write the log you would have wanted to read before you set off.

Hints

Hints are for people who are in the right place and cannot see it. A hint that repeats the coordinates is not a hint, and a hint that says “you’ll know it when you see it” is worse.

The encryption convention exists precisely so that a hint can be specific without being unavoidable — you have to decide to read it. That is a small, elegant piece of design, and it works only if owners put something worth decoding in there.

Trackables, briefly

The etiquette that gets broken most often is not about spoilers at all. It is holding a trackable too long, which is covered in the trackables section.

It belongs here too, because the mechanism is identical: no rule, no enforcement, and a small obligation to a stranger that only works if most people honour it most of the time.

Photographs are the hard case

Written spoilers can be edited. A photograph cannot be partially unseen, and it sits on the listing where every future finder meets it before they have decided whether they wanted the help.

The safe frame is one that shows the place without showing the container’s surroundings closely enough to locate it. The view from the site, the walk in, the thing that made the spot worth choosing — all of those are welcome and make the listing better.

Why the unwritten rules are enforced so gently

An outsider reading the community’s arguments would expect a formal code, and there is not one. What exists instead is a set of expectations enforced almost entirely by mild social pressure, a comment in a log, a note from an owner, a thread that goes quiet.

The reason is structural. Nearly everything a cacher does happens alone, unobserved, at a container in a hedge. There is no mechanism by which anybody could enforce anything, and the community knows it. What is left is the expectation that people will behave well because the whole arrangement collapses if they do not: and, remarkably, it mostly holds.

That fragility explains the tone of the arguments. When cachers get sharp about spoilers or trackables or a badly replaced container, the sharpness is not really about the individual instance. It is about a set of norms that has no enforcement and therefore depends entirely on people continuing to take it seriously.

Where the etiquette is genuinely contested

Most of this page describes settled expectations. Three areas are not settled, and it is more useful to say so than to pretend a consensus exists.

How much a log may describe. The line between a useful account of the walk and a description that removes the search is drawn differently by different people, and both positions are held sincerely.

Whether hints should be needed at all. Some owners regard a cache that requires the hint as under-described; others regard the hint as part of the design and expect it to be used.

What to do about a cache you believe is bad. Say nothing and it persists; say something and you are criticising somebody’s work in public, permanently, in a log they cannot remove.

Nobody is going to resolve these, and a page claiming otherwise would be describing a community that does not exist.