#[5] this is 🔥
What can team #ndk do from dev, and/or design perspective to make your experience using #ndk even better?
What did you find most valuable in using #ndk?
cc #[9] #[3] #[10]
I've been dabbling with Nostr packages lately and decided to experiment by creating a real-time mirror of the Bitcoin Mailing List on Nostr, going back to 2011👴
nostr:npub15g7m7mrveqlpfnpa7njke3ccghmpryyqsn87vg8g8eqvqmxd60gqmx08lk
To help catch up on discussions, threads from 2011 and 2023 with multiple responses include AI generated summaries 🤖. If this sparks interest, I might expand this feature.
Each sender has an archive account for easy access to all their messages and stats 📬. The best part is that there's no moderation here - I believe in client-side filtering.
Considering making it two-way: zapped notes could bounce back to the mailing list based on popularity. 🔄 What's your take?
Please note, due to rate limits, it's not on all popular relays. However, for those of you who run a fancy relay and would like to store a backup, I can provide the full npubs whitelist🔒
Lightning mailing list is coming next!⚡️
Using nostr:npub1ndk0nwqwjajykt5fnlyjhdlp33dffurcmx5vfp2hljp2y7ew62fsq7qfy4 for this was straightforward, shoutout to nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft and the team! Feedback is welcome, let me know your thoughts!
nostr:npub1qgwhaaa2lsp54rl0hfx7qa3z678ax6wlre0em475rhpvl7n54cpqgg7y7n
Discussion
I looked into a few options and NDK stood out as the simplest and best built. It is really tough to spot any issues.
I had to go through some nips and work out the exact tag symbols to use, which I think could be avoided. Also, I couldn't catch and handle the rate-limit exception from outside the library code.
We’re you using fetchEvent or subscribe when you were hitting limits or was it publishing events?
Wrt the first part; I’m about to launch an ndk-kinds library that makes dealing with NIPs transparent.
I’ve been writing it and makes dealing with NIP peculiarities very nice and intuitive