I figured it was! nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 how would you prefer to see this become more nostr native?

Reply to this note

Please Login to reply.

Discussion

The episodes themselves should be nostr events.

Unfortunately and surprisingly there is no nostr-native podcast player.

Yet.

But they still need be playable on regular podcast apps !

Non-nostr proxied into nostr vs nostr-native proxied into non-nostr

By that I mean; you could create a nostr-native podcast and then have some service that generates an RSS feed that is playable in non-nostr players.

#nostr native and legacy compatible - is the way to go !

yes

#YESTR

#WHENSTR?

I barely use Nostr ever since stemstr died. I had hopes of media being taken seriously.

But all I saw was “v4v rules!” “More zaps”

Blossom is a step… but not what I had hoped for.

I just wish my rss was also a full website.

Npub.pro generates RSS suitable for podcast ecosystem, i.e. cd-demo.npub.pro

What if I already have a nostr:npub1pj3a304qsdh99yr5wkug75rfznr284fzy7zalfnuwkctwyye2djsae7des rss? Can I set my npub.pro site to intake that rss feed and display the episodes like it does in Citadel Dispatch?

Not right now. Maybe that rss feed could be converted to nostr posts which could then be displayed by npub.pro. There were some rss-to-nostr utilities, but not sure how well those work.

Surprisingly? Frustratingly!!! Is there at least an agreement on how it should be handled in term of events?