Replying to Avatar Sjors Provoost

nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx I think your node is down, I can't post my pun!

Podcasting 2.0 could definitely use nuts.

cc nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg nostr:npub13ql75nq8rldygpkjke47y893akh5tglqtqzs6cspancaxktthsusvfqcg7

Reply to this note

Please Login to reply.

Discussion

Throw nuts at podcast host, done, sounds simple!

(meme credit goes to moonsettler)

Chainanal? O_o

The nut gallery approves

chainanal....nice

To expand on that a bit: in practice you need a (semi)custodial lightning wallet as a listener anyway, because otherwise you're going to run out of battery on your podcast walk. Who then know what you're listening to and when.

As a podcaster you can self host, but - especially with splits - you'll miss out on some of the payments due to routing issues.

If instead you can post (pubkey locked) e-cash tokens somewhere, that's probably easy enough for a podcast client to support and hardly requires bandwidth.

And you don't even have to throw the nuts *at* the podcaster. If they're pubkey locked anyway you can just toss them anywhere. Eventually they'll get to the host. Either because their wallet crawls the web or their friend finds it on nostr and forwards it.

You could add a "has this been claimed yet" API call to mints so when software encounters a nut somewhere they can decide to either ignore or kick it down the road somewhere.

Iiuc, there's already a check for if a nut has been claimed or not. At least in sole impl.

(I guess you've already used the name "nut kicker" for some other feature than this random forwarding idea...?)