This is the message Amethyst gave me..
Could not fetch invoice from https://getalby.com/lnurlp/chiangmai/callback: Recipient wallet error. Please contact the recipient.
Discussion
nostr:npub1c9r9lad84kpqwnh09u58vdzwnfsnxcr7a40uf5ulkpdguq4667jsgaxu4k Yep, just tried him, his node is not producing an invoice. Here is the deal with nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm lightning addresses, according to our findings.
1. "Alby Pro Cloud" ( https://getalby.com/pricing ) -- should be VERY reliable. You should NEVER have a problem getting zaps if you do this.
2. If you self-host your own Alby node, then things get more complicated. Is your computer online 24/7? Is your internet connectivity really good? (And lots of people **think** their connectivity is good, but in reality, their internet goes up and down, and they don't notice.)
I'd be willing to bet that nostr:npub1c9r9lad84kpqwnh09u58vdzwnfsnxcr7a40uf5ulkpdguq4667jsgaxu4k might be in situation #2.
Self-hosting is good for other reasons (decentralization of the network). But it is challenging to get zaps.
This is definitely helpful to know
I’m building a PWA nostr client that primarily focuses on short form video events and run into issues when trying to directly zap users with different LNURLs that have CORS-restrictive policies
how do you deal with CORS issues when requesting invoices from different origins?
Are there any specific tools or libraries that you recommend for handling CORS issues in a browser-based application?