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

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.
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.
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.
โ†‘