RSS is data. Nostr can be really good at relaying that data. Simple.
Discussion
Maybe I'm misunderstanding something, I'm still learning, but nostr still needs to store the data on yours or someone else's server? It's just sending the data over websocket instead of http? Like under the hood, it's still just clients connecting with a server, and the server sending and storing data?
I haven't worked with relays but yes, the main thing would be nostr relays would store the data and it would also be signed with an identity (pub/priv key pair). I think the Blossom protocol nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr has been working on is a really great way to marry the RSS & nostr experience, but I haven't had time yet to dive into it
Well, it's not *a* server. It's multiple servers according to the choice of the publisher.
So with RSS, the identity of the feed where the data is fetched from is a single server. If that server goes down the data being published becomes unavailable. Also, these servers are associated with real world identities.
With Nostr, the identity of the feed is the signature of the person publishing the feed. The feed can be fetched from any number of servers (relays) according to the needs of the publisher. You can publish your information/media/data to any number of them, and the likelihood that your published information becomes unavailable becomes increasingly low the more relays you publish to.
The difference that gives us censorship resistance is one server vs an arbitrary number of servers where the identity of the feed is not tied to any one.