Yeah probably, I think this is so a client is able to locate the corresponding RSS feed for all the content metadata, which is within the podcast namespace. nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2 Does that sound right? https://github.com/Podcastindex-org/podcast-namespace
I suppose this is a transitional period until everything becomes nostr native in the future? Not sure how the RSS/nostr relationship will wind up looking down the road. Could wind up being redundant/parallel systems? 🤷♂️
Here is a fountain example using the same `i` tag format: