That's unfortunate because it's actually what I'm using for my lnaddress
Discussion
Isn’t it the wallet that needs the support?
Nope.
ln address provider need to fetch an invoice with specific description.
Plus, provider need to look for payment status in order to publish nip57 notes.
Damn.. I’m using lnme but it doesn’t see much development.
NIP-57 is simple, but satdress cannot support it currently since it doesn't know when the invoice was paid, and you can't have a separate address for zaps and lnurl because of the bad choices NIP57 made.
Would it need access to an admin macaroon to know if the invoice was paid?
It would need to keep an open connection to all nodes from all registered people and would turn into a very bloated thing and error-prone thing.
And easy to DoS because monitoring all those invoices means keeping state, which takes resources.
Especially when creating a zap request (i.e. binding resources on the zapper) is free, just takes sending a nostr message.
So... zaps will only ever work with big centralized custodians? That's a big let down...
Not necessarily as long some good Dev can tweak simple ln@ Foss solution.