I'm interested in this idea. It's been knocking around in my head since January. You could even have your own relay which kinda represents an rss feed for your podcast
Discussion
True could be a relay per show. Or maybe there are podcast-only relays that host any shows. Then your podcast account connects to those relay and writes to them. Nostr podcast apps connect only to those relays and display shows and episodes based on info published there.
With the "relay per show" model you can manage subscriptions andsee your metrics. With an aggregate Relay they would have to build login management to keep everyones metric separate. Or they could just make it all public I suppose.
As a podcaster I wouldn't mind having my metrics public but in would like to control subscriptions
I can see that. Simplicity of managing subscribers by npub. Some people wouldn’t want to run their own and offload that responsibility. Aggregate relay could have slightly more complex account mgmt.
It could be both. Those who want to run their own and get all the metrics, can.
Im down to help test a prototype with our podcast if someone wants to hack something together
regardless of relay; it should not misuse currently well-known event kinds, this is an entirely different use case than 30023 and there's a specific event kind for exactly audio tracks