Is there anyone interested in testing out our NDK in their next client?
The more different projects use it, the better we can build it.
#asknostr #dev #Nostr
nostr:note1ud5sncavvettjxzevvm8acffktgunvd86mervfepz6t0w2gqp3asr75fel
Discussion
Def want to see more c/c++ apps out there!
If you want to try it out, just DM nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn or reply here and he'll get back to you. Thanks.
What's the difference between your NDK and the rust-nostr libraries?
1) We wrote it and we're an entire group of uptight corporate types who review and test everything to death.
2) We will be versioning and releasing differently.
3) Using our stuff adds an additional counterweight in the whole NIPs discussion, so you would have representation without having to spend all day stalking NIP specs.
4) There will be OnlyUs features included and you can influence the design.
5) It is written in C/C++.
6) We have Nostr-native customer support, over GitWorkshop, and we are responsive because this is basically what we do.
To clarify, our NDK is still in development. We're looking for potential customers, to help scope out what to put in it.
There is actually no NDK that matches the complete current NIP list and is 💯 backwards compatible. They all pick and choose what to focus on and which changes to support.
And, increasingly, new Nostr specs aren't going to be NIPs. They're going to land in the wiki event register or be product specs in those individual product repos. Or just be open-source prototype implementations. We will be implementing a selection of those, as well.
So, yes, different NDKs are different.
https://wikifreedia.xyz/nip-event-register/laeserin@getalby.com