Zap server implementations, can you start putting the optional `a` tag of the zap request note in the receipt when present? 🙏 This will enable zaps to parameterized replaceable events (NIP-33) like long-form content (NIP-23) or user lists (NIP-51). A description of how implementations should behave has been added to NIP-57 https://github.com/nostr-protocol/nips/blob/master/57.md cc #[0]
Discussion
Sure, I'll do it. What's the purpose?
Do I just copy the a tag from the request to the receipt?
zap things like long-form notes, check out https://habla.news copying the tag works, they have `kind:pubkey:d` structure if you want to validate it.
Maybe it should be made mandatory in the spec?