Nice to see some integration happening!
Re: zapping. We intentionally did not put a lightning address on the npub we're using to publish track events so that we wouldn't receive generic zaps. Our goal was to only enable zaps for specific events (tracks) so that they could go to the artists.
I think there is still a bit of ambiguity on how to handle zap requests for these NIP-33s... we're sorting through that now. But great to see some progress and hoping we can help clarify things for future dev
rheedio
npub1z0…wxuxf
2023-04-20 22:30:10
in reply to nevent1q…ua6w
Author Public Key
npub1z0rrmak9v5drkr3a20e5pehrwzc5pf392apfl5t9h9qk928nay3s7wxuxfPublished at
2023-04-20 22:30:10Event JSON
{
"id": "4f23ae3d60e18976663c5db171d3ff8764975c7a2c49be434c9ab043639740cc",
"pubkey": "13c63df6c5651a3b0e3d53f340e6e370b140a62557429fd165b94162a8f3e923",
"created_at": 1682029810,
"kind": 1,
"tags": [
[
"e",
"09d9b242016abe1dd810dabc15f3b945b8b2917059f8b7bae6979edea6721bd2",
"",
"reply"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"
]
],
"content": "Nice to see some integration happening!\n\nRe: zapping. We intentionally did not put a lightning address on the npub we're using to publish track events so that we wouldn't receive generic zaps. Our goal was to only enable zaps for specific events (tracks) so that they could go to the artists.\n\nI think there is still a bit of ambiguity on how to handle zap requests for these NIP-33s... we're sorting through that now. But great to see some progress and hoping we can help clarify things for future dev",
"sig": "413317853e6a8830425c98db77ee9365a5e37815413ecebddd012b5ea25830cc23fd505ee54e1ee6e6286d426b3a540d0930d31a241659d47a23ceb1fbd10527"
}