will the next release send/receive zaps?
Discussion
What is more important, putting in more features or releasing sooner? Always a tension there. I don't know the answer.
Release sooner, get quality feedback, iterate/improve more in alignment with what the market wants to see from the product
I agree with this. Release sooner.
As a tease to #[2]
4 days ago I added event kinds 9374 and 9375 to nostr-types along with PayRequestData struct, lnurl() computation from Metadata, and Event::new_zap_request(), plus I tested it all with manual scripts and one-off small binaries in a joint session with #[1]
so the type-related work is already prepared and ready. I think it will probably show up in the next few weeks.
Release often, of course.
Unless you find it takes so much extra time to feature freeze, etc and coordinate many contributors.
My choice would be to build it out of sync with your releases. I doubt I would have much success deciding exactly when to do that, so I haven't tried yet.
Gossip is my 'daily driver' but I find myself shutting it down just to go to Nostragram to watch (and participate in) the zapfest. And the pretty colors of course. :)
Not sure why exactly, but I loved using zaps to pay for relays, for example.
I can probably resist the urge more now I think. :)
NostrGram is great for visuals. I'm not jealous. Use multiple clients, microapps, etc. Gossip will probably have zapping ability in a few weeks if life doesn't get in the way.