Cameron on Nostr: npub1ln5q8…5xyw6 npub1df6ey…gns3a Re-listening to today's show... Correct all the ...
npub1ln5q8np5aezhtt7ztv6tah86xk4t3smjuchdvxp0u6uta056204q45xyw6 (npub1ln5…xyw6) npub1df6eyr7x6cv4gq99h3rjnhj6f4yqzxa97pxf2ecxeq82ea8mwdyqfgns3a (npub1df6…ns3a) Re-listening to today's show...
Correct all the nodes hosting the file get a portion. I don't think you can know *who* served up the file because it's stored in chunks (like bit-torrent). One playback may pull a chunk from all the nodes. Which makes it faster/more responsive with more nodes.
When you get "too many" nodes, the payouts will be smaller (100 nodes = 1/100th share). You could increase your split ; ) or let them self-regulate. They may un-favorite if only getting 1 sat.
Correct all the nodes hosting the file get a portion. I don't think you can know *who* served up the file because it's stored in chunks (like bit-torrent). One playback may pull a chunk from all the nodes. Which makes it faster/more responsive with more nodes.
When you get "too many" nodes, the payouts will be smaller (100 nodes = 1/100th share). You could increase your split ; ) or let them self-regulate. They may un-favorite if only getting 1 sat.