The whole shelf lives here: source audits, deep research, app maps, NIP references, field guides, long reads and the routes that keep a huge archive actually usable.
Crays research map for nostrapps.com: pages, headings and links used to understand the Nostr ecosystem.
This research page documents what the crawler found on nostrapps.com. It is not copied material; it is a working map for the Crays editors.
The quick readCrays research map for nostrapps.com: pages, headings and links used to understand the Nostr ecosystem.
The library is the map readers use when curiosity gets serious.Deep content needs routes, scenes and memory hooks.
What was captured
The crawler captured 74 reachable pages from nostrapps.com. For each page it stored the URL, page title, description, visible headings and link graph. This gives the archive a concrete working map instead of vague claims.
In the source-inventory / nostrapps-com chapter, This map keeps the Crays Nostr work maintainable. If tomorrow's chat needs to continue the work, this page and the JSON inventory show what was already reviewed.
Domain. nostrapps.com
Captured pages. 74
Use. Research map, editorial backlog and QA evidence.
Captured pages
The cards below link to the original public pages. The archive uses them as working material, then writes independent our explanations for readers.
Research Map: nostrapps.com belongs to the research and source material layer. The page should help you answer one concrete question instead of forcing you through a generic Nostr essay.
The short version is: Crays research map for nostrapps.com: pages, headings and links used to understand the Nostr ecosystem. The deeper version is to see which concept, standard, product surface or human decision actually changes because of it.
Evidence quality
The useful machinery around Research Map: nostrapps.com is taxonomy, internal links, search paths, topic clusters and update discipline. Name those moving parts directly, because vague protocol language is where confusion starts.
In the source-inventory / nostrapps-com chapter, A strong page gives you enough context to recognize the term in another client, NIP, relay policy, wallet prompt or source document without pretending every reader is already a protocol engineer.
Source type. Standard, repo, monitor, directory, essay or research paper?
Claim. What claim does this source support?
Next use. Which article should absorb the insight?
The full archive should feel organized enough to browse for hours.Every branch of the atlas should still feel connected to real work.
What it can verify
Test Research Map: nostrapps.com by asking what is signed, where it is stored, who renders it, which relays or services are involved and what survives when the first app or server is unavailable.
In the source-inventory / nostrapps-com chapter, That test keeps the explanation tied to reality. It also tells us which internal links belong in the body: foundations first, then standards, then practical examples.
What it does not prove
In the source-inventory / nostrapps-com chapter, The main risk is that a large archive becomes useless if it is only a pile of names and links. The page should say that plainly and then show the safer reading: what works today, what is experimental and what needs source verification.
In the source-inventory / nostrapps-com chapter, This is where dense content beats long content. Give the reader facts, constraints, examples and next steps instead of repeating broad claims about openness or decentralization.
Where the knowledge should feed
For us, Research Map: nostrapps.com matters only when it improves understanding or helps a real flow: identity, publishing, relay choice, signing, payment, media, moderation, commerce, venue context or governance.
In the source-inventory / nostrapps-com chapter, That does not mean every page has to become our product pitch. It means the page should make the connection visible when the topic affects our ecosystem, and stay purely educational when it does not.
Library path around it
The best next step from Research Map: nostrapps.com is not a generic link pile. Connect it to the closest prerequisite, the closest technical standard and the closest practical example.
In the source-inventory / nostrapps-com chapter, A large archive becomes useful when every page behaves like a node in a knowledge graph: this explains one thing, points to what it depends on and shows where the idea is used.
Complete Nostr Apps CatalogApps and clients
NIP-07: Browser SignersProtocol and NIPs