it would make sense that nostr clients start watching the taproot addresses associated with users' respective NSECS, it has potential for interesting social use cases

I was there when it happened and, I can assure you, you didn't zap first 😄😄

These were not the expected players for this P2P game but thank you for sponsoring ahaha

The future of zaps is here!

try it out at https://pubpay.me

nostr:nevent1qvzqqqqqqypzqqj2rcxwgy0jwau06r54fgjv2d5v8mdk4y3kqgcl4r7tr4graqm3qqsze6txe4kqmy92jegefzm4k7cm92atsk8w3lqax0ntvfvezvqvjjqss0uye

If a kind0 pays a kind1 and no one publishes a signed receipt, does it make a zap?

Zaps to this note will zap nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m

I would Pub Pay you but the zap-lnurl you provided doesn't allowsNostr zaps

Pubpay tags don't conflict with zap-goals.

They're complimentary uses cases.

We're going to implement zap-goals in https://pubpay.me soon 😎

So... what did you have for lunch? 😄

It was tested on mobile with nostrsigner (amber, for example) or nostr.window (firefox with nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm extension or nostr:npub1uq70uqgas9pyhds2zt57kr9se8rg3s68ztphjnq82ts8rzeknmeql7u0c2 Bravo)

try with a zap-min tag as well 😉

let me know when the problem is fixed so I can pub pay you 😊

It should work on desktop\mobile with window.nostr (alby, for example) and with nostrsigner: on mobile as well (amber, per instance). it was also tested on mobile with fedi bravo and kiwi.

Some browsers don't allow the opening of the lightning wallet from a link lightning:

you need to activate the cors or else I can't zap your zap-lnurl address 😉

and my server crashed because of that🥲

Try creating a pubpay with the zap-lnurl tag:

Insert a lighting address, that is not the one on your kind0

You just press Pay 😉

When the note1 has reached zap-uses, the pay button gets deactivated

Since a public payment it's a normal kind1 with some extra tags, you can zap from any client.

For now, only pubpay.me is rendering the zap conditions

nostr:nevent1qvzqqqqqqypzqqj2rcxwgy0jwau06r54fgjv2d5v8mdk4y3kqgcl4r7tr4graqm3qqsqqqq8vgqurwr8q9xk2wha9tnjsemhwd8qtxjuva0uktv8sgw2xhsw0v8hx

I'd have to write the code that calculates which zaps went to you and which ones came to me

*if zappers use the correct client 😁

These zaps go to Zoe