Should malformed lightning callback urls be supported for zapping?

[oren-z0]

For Example, http://sendsats.lol/.well-known/lnurlp/jb55 gives:

{
  "status":"OK",
  "tag":"payRequest",
  "minSendable":1,
  "maxSendable":10000000000,
  "callback":"https://sendsats.lol/@jb55",
  "metadata":"[[\"text/plain\",\"jb55's lightning address\"],[\"text/identifier\",\"[email protected]\"]]",
  "allowsNostr":true,
  "nostrPubkey":"9630f464cca6a5147aa8a35f0bcdd3ce485324e732fd39e09233b1d848238f31"
}

Notice that the callback url contains an unescaped "@".

Right now, NDKEvent.zap() function fails to create a payment request.

[oren-z0]

The URL was ok, it's the zapping comment that included a "nostr:..." (mentioning some user, different from the payment zap receiver) - so the generateTags() function added the mentioned user's pubkey as a p tag in addition to the receiver's p tag, and some lightning servers don't like zap events with more than one p tag. They are correct to do so - according to the protocol there should be only one p tag: https://github.com/nostr-protocol/nips/blob/master/57.md#appendix-d-lnurl-server-zap-request-validation .
See: #53