How to Follow the People Map Without Getting Lost

Do not read the directory like a phone book

A raw list of names is not a map. It gives the appearance of completeness while leaving the reader alone with the hardest question: why does this person matter? The People route becomes useful only when it begins with roles. Builder. Client maker. Relay operator. Creator. Educator. Funder. Event host. Critic. Standards author. Early user. Once the role is clear, a profile can carry meaning.

This is why the hub starts with community themes instead of dumping every profile first. A reader can enter through the public square, builders, creators, events, zaps, trust, funding or migration. The name list is still there, but it no longer has to explain itself.

Follow the public evidence sideways

A People page often makes more sense after the reader opens another route. A builder profile may need an Apps page, a NIPs page and a GitHub repository. A funder profile may need Commerce and grant pages. A creator profile may need Media, Wavlake, live streams or podcasts. A relay operator may need the Relays hub. A privacy educator may need the Basics and Privacy routes. People are not isolated entries.

The best reading path moves sideways. Name, role, source, product, standard, event, next person. That movement turns the archive into a living map rather than a pile of biographies.

Depth follows evidence

Some people deserve long portraits because the public record is rich: projects, talks, writing, funding, code, controversies and influence. Others need shorter but precise entries because the public evidence is narrower. That is not a quality failure. It is honest proportion. The article length has to follow the evidence, not the desire to make every page look equally important.

The archive loses trust when it pads thin pages. It gains trust when it says what is known, links to the evidence and stops before speculation.

A large people map should feel like reporting, not a spreadsheet

A 100-plus-page People route can become impressive and useless at the same time. The fix is not to hide the size. The fix is to give the reader story paths. Open the public square when the question is culture. Open builders when the question is work. Open zaps when the question is money. Open funding when the question is who pays. Open events when the question is where the room becomes real. Open client makers when the first impression matters.

The archive should feel like reporting because Nostr itself is a living scene. Companies raise money. Open-source builders receive grants. App-store rules change product design. Conferences create shared memory. Pseudonymous maintainers become trusted. Media people bring outsiders in. Relays quietly decide whether the room works. A static directory cannot carry that story by itself.

The People map is useful when it helps the reader choose which pressure to follow.

Public evidence keeps the map honest without making it dry

The source list is not there to make the page look academic. It is there to keep the story honest. A Forbes funding article, an OpenSats grant page, a GitHub repository, a conference speaker page, a LinkedIn public note, a podcast episode, a Nostr profile and a project homepage are different kinds of evidence. A good article lets the reader know which kind is doing the work.

This matters because Nostr attracts myth quickly. A small protocol can turn public names into legends before the public record catches up. The archive has to do the opposite: tell the story vividly, then show where the story can be opened. That is how it stays human without becoming hype.

The map should make the reader more curious and more careful at the same time.

The map has to stay alive

Nostr changes quickly. Builders leave projects. Clients change direction. Grants get announced. Events happen. Relays vanish. New creators arrive. Old claims go stale. A People map has to keep moving without showing its maintenance work to the reader as messy internal notes. The public page needs finished context, not visible editorial scaffolding.

A living map is not an excuse for weak writing. It is a commitment to update the story when the community changes.