<oembed><type>rich</type><version>1.0</version><title>plantimals wrote</title><author_name>plantimals (npub1mk…0r4tx)</author_name><author_url>https://nostr.now/npub1mkq63wkt4v94cvq869njlwpszwpmf62c84p3sdvc2ptjy04jnzjs20r4tx</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>I am glad to have a reasonable conversation.&#xA;&#xA;I agree that the file format is not a problem. It successfully conveys the information we need. And indeed, it could be copied to multiple places, signed, etc. &#xA;&#xA;My point is that the same job can be done in a much better way if it were #NOSTRNative. One aspect is that RSS is a polling process where the file is downloaded at a regular interval and scanned for new contents. This paradigm is inverted by nostr, where an event can be published when there is new content, eliminating the wasteful traffic spent polling. &#xA;&#xA;You are right that relays still depend on domain names and servers. I just think that NOSTR will offer a better pathway to substrate independence and uncensorability.&#xA;&#xA;The pathway to a better version of what RSS is trying to accomplish will be found in using NOSTR directly, rather than reimplmenting some kind of identity and auth scheme for RSS.&#xA;&#xA;My guess is that most of the blogs and podcasts I follow will one day originate as NOSTR notes and get syndicated into RSS feeds by services offering such. I am working on just such a service myself. I don&#39;t want someone like you to have to choose. I want the content to be addressable in whatever format you prefer.&#xA;&#xA;&#34;The core ideas of nostr offers redundancy and identity, both of which can be adopted into the RSS feed. &#34;&#xA;&#xA;In this we are in close agreement. And thank you for your reasoned response. </html></oembed>