Thank you all for the likes and zaps. The test worked well.
Thank you #[2]!
Thank you #[2]!
...and if you zap me, you might get a surprise...
Please go to nostr:note1qqplpschvr6wq0pml2myhte33pnglyvft0q74pd2n0hktcdx7k2s93j4pq and like it. I'm testing high like counts.
I'm testing something. Please like (or dislike) this event. I need the reaction count to get really high.
Thank you #[1] and #[2]
Thank you again #[1], and thank you #[2], #[3], and #[4].
My TODO list as of this morning:
It wasn't so long ago that nostr was:
Yeah, well, I already know what Z is. My bike broke an hour ago and I desperately need a new one. So Z will be finding and buying a new bike.
>From: JackDorsey at 05/15/23 14:36:14 on wss://relay.nostriches.org
>---------------
>Best thing at this point is to move on to Z
X was definitely on the to-do list. It's a pretty important feature. (showing all mentions, and selecting recipients of replies). Y (determining who sent a zap) was not on the to-do list at all; but it suddenly got really interesting because I could diagnose it using print statement in real time. (sigh).
>From: (Stackinbeets) at 05/15/23 14:23:23 on wss://nos.lol
>---------------
>Let me guess, Y was something on the bottom of the to-do list and X has a fair amount of urgency.
Thank you #[1] X 2!
Thank you #[2]
So I started the day with a plan to do X. Then I got distracted by Y. I got Y done; but not X. And that's the way it goes.
Thank you #[1]
Thank you #[1]
I've added the private/zap.log file to more-speech. Any zap that you either send or recieve will be logged in that file. It may or may not contain the amount of the zap, since that seems not to be reliably included in the zap reciepts from some wallets.
That's pretty much what it takes. I was putting print statements into more-speech. One way or the other we divine the contents of these events.
Nips. Who needs 'em?
The bottom line is that the "description" tag of the 9735 Zap Receipt seems to contain the json string of the 9734 Zap request. The "pubkey" field of the Zap request is the sender of the zap. However, at least some of the wallets seem to delete the "amount" tag of that Zap request; and so the amount of the zap is lost.
I'll write up a blurb about this for NIP-57 and do a pull request. My luck getting PRs into the main-line has not been great, so we'll see.
;-) What fun would _that_ be? ;-)
>From: jsm<-DerekRoss at 05/15/23 12:10:41 on wss://relay.damus.io
>---------------
>Was about to tell you I figured it out but realized you were a step ahead of me.
>
>Maybe the NIP could be made clearer?