@Vitor Pamplona has a great perspective on nostr development. We all build it together. Devs, maintainers, mavericks, content producers and content consumers. 

 Make one with the pubpay logo! 

 Ops 

 PubPay it forward 

 It's a risk, but clients can adapt or ignore. Moving it to another kind breaks the social proof use case. 

 Wasn't the chaos supposed to be embraced?  

 With current clients, kind 9041 are invisible to 99% of users. 

 Appreciate the feedback. Social proof use case is pretty self explanatory. 

 Amethyst uses "zapraiser" tag on a kind 1. Damus doesn't seem to render zap goals in the versions I'm running. 
Can you share an example? 

Nostrudel renders it but pushes it out of the notes feed.
nostr:note1dfrp7zgt4jl6nwwqskgjzsyxs9t9ks775ukafhjpkenf6y6fph2slxcxf5 

https://image.nostr.build/8514edb2b074793f4463c0fa2c16f6036a5e0d2832f7fb901b3fa86313cb54de.png 

 So the experience is inconsistent regardless. Does't seem like a strong enough reason to stop building on a new standard.
We envision a world where more is possible with zaps, and the current tags and standards are just not going to cut it.  

 Exciting stuff! 

 This guy get's it!
https://image.nostr.build/df05e5eab2568e9210e8f0a22c2866545d10364d7cb5fc9e8a655755bf6f31ed.png
nostr:nevent1qvzqqqqqqypzqgd5rygzm28upw5sfp9wey6t74dh408htmkm8yfyart4ujglgxj7qqs9t6v7kvwd09gkf77rxfj6qhctvstur3emxrsed97588ll7y0gugctzpauh 

 PubPay does the accounting. All zaps are linked to the note. 

 Works best when you add zap-min or zap-uses tags. 

 Yes, but different browsers and operating systems will limit the access to the clipboard so still not working perfectly. 

 There is no good signer for iOS that we're aware of. 

 sad 

 Ecash via pubpay zaps! That's what we want! 

 Nice! Let's make it happen 

 The main goal is to be zap native. The UI is up to the clients to decide if they ignore or adopt these tags. 

 😀 We'll do some nice zap event rendering soon!