My suggestion is that you build a usable product instead of building just a library. Or build both together. But don't build just the library. I would start with go-nostr and build on top of it if I were you, but I'm biased. If go-nostr is not working well, then start a new library, but always build it along with a product.
Hi 🌊 nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 how would you describe or compare the goals of these repos?
https://github.com/fiatjaf/khatru
https://github.com/nbd-wtf/go-nostr
This weekend I will start something like ~gNDK~ a bunch of Go types, funcs just simple foundational building blocks to start but same aim as NDK to encourage and simplify adoption and development, then optimise and build on top of this some reference relays, outbox, clients, filters, tie in with any reference nip code…
Does it fit in with either of those repos, any other projects, or should I just start afresh with its own focus? 🤔
Discussion
yep that's the plan, several layers built out at once with first product exercising them, and open the foundation to encourage parallel and similar value-adds, work up the stack from there Cheers man