I love RSS and Atom. I'm an avid user for everything, I will not sign up for an account for subscription to things, period, if there's not a feed to subscribe on my side I don't subscribe. It has enabled a permissionless model of publication and subscription to flourish on the internet. What I said above isn't to rip on it, I love it. (Thanks for the work you've done to further that flourishing.) But, the published works live at individual servers. It's identity is the URL at which it can be found. This means that it cannot be censorship resistant. A person publishing their work can choose to publish it in multiple places, but someone subscribing to one might not know how to find the other. This is why I say nostr can do everything RSS can do but in a censorship resistant way. The content is simply signed, where a user pulls it from is of no consequence. A publisher can put it at several relays to be pulled from, the user hardly notices if it gets taken down from any of them. If someone wants to be able to publish anonymously, and in a way they can't be censored, nostr is a dream come true. RSS is still cool, useful, and you're right about all the infrastructure. But this censorship resistance, you can't beat it. I exclusively publish what I want to publish with Nostr, the identity of this voice is the key that signed this message. I won't host my writings on a blog, because it requires identifying myself to a data center, and having to watch what I say to avoid my site being taken down or blocked or something else. You should know, I'm working (very slowly) on a piece of software that enables publishers to share multimedia content in a censorship resistant way. Once I have it working and published, which is hopefully soon if real life can get out of my way, your average person will be able to publish audio and video with ease in a way nobody can stop, and even offload hosting to a trusted provider at their leisure also very easily. It leverages existing protocols and does not require any new infrastructure. Right now, nostr publishers have to host media at a URL and it is not censorship resistant. This is a weakness, I hope my solution is adequate for people.

Absolutely - features are different .. in fact every rss client may offer different features just as Amethyst offers different features v/s Damus ! ..that said , I was talking more about the underlying philosophy - e.g. being able to get the content without having to subscribe (no KYC) . A website or podcast doesn't need to know who am I and where I am ! kinda .. Now here is the fundamental difference ... rss works on top of http(s) ..which means despite good intent (for anonymity of the subscriber), the construct is superficial .. means a hacker can find what I am listening to and where .. of course there are ways to protect but most users wont employ those tools .. http essentially drives centralization - as happened with the internet overall ... rss is kinda a sliver of goodness residing with in the pool of darkness :-) who is better than you to know how strong Apple and Spotify are despite all the good intent (of rss community) ... nostr (and bitcoin) is built on gossip protocol .. it obviates the need of central servers .. in that , relays are NOT servers . Server serves me based on my credentials stored with them, on the other hand , I can simply go to a relay and pick up what is mine - kinda like the difference between a sit down restaurant ( server) and a Chipotle ( self service) . Crude analogy but the point is in the "http world" a waiter (third party) needs to know what I ordered and where I am sitting (location) .. in "nostr land" all that information grab by middle men is removed by design .. In addition , what relays store is not the content .. it is simply the rss style fields .. a specific set of fields for an event type ... Thus nostr is simply a better core tech ... that said .. a podcast wouldn't be called a podcast if it didn't support billions of existing user .. we may call it a nostr-cast but that is a totally different product ..albeit a better one but without any user :-) .. just the way I would not call it an EMAIL unless it supports all the smtp and pop based email clients ..including mut :-) So the path is to build a better solution on #nostr and make sure it is backward compatible ... not only for podcast , but for email too .. and many more great tools crippled by http ,,and eventually the entire internet .. Disclaimer : My technology interpretations may be wrong for lack of research on my part ! This thread has ton of great devs to correct me !