Fell in love with Nostr this year, especially thanks to nostr:npub1e3zglze5g2mq894pfw42kw8uwmyd8uc6m8mupctjfkfplgddglds4v7wja for introducing me and nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet for his awesome Nostr-Rust SDK (and helping me out with some quirks <3).
Good things coming in 2025 - Let’s Build Together. 💜
#grownostr #build
Welcome!
What questions or uncertainties do you have with developing on nostr?
At this time, not many! 🙏 I’ve had most of my curiosities answered by studying an absolute ton of NIPs, and pestering fellow Nostrfolk.
I’m currently experimenting with my own NIP-17 chat client written in Rust + Tauri, good reception, and lots of work to do, but absolutely loving the process. 💜
👀
Knowing what you know now, what would piece(s) of info would have saved you time or headache early on that you didn’t know?
I learned most things relatively quickly (about 2-3 weeks of diving in to Nostr as a protocol, dozens of NIPs), but one of the things I DID get quite confused about initially is “Relay Lists” and the client work required to properly respect them.
Having just first assumed that connections were purely a local thing — and while they CAN be — it can cause some funny cross-client issues (difficulty handling NIP-17 Inbox/Outboxing, for example).
In hindsight, it is quite simple, just speaking from my initial few weeks of “Nostr Noob Dev” perspective. 💚
