nostr:nevent1qqsxtk5avksr3usfshhugt0hwrdtsd2tflvxav64zmapjwznrrwejdspz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qygyxsh477ejn8rwkjv0zen0ncxwe7rj6zpnujx8j9ecgrsj43786lqpsgqqqqqqshykc4n

Reply to this note

Please Login to reply.

Discussion

Afaik most - but not all - people can zap me, but it doesn't get confirmed. I set up the lightning address long before Nostr using BTC Pay (and some nginx magic to so it can use the root domain).

I failed from web. it might be CORS issue

Ah that could explain the difference. Is there any guideline what the header should be?

IIUC the fact that I redirect to (my own) nostr:npub155m2k8ml8sqn8w4dhh689vdv0t2twa8dgvkpnzfggxf4wfughjsq2cdcvg should mean that setting CORS headers is it's responsibility. So maybe this is a bug on their end?