Research Source: Groups NIP-29

Groups NIP-29 is part of the Crays Nostr deep research database. This page turns the workbook entry and live source audit into a readable archive chapter.

What this source adds

Groups NIP-29 belongs in the Crays Nostr archive because the workbook places it in Clients & Apps, with the subcategory Chat / Groups. That already tells us the role: this is not random web noise, it is a mapped source inside the larger Nostr research base.

The useful information to carry forward is this: NIP-29 groups UI/directory. The Crays job is to translate that signal into a reader-friendly explanation, not to throw another raw URL at someone who is trying to understand the scene.

During the audit the source was reachable during audit, HTTP 200. Where the live page did not expose clean metadata, the workbook context remains the editorial anchor.

A standards source is where builders agree on shape. Crays should translate that into what changes for people: what becomes portable, what becomes safer, what becomes more searchable, what becomes payable and what still depends on client support. The important line is this: NIPs are not product guarantees. They are agreements that make product behavior possible. That distinction keeps the writing honest.

• Category. Clients & Apps
• Subcategory. Chat / Groups
• Importance. High

Where it sits in the Nostr map

This source sits in the standards and nips route. These sources define or explain the shared conventions that let independent Nostr apps understand each other.

The captured structure points toward no readable heading structure captured. That does not mean Crays copies those headings. It means the page gives us clues about how the ecosystem itself explains the topic, which Crays then rewrites into a cleaner, more human chapter.

The live audit found 0 readable paragraph signal(s). They are used only as research evidence; the public Crays copy stays original, traceable and written in the same voice as the rest of the atlas.

What Crays should carry forward

The archive should pull the lesson out of the source and place it where a reader expects it: standards in the NIP path, products in the app path, relays in the infrastructure path, research in the library, and Crays-specific meaning in the product layer.

The language has to stay calm and alive. A reader should feel guided by someone who knows the protocol and also remembers that most people do not wake up wanting to read implementation notes.

• Keep. The concrete ecosystem fact, product pattern or standards signal from the source.
• Translate. Turn technical or directory language into Crays' plain, cool, explanatory Sachbuch voice.
• Place. Connect the source to the right atlas route so it can be found logically later.

Workbook evidence

This page is backed by 2 workbook reference row(s). That matters because the same URL can appear in several research sheets and carry slightly different editorial meaning.

Link Directory row 185Clients & Apps: Groups NIP-29 Clients Apps row 67Clients & Apps: Groups NIP-29

Subpages checked

The audit checked 0 same-site subpage(s) for this source where the domain and crawl rules made that useful. These subpages are treated as research evidence, not as imported copy.

No useful subpage crawlThe URL itself was checked, but no relevant same-site subpage was captured for this source.

Reader takeaway

If you are reading the Crays Nostr archive, the practical takeaway is simple: Groups NIP-29 is one source in the wider standards and nips map. Use it to understand the ecosystem signal, then use the Crays chapter links to see how that signal fits identity, apps, relays, payments, creators, venues and governance.

That is the standard for this whole database: no loose bookmark dump, no protocol fog, no lonely expert reference that only makes sense if you already know the answer.