So you are saying , publish a podcast on #nostr - rss text fields as well as content ( a new event type maybe ) .... and then use npub.pro ( or similar solution ) to feed legacy rss clients .. eg Spotify or Apple ..if one wishes to ..

That way a podcaster also gets a nice home page on npub.pro , plus captures all the social interactions (on nostr) on the home page ..

Did I get it right ? Broadly ..

Reply to this note

Please Login to reply.

Discussion

you got it!

So essentially, we are building a nostr specific podcasting solution , that also feeds to the broader RSS community ..

The rss world may not need all the fields that nostr peovides ..such as digital identity of the publisher .. but in due course they will understand the importance of signing the podcasts ... because AI tools will create almost indistiguable replicas of popular pods .. imagine a #noAgenda show where Adam is actually an AI :-)

I think podcasters will want to use nostr because it will be incredibly easy to directly engage with their community on a level never before possible

That is when #nostr has a billion users .. yes obviously :-) .. but till then , we need to be compatible with rss .. just the way we cant claim to have an email solution without being compatible with say gmail !

yes absolutely. RSS is the core of what I'm building with nostr