How about a readable spec that tells you what a Nostr client is and is modular enough to change interactions and functionality?
a base off of which to build, instead of having everyone implement their own version and kinds and so forth.
Login to reply
Replies (3)
What if instead of misinterpretable hand-wavey specs, we had concrete implementations in code of the core functionality? We might even package this up into an easy to use thing, which we could call a library.
But the UI is still very problematic. So we also make a base UI. Then, why bother with people reimplementing their own thing all the time? We add 99% of the functions everyone needs into the base UI.
You have built a client
Isnt the nostr sdk exactly this?
I'm with you about building a library but after that, UI is completely function dependent. So, I'm not sure hard coding a UI is a good idea.