rich1.0Satosha (npub1tt…xm0da)https://yabu.me/npub1ttc8j3sx59d4vs0zt23r6p90fjcd040x3vgu4j68u44ydx8u4rzqkxm0danjumphttps://yabu.meAbsolutely - 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 !