merryoscar on Nostr: UPDATE - seems like this is already partially working: - damus displays zapper image ...
UPDATE - seems like this is already partially working:
- damus (npub18m7…q955) displays zapper image and zap message
- primal (npub12vk…pugg) and a open source android nostr client (npub1nz6…0w5y) display zap message
I guess it's not too much of a lift to add zap sender and recipient to the embedded notes?
- damus (npub18m7…q955) displays zapper image and zap message
- primal (npub12vk…pugg) and a open source android nostr client (npub1nz6…0w5y) display zap message
I guess it's not too much of a lift to add zap sender and recipient to the embedded notes?
quoting note10ld…83xjZap Mentions / some thoughts on broadcasting zaps...
Today on nostr zaps don't provide a great discovery signal because they are fundamentally reactions which you only see if the event being zapped is in already your feed.
If you don't see the content, you won't see the zap reaction, and therefore you won't get the payment signal that indicates the content is valuable.
Zaps also can't trend on nostr because they can't be liked / reposted / zapped / quoted / replied to.
As a user there is no way for me to broadcast a zap in the same way I would broadcast a kind 1 note. I can share my thoughts on something - but there's no way for me to increase the signal of those words by including a zap alongside them. Examples where you might want to do this include:
- donating to a good cause
- sharing a long form article
- supporting a content creator
- thanking a supporter for a zap
---
Potential Solution - Zap Mentions
I think there is a solution to this that doesn't require a new nip or change to the spec. Zap events could just be embedded in kind 1 notes using the standard NIP-27 nevent1 format.
Clients could give users the option to 'broadcast' their zap within a kind 1 note in certain cases and other clients could render some additional UI to display the zap.
Below is an example zap I just sent to jb55 (npub1xts…kk5s) - you will probably be reading this just as nevent1... but it would be trivial for clients to parse this and render the zap in whatever way they choose:
nevent1q…5tnu
Ultimately we don't want users of nostr clients to be forced into a choice between sharing content or zapping it - we want them to be able to do both in one frictionless action and this will generate the most signal and make nostr the most attractive place for content creators.
I would love to hear thoughts on this from client developers / designers - fiatjaf (npub180c…h6w6) jb55 (npub1xts…kk5s) miljan (npub16c0…6nvr) hodlbod (npub1jlr…ynqn) PABLOF7z (npub1l2v…ajft) JeffG (npub1zuu…c2uc) Karnage (npub1r0r…q9ac) nielliesmons (npub149p…722q) Gigi ⚡🧡 (npub1der…xzpc)
And if someone wants to try rendering this note in the way I've described please tag me!