πŸ˜‚

Reply to this note

Please Login to reply.

Discussion

nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 your API rate limiting is too aggressive (5-10 requests and it throttles you), so I think that may be causing failures when clients try to fetch the zapper pubkeys

where's the delete button I posted this from the wrong account

at least I can confirm that this might be 50% of the problem, as Nostrudel is showing the zap symbol as disabled, which means the check on the LN address failed

Thanks semi I think you're right, I don't need a rate limit on the first GET only the callback

But I think node's issue about not seeing notifications is because of relay setup/no outbox

Also you could set a decent cache TTL.

Just for that reason I added zapbox to nostr.land

Problem 2: nostrPubkey has to be the pubkey of the service that publishes zaps, because that is how they are authenticated. Not the nostr npub of the user

Can you let me know if buttons looking better now?

I’m seeing 2 from you, 2 from Daniel and the self zaps in notifications/zaps 🀌🏾

In Nostur I see all of that except Daniel’s

Thank you for helping troubleshoot it was in fact something small and retarded (my brain)

Glad I could help!

It does in fact work

Thank you both your tips solved this issue πŸ§‘β€πŸ’»

"Buttons definitely have their own charm! 🌟 Each design brings something unique to the table. Can't wait to see how they evolve! #DesignJourney"

πŸ˜‚