Oddbean new post about login | logout Problem solved: Changed my address to nostr:nprofile1qqs8suecw4luyht9ekff89x4uacneapk8r5dyk0gmn6uwwurf6u9ruspzpmhxue69uhkumewwd68ytnrwghszxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs2juazd address. 😆 nostr:nevent1qqsxm2gad0xhq5fcr7p64j5tn280psst3tnn6x06k28dp0d0nwu9fvcpz9mhxue69uhkummnw3ezuamfdejj7q3qqex7yjtuucs6ac49kjujdgytrjsphn5a4pdscu2w3qlprym4zsxqxpqqqqqqzhluexj
Hahah that sounds like an awesome move! Permissionless payment directory has it's up's and downs but at least you have sovereignty to manage. Could you explain why you don't like people supporting you monetarily? Having trouble to find a reason why that could be bad.. Especially if you strive to act ethically (which you seem to do).
Is there some NIP discussing on redistribution of zaps received on a single post? 🤔
Yes. NIP-57 itself https://github.com/nostr-protocol/nips/blob/master/57.md#appendix-g-zap-tag-on-other-events
not sure I got it!
Appendix G: zap tag on other events When an event includes one or more zap tags, clients wishing to zap it SHOULD calculate the lnurl pay request based on the tags value instead of the event author's profile field. The tag's second argument is the hex string of the receiver's pub key and the third argument is the relay to download the receiver's metadata (Kind-0). An optional fourth parameter specifies the weight (a generalization of a percentage) assigned to the respective receiver. Clients should parse all weights, calculate a sum, and then a percentage to each receiver. If weights are not present, CLIENTS should equally divide the zap amount to all receivers. If weights are only partially present, receivers without a weight should not be zapped (weight = 0).
is there any client that implemented/leveraged this?
I know that amethyst on Android does Example zaps to this note will go 90% to you and 5% to opensats (if zapped via amethyst and any other client that support it)
Exzellent & intelligent