#[0] got the 21 sats, on my side all looks good
zapped you and I see nothing, did you restart? :)
I made a PR which works for me
// vec![zap_request_info.zap_request.as_json()],
vec![invoice.description],
I think this change is enough to make it work
mine works fine http://rr.btcmp.com/IMG_6795.MOV
and that means anybody zapping me and CAN see the zap has a broken client. :)
#[0] damus is checking if the description hash matches the description and your zapper is messing up the description order. this also means that nostur is not checking that
interesting, on another client I can see the zap. either your plugin is doing something wrong and the other client is not checking or damus is doing something wrong
“At times like this, I wish I was but a simple peasant.“ https://iwdrm.tumblr.com/post/4088689039
https://void.cat/29BDetehjMq4XUCRhoKvBB left is working, right is yours
id bd0dc2d1b75586a0c6edc3b9e24552b5bcbfb169a2702c32838b3acfc53d060d. this account, damus
#[0] your zap got answered by the js zapper. turned that off now
I used a working zapper on the same invoice and that works. your output has the description changed and also the tags have different order. don’t know if that matters though
what do you think the spammers will do with that table?
#[0] tried your zapper, everything looks fine in the logs, but my client can’t see the broadcastet note yet
first thing I added to lnurl-commando was checking that ID machtes the content and that the SIG matches the ID
Please do not accept invalid events in your client. Do not accept non-integer "created_at" values, do not accept non-string-array on "tags", do not accept bech32-encoded keys as tag values. Every time you do that, Nostr dies a little.
For more information on how this kills Nostr, read https://fiatjaf.com/27598e6f.html
error fetching invoice
“There is no clock on my business!” https://iwdrm.tumblr.com/post/7804044233

