where comes the need for a non-custodial lightning address? principle? cause the value transacted with zaps is miniscule

Reply to this note

Please Login to reply.

Discussion

It's just I want to use my own domains.

Otherwise which custodial service is fully compatible with zap including notifications to relays so I can see I got a zap in Amethyst or other clients ?

i've build myself a little proxy for nostr:npub1qkdmqs7sqazsk3swa7ymvhq7g0j4fuxk06sxr395qsaw9kngvjus37h9tf (although someone told me he couldn't zap me, others can, not sure that was temporary)

That's the same issue I have with my LNbits routed by nginx, some can zap, some cannot (mostly Primal cannot).

And what about using bolt12 for zap ? Is it working ?

i don't know

95% sure you have a CORS issue with the "dalliard.ch" endpoint:

that doesn't look right — will take a look

Can you check if I have the same issue on eluc@bitcoincoin.ch LN address ?

you would need to set that as your lightning address in your nostr profile in order to test it properly

I just set it back to eluc@bitcoincoin.ch if you had a minute to test.

it worked for both of us, but would be great if nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq could confirm with the client he had the cors issue (at least with my address)

just worked, looks like u fixed the CORS issue?

yes, thank you for helping out

yes looks like it works.... looks like you are in French-speaking Switzerland?

I've got great memories of summer in https://en.wikipedia.org/wiki/Les_Diablerets here

Nice resort. Did ski there for a long time.

My VPS reverse proxy is at least.

Now Primal cannot zap me again. So definitely something going wrong between Primal and LNbits LNURLp.

with a cors issue like this, some clients will be able to zap, but some will not

to demo the failure, you can set up a separate nostr account and attempt a zap from a web client like Yakhonne or Nostrudel

ah it is about the client and not the lightning provider beeing used. cause i got two zaps from you, i guess not from yakhonne or nostrudel?

yes, CORS is something enforced by web browsers... very confusing...

so it is even the web browser and not the client? cause i tested zapping myself with jumble (and my web browser) and that worked

i think i solved the cors issue — if you could be so kind to zap me (with the client you had the cors issue), i will zap you back of course