Reads and research atlas

This shelf turns the Excel research into reader-facing our pages. It is not a link dump. Every entry has a reason to exist, a route, an evidence trail and our interpretation.

How to use this shelf

This shelf contains 23 derived topic page(s). Use it when you know a name, app, relay, standard, tool or research source and want to see where it lives in the Crays Nostr map.

Some entries are mature products, some are infrastructure, some are experiments and some are reference material. The page does not pretend they are equal. It gives each one a findable place and a next step.

• Entries. 23
• Reader question. What story, evidence or outside framing helps a reader understand why Nostr matters beyond implementation details?
• Editorial rule. Only explain what the source trail supports. No filler, no hype padding.

Research entries

Open an entry for our interpretation and the source trail behind it.

HNHabla NewsLong-form / Reads and Nostr Reads. 1 source(s), 2 workbook signal(s). LFLong-form ContentActive and Publishing/reads. 2 source(s), 2 workbook signal(s). NCNostr.comNostr.com articles and Official. 1 source(s), 2 workbook signal(s). NCNostr.com Topics / ArticlesNostr.com articles and Official. 1 source(s), 2 workbook signal(s). AEAn Empirical Analysis of the Nostr Social NetworkResearch paper. 1 source(s), 2 workbook signal(s). HIHighlightsActive and Reads/annotations. 2 source(s), 2 workbook signal(s). LALyn Alden — The Power of NostrEssay. 1 source(s), 2 workbook signal(s). NBNo Bullshit Bitcoin — Primal v2.0Product/news. 1 source(s), 2 workbook signal(s). NCNostr CompassNews / newsletters. 1 source(s), 2 workbook signal(s). NRNostrium / read.nostr.comLong-form / Reads and Nostr Reads. 1 source(s), 2 workbook signal(s). PWPostr / write.nostr.comLong-form / Reads and Nostr Reads. 1 source(s), 2 workbook signal(s). BorisLong-form / Reads and Nostr Reads. 1 source(s), 2 workbook signal(s). FGForbes — Guide to NostrGuide. 1 source(s), 2 workbook signal(s). HNHacker News — Nostr discussionsDiscussion. 1 source(s), 2 workbook signal(s). NCNostr Compass NewslettersNews / newsletters. 1 source(s), 2 workbook signal(s). NCNostr Compass PodcastPodcast. 1 source(s), 2 workbook signal(s). NDNostr Design docsNostr design. 1 source(s), 2 workbook signal(s). NCNostr.com ExploreNostr.com explore. 1 source(s), 2 workbook signal(s). NCNostr.com indexed Primal Reads notePrimal / Reads. 1 source(s), 2 workbook signal(s). RRReddit r/nostrCommunity. 1 source(s), 2 workbook signal(s). SNSoapbox — Nostr 101Guide. 1 source(s), 2 workbook signal(s). TNThe Nostr BookProtocol books. 1 source(s), 2 workbook signal(s). WNWikipedia — NostrWikipedia / overview. 1 source(s), 2 workbook signal(s).

How to place Reads and research atlas on the map

Read Reads and research atlas as part of the Library route, not as an isolated entry. Its main surface is research and archive navigation: source maps, deep research, glossary entries, long reads, indexes, field guides and routes through the archive. That framing matters because a Nostr page is useful only when you can see which layer it belongs to and which layer it does not solve by itself.

The first question is practical: what changes for you if Reads and research atlas works well? Sometimes the answer is safer signing, sometimes better relay discovery, sometimes clearer media storage, sometimes a stronger source trail. Keep that question in front of you and the page becomes easier to judge.

• Layer. Library is the parent route, so the page should send you back to that shelf and sideways into adjacent concepts.
• Evidence. The current source trail starts with Crays Nostr deep research database, Nostr protocol repository, Nostr NIPs, Awesome Nostr. Treat those as anchors, then compare product behavior and NIP support.

What Reads and research atlas should help you decide

A good page about Reads and research atlas should leave you with a decision, not just recognition. You should know whether it is a protocol primitive, a client behavior, a relay operation, a product example, a research source or our implementation question. That distinction keeps the archive from becoming a flat glossary.

The common mistake is leaving the reader with a flat pile of links instead of a guided path through sources, concepts and examples. We avoid that by making the claim, the evidence and the next step visible. If a statement depends on a NIP, the page should point to that NIP. If it depends on a project, the page should show the project source. If it affects user safety, the page should say what can fail.

The working example behind Reads and research atlas

Use this page with a concrete mental test: a library page should tell you what kind of source you are looking at, what to trust, what to verify and where it fits in the wider map. That example is more useful than a generic definition because Nostr is not one product. The same signed event can be read by different clients, stored by different relays and interpreted through different product choices.

This is also why internal links matter. When the page mentions keys, clients, relays, events, zaps, Blossom, Cashu, FoundUPS or NIPs, those words should lead to the page that explains the concept more deeply. The goal is not to trap you in tabs; the goal is to let you move with context.

Source discipline for Reads and research atlas

The source list is part of the content, not decoration. For Reads and research atlas, use primary protocol documents first when the claim is technical, project repositories or product pages when the claim is about an app, and research or directory sources when the claim is about ecosystem position. If the sources disagree, the page should show the uncertainty instead of smoothing it away.

That source discipline is how a large archive stays trustworthy. It also helps learning: you get a short explanation first, then a route to the source that proves or complicates it. The page should feel like a guided chapter, but the evidence should still be close enough to inspect.

Before and after reading Reads and research atlas

Before reading Reads and research atlas, make sure you know the nearby base concepts: a public key identifies, a private key signs, relays carry signed events, clients render those events, and NIPs describe shared behavior. You do not need to memorize the whole protocol, but those pieces prevent most confusion.

After reading Reads and research atlas, the next useful move is to compare it with one neighboring page. If this is an app, compare it with a signer, relay or wallet page. If this is a NIP, compare it with the product behavior it enables. If this is a research source, compare it with the hub that uses it. That is how the archive becomes a learning path instead of a pile.

Why Reads and research atlas is not just a short note

Some pages look small because the object is small: a source entry, a micro-topic, a category shelf or a project reference. The page still needs a job. For Reads and research atlas, the job is to name the object clearly, place it in the right route, connect it to source evidence and give you the next reading step.

That is the difference between a database row and a useful knowledge node. A database row stores a fact. A knowledge node explains what the fact connects to, what it does not prove and why you might open the next page.

The navigation job of Reads and research atlas

Reads and research atlas also has a navigation job. It should help you decide whether to move upward to the Library hub, sideways to a related concept, or downward into a more technical source. That sounds simple, but it is the difference between browsing and learning.

When a page does that job well, you do not need to keep the whole archive in your head. The page carries enough context to orient you, enough links to continue, and enough source discipline to show where the claims come from.