"what’s the best way to build on nostr, any resources you can share?"
I get this question a lot. What's the best answer?
"what’s the best way to build on nostr, any resources you can share?"
I get this question a lot. What's the best answer?
Hodlbod's book can be a great start IMO
But people also have the tendency to over prepare. They want links to articles, videos and specific documentations BEFORE they get started, but in reality, just reading NIP-01 and using Amethyst/Damus for a while to understand the UX should be enough. LLMs, even without MPC servers and whatnot have enough info about nostr to build you small functional clients already
nostrability...
I assume yo are talking to a software engineer.
I would follow up with a question to clarify the areas of interests / experience and point the person to one of the open-source projects to get inspired.
The benefit is that most probably the person can view a live version of the app which is cool, and the repo would explain what NIPs, libraries and tools it uses.
Vibecoding with #MKStack and #Shakespeare (https://shakespeare.diy)
Some great resources to start with:
• https://github.com/nostr-protocol — official protocol docs + NIPs
• https://nostr-resources.com — curated list of tools, clients, dev resources
• https://github.com/fiatjaf/nips — NIP (Nostr Improvement Proposal) specs
• https://nostr.build — great for image hosting + developer inspiration
Read the NIPs
this is the answer. the nips are axioms, your apps are theorums. prove some useful stuff.
echo '["REQ","sub1",{"kinds":[1],"limit":3}]' | websocat wss://nostr.mom
If that simple command doesn't get them playing, then maybe they are not really that interested.