nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj You are nominated for "30 days, 30 devs" -- we tried to zap you but your zaps seem to be broken currently. Pls let us know when you are back up and running!

Reply to this note

Please Login to reply.

Discussion

I will fix it 1 moment

My zaps are working. What error are you getting?

Zap failed: Failed to create invoice.. from jumble.social.. will try for a different client

Could you check the network tab response?

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl Are you able to zap nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj using jumble.social? I'm am repeating the following issue:

1. I am able to zap @semisol from Yakihonne (web) and Nostrudel (web)

2. On Jumble.social I get "failed to create invoice".

Might be an interesting test case for you to debug if you can reproduce the issue

Are you using anon zaps by any chance?

No, nothing special or unusual.

Odd…

Zapped

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl Yes, I think I have a good repeatable issue for you -- I am able to zap nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj with Coracle, Yakihonne, and Nostrudel, but with jumble.social I get "failed to create invoice".

The latest version of nostr-tools builds zapRequests with a k tag, but nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj’s lnurl server doesn’t support it.

Could you make such error texts visible to the user? Thanks.

I have added support for k.

fix confirmed! I am now able to zap nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj with jumble.social!

I’d like to confirm, are the response formats from lnurl servers standardized?

Yes. It is always status==ERROR with a reason.

They're visible now

Hi

Hi

No sé si rizful está funcionando mal pero hay algunos zaps que no me llegan, no sé si es problema de rizful o del usuario que envía sats

Los zaps son difíciles de depurar debido a la gran cantidad de posibles puntos de fallo. Podría ser el emisor del zap. Podría ser el receptor. Podría ser la aplicación nostr del emisor, podrían ser problemas de conectividad con la red Lightning... De hecho, nos especializamos en pruebas de zaps. Así que, si encuentra algún escenario donde los zaps no funcionen, le agradeceríamos que nos lo indicara para probarlo. Necesitamos saber qué aplicación está usando, quiénes son el emisor y el receptor del zap.

Gracias