Build the Nostr knowledge graph with the people who use it
This is the product layer around the archive: questions, projects, people nominations, source review, relay reports, NIP debates and moderator decisions. The content stays stable; the community makes it alive.
1436indexed pagesThe editorial archive remains the base layer.
15community lanesTopic communities mapped to the 12 Crays routes.
64people seedsEarly Nostr Users from the handover screenshots.
0server-held keysPrivate keys stay with signers or local account flows.
Contribute to CraysChoose what you are adding. The event is signed locally and goes to review before it changes editorial content.
18
QuestionUnansweredPrivacy & Keys
Which signer path should a new Crays reader start with?
A newcomer wants a safe route between extension login, Nostr Connect, read-only npub and local account creation.
26
Project launchNeeds reviewMedia
Add Blossom and media-server projects to the Media route
A contributor found active Blossom implementations and wants them mapped to media, apps and developer pages.
31
Person nominationNeeds sourcePeople | Users
Nominate relay operators and maintainer accounts for People | Users
The People route should cover maintainers, relay operators and researchers, not only celebrity accounts.
14
Relay reportPendingRelays
Compare public, paid and search relays for new readers
Relay operators can submit NIP-11 metadata, policy notes, paid/free status and uptime evidence.
43
NIP discussionHotGovernance
Use NIP-7D, NIP-22 and NIP-29 as the primary Crays community path
NIP-72 remains useful for compatibility, but the current upstream guidance says new group work should check NIP-29.
22
Source updateAcceptedApps / Relays
Attach Primal Server as cache/discovery reference, not relay replacement
The audit says Primal Server is useful architecture reference and possible cache layer, but not a standard relay.
19
Project updateMergedLibrary
Keep noStrudel as the admin/event-inspector reference
The product needs raw event inspection, relay visibility and signer warnings before adding heavier moderation tools.
37
CorrectionNeeds reviewStart
Move article talk boxes out of the reading flow
Hub pages should carry heavy contribution work; articles should behave like talk pages with corrections and source proposals.
Nostr identity
Login with Nostr
Use a browser signer, Nostr Connect, read-only npub or local account flow. Private keys stay out of the Crays server path.
Not connectedSigning actions will ask for a Nostr signer.
Crays6 min readCrays Nostr community
Crays Nostr Community
A Reddit-like Nostr community layer around the Crays knowledge hub: ask, submit, nominate, review, improve pages and surface new projects without weakening the existing archive.
The Crays Nostr hub should become a working room for the Nostr ecosystem. The 1,400+ content pages stay intact. The community layer lets people bring new evidence, new projects, better links, public users, questions, reports and review energy into those pages.
The quick readA Reddit-like Nostr community layer around the Crays knowledge hub: ask, submit, nominate, review, improve pages and surface new projects without weakening the existing archive.
The culture layer becomes stronger when venues can carry it.Self-custody is a lifestyle promise only when people can understand it.
What people can do here
The point is not to bolt comments under articles. The point is to let the Nostr community work on the archive: ask useful questions, submit projects, nominate public accounts, add sources, review crawler findings, report problems and help editors merge good evidence.
A contributor should always know what will be public, what is only a review item and what happens after approval.
The model now treats NIP-7D forum threads and NIP-22 comments as the primary public discussion shape, NIP-29 relay-based groups as the future enforced group path, and NIP-72 as compatibility with older moderated-community clients. Reports use NIP-56 and review labels use NIP-32.
Because this repository is currently static, the first implementation signs and queues events in the browser and can optionally publish signed events to selected public relays. Editorial integration still requires review.
The Reddit-like feed model
Each category can have a feed, but the feed should be useful rather than noisy. Readers need New, Hot, Top, Best, Unanswered, Needs source, Needs review, Accepted and Merged views. Moderators need the same objects with more context.
NENewFresh posts, project submissions, questions and source drops.
HOHotThreads with recent replies, votes, reports or moderator activity.
TOTopUseful contributions by upvotes, accepted status and trusted-source labels.
UNUnansweredQuestions and review requests that still need a human answer.
NSNeeds sourceClaims, project data or People nominations that need evidence.
NRNeeds reviewCrawler findings, submissions and reports waiting for moderators.
ACAcceptedItems that passed review and can be linked or merged.
MEMergedContributions that already improved an existing page.
Security needs calm product design, not fear as a brand voice.Trust is built through visible rules and sober decisions.
Who participates
A living Nostr hub needs roles. Some people only read; some submit sources; some maintain projects; some review; some moderate; some turn accepted work into finished pages. The UI should make those jobs visible.
REReaderSearches, follows topics, asks questions, reacts and reports problems.
COContributorSubmits projects, links, corrections, people, relays, videos and app updates.
MAMaintainerClaims or updates a project/profile and answers questions about it.
EDEditorTurns accepted evidence into Crays editorial updates without changing good slugs unnecessarily.
Contribution types
The composer should feel like a community tool, not a blank text box. The post type tells the system which review path, labels, required fields and destination community make sense.
QUQuestionA help request or discussion starter.
LSLink / sourceA page, repo, video, NIP, article or research paper.
PLProject launchA new or newly discovered Nostr project.
PUProject updateVersion, license, status, platform or maintainer update.
ARApp reviewA usage note, comparison or implementation finding.
NRelay reportNIP-11 metadata, policy, uptime, paid/free status or search capability.
NDNIP discussionSpec interpretation, implementation risk or example event.
PNPerson nominationA public account with evidence and a reason to include it.
MDMedia dropTalk, tutorial, podcast, article, video or creator archive.
COCorrectionA stale claim, broken link, wrong category or missing source.
Prepared communities
The prepared communities map onto the 12 Crays Nostr categories and the extra research/developer spaces needed for a live archive. They are ready for official community owner and moderator pubkeys.
GNGeneral / NostrStart. Broad protocol orientation, new member questions and practical learning. Topic space prepared for NIP-7D/NIP-22 threads, future NIP-29 group enforcement and NIP-72 compatibility.
NPNostr ProjectsApps. Project launches, repo updates, app research and build notes. Topic space prepared for NIP-7D/NIP-22 threads, future NIP-29 group enforcement and NIP-72 compatibility.
NRelaysRelays. Relay operations, NIP-11 metadata, paid relays, search relays and venue relays. Topic space prepared for NIP-7D/NIP-22 threads, future NIP-29 group enforcement and NIP-72 compatibility.
NINIPsNIPs. Standards, event kinds, implementation notes and open proposal tracking. Topic space prepared for NIP-7D/NIP-22 threads, future NIP-29 group enforcement and NIP-72 compatibility.
COCommerceCommerce. Listings, creator sales, marketplaces, FoundUPS and revenue paths. Topic space prepared for NIP-7D/NIP-22 threads, future NIP-29 group enforcement and NIP-72 compatibility.
GOGovernanceGovernance. Badges, labels, reports, reputation, DAO readiness and policy. Topic space prepared for NIP-7D/NIP-22 threads, future NIP-29 group enforcement and NIP-72 compatibility.
DEDeveloperLibrary. Libraries, relays, NIP debugging, event inspection and tooling. Topic space prepared for NIP-7D/NIP-22 threads, future NIP-29 group enforcement and NIP-72 compatibility.
RNResearch / New FindingsLibrary. Crawler findings, source review, duplicate checks and page update proposals. Topic space prepared for NIP-7D/NIP-22 threads, future NIP-29 group enforcement and NIP-72 compatibility.
CraysCrays. our implementation, profiles, venues, Super Nodes and Crays integration. Topic space prepared for NIP-7D/NIP-22 threads, future NIP-29 group enforcement and NIP-72 compatibility.
Moderation stance
The default state is review-first. Community posts can exist as Nostr events, but they do not become Crays editorial content until they pass the local review queue. This protects user keys, source quality and the existing archive structure.
Pending. New users and crawler findings are review items first.
Approved. Group visibility, compatibility approvals and local moderator actions make a post visible in trusted surfaces.
Rejected. Spam, unsafe links, duplicates and unsupported claims stay out of editorial pages.
Merged. Accepted source material can be merged into existing pages without changing good slugs.
CraysCrays. our implementation, profiles, venues, Super Nodes and Crays integration. Topic space prepared for NIP-7D/NIP-22 threads, future NIP-29 group enforcement and NIP-72 compatibility.