And then name it RRSSS to make it very clear how simple it is?
Totally doable. Sign an event, but put the signature in the feed to prove ownership, upload the feed to multiple servers. If the signature is legit, the servers replace the feed with the updated one. Add a new tag so a podcast app know there's more than one server to pull the feed from, just in case the main server is down for whatever reason. No need to replace podcasting, just add some of the great ideas from nostr to make it better.
https://github.com/Podcastindex-org/podcast-namespace/discussions/686
Discussion
I'm partial to nostRSS, and then we can relabel the tags and make it real simple by adding more NIPS but not really organizing them in any coherent fashion, and then we can make up some arbitrary number like 33333, and because it's in a range, we know it's replaceable, but 33333 is only for episodes, 33337 will be for the podcast itself, and then we'll link the 33337s to the 33333s by using an array of [e] tags. Yeah, I think we can simplify it.
Oh, I thought of something else we can do to make it more simple. Let's use ids each time the feed is updated, something like 4e55ae60f5583112bb1e63c41b675bd72dd64ed6c6e680c78ba1896f70572051, but that number doesn't actually do anything, you can't really share it, you have to encode it using the super simple NIP-19 encoder. Then you can share this "note1fe26uc84tqc39wc7v0zpke6m6ukavnkkcmngp3ut5xyk7uzhypgsm2vk57" but it only works inside of certain apps. Like if it sent it in an email or text, they couldn't click it or anything, they have to copy and paste it into certain apps that know how to read it. Man, RSS is really complicated, but I think adding these changes may actually simplify it.
