Might i ask a semi passive task from you, @elsat and anyone else caring to help educate the ecosystem?
We gotta aggregate all these nuances together somehow. Whether as a list saved/bookmarked events, or even adding a #nostrdocs tag to a thread to find later. Hell, even tag me! ๐
Anything unclear but important to know, terminology, workflow, usability etc.
Might be a nice starting point for a nostr manual
Login to reply
Replies (4)
Agree. Iโve been documenting best practices for a few months when I detect them. Example today thanks to Vitor:
Feel free to create best practices issues in nostrability repo, for lack of a better place.
GitHub
RFC: relay selection best practices ยท Issue #209 ยท nostrability/nostrability
problem statement & motivation Even as a technical person, relays are currently more hassle than I'm willing to put into this for fun. If mine are ...
Of course. What would be the most efficient way for existing resources & what would you like to see for new ones?
Nothing that can add labels post-publication seems to be working for me lately but anything other than that I can figure out.
๐
We're increasing the resolution.


Whether client specific, nostr specific, even zaps - any points of confusion. Minimal work, just some things for me to keep an eye out for and compile a set of resources to sort through.
The idea would be to tile up #TheNostr with a bunch of Q&A/terminology flashcards, in addition to any other more sophisticated, focused guides that could exist.