So, the idea is to do a book for programmers (like we have thousands of books about some particular language so that programmers can learn the API). Problem is, there is no “official” API. With that in mind, for now, and until that happens, I guess we could include what we have: NDK from nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 Swift code from nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe C++ code from nostr:npub1f65y84223ldt8x4ytaslr8el77wvryu9xu8k5fedm2ql4hs2q54s7uaq28 (actually also C code from nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s ) . Mix the code with the algorithms . I did not get a good idea of how to do things just by reading the NIPs. The only way I was able to know how to get a list of follows, for example, was to debug nostr:npub1fjtdwclt9lspjy8huu3qklr7eklp5uq90u6yh8mec290pqxraccqlufnas and dump some json to files. That is from the programming side. Also include some background for the motivation of #nostr. Like from an historical point of view, starting with the invention of the WWW by Berners-Lee. I did a small write up on that , in the link below, that tells that we need a “global digital public square that is essential to the survival of humanity” ( more or less quoting Elon Musk here) , I guess what Twitter was supposed to be (and is, but with issues it has now) https://pedro-vicente.net/
Discussion
Nice! The Web was not just HTTP, it was also HTML, and the most important part of all, the URI, which ties it all together. Originally the UDI (Universal Document Identifier).
Two ways of creating a knowledge base are though a wiki or a collaborative book such as:
There's quite a few different book style documenation software. Maybe we could make a short list.
There's also a bunch of wiki software. Here's something I started for the W3C Nostr Community Group in a github wiki, which I hope to create a user guide and a dev guide. Still very early: