Nostr is when a homemaker in Wyoming can use a client built in Mongolia to read articles stored on a relay in Seattle and pay for each part with a zap-split from a Lightning node in Switzerland.
Discussion
“Pay for each part with a zap-split” 🙌
We need bidirectional zap-splits, all the way down.
Some people mostly read or watch, and they can zap the whole stack (client, npub, media server, relay).
Other people mostly write or create, and they can arrange to share the zaps they receive.
I would love to have a zap-split event, where I could define who-gets-what, when I get zapped. At the moment, I get the zaps and then I set up monthly zaps from my Lightning wallet, to spread them to my service providers. This is tedious.
Better would be to edit it in https://metadata.nostr.com/
This would also mean that relays could compete on content. Relays with a better selection of npubs would have a higher sat:work ratio.