Thread - Nostr Hypermedia

cloud fodder and 121 others cloudfodder@rogue.earth 4 months ago

ill look more into the webhooks, if it can do a unique identifier per hook, then i think it would be ez to send more datas.. the podder would need to run a service to collect those. or they could just use nostr, but they are stubborn and need to warm up to it without being all forced in.. clearly they enjoy running *something to push their RSS warez.

↑ Parent

Replies (2)

BITwise 🐳 >>= RIGHTish gug@nostrplebs.com 4 months ago

Same team brotha, same team. But yes there would need to be compromise on both sides. Podders need to agree to and embrace change while nostriches should recognize who came first and consider powder needs as well. This is how we win together.

1 replies ↓

StevenB 4 months ago

GitHub

podcast-namespace/docs/examples/value/blip-0010.md at main · Podcastindex-org/podcast-namespace

A wholistic rss namespace for podcasting. Contribute to Podcastindex-org/podcast-namespace development by creating an account on GitHub.

All of this metadata is being sent to the podcaster in the keysend TLV record. It's a lot more than a message. With keysend being no longer widely supported, as we shift to lnurl, the podcasters would still like this metadata, and we're discussing how best to get it to them in a way that is private if they choose to keep their stats private, or if listening data should even be private.

1 replies ↓