At the moment I'm leaning towards that it's retarded to try to replace the existing RSS infrastructure. (I'm willing to be convinced otherwise)

RSS is Rock Solid. It's been time tested, battle hardened and it just works.

The argument that having to have a server to host one's feed is somehow difficult or out of reach for most folks is ridiculous. There are currently 4,370,848 feeds that say otherwise.

Why re-invent the wheel?

Granted there are some things that nostr can do that RSS can't and vice versa, but the RSS spec is very flexible and extensible. After all that's what the podcast namespace is all about.

We can find ways that make RSS and nostr play nice with each other but to try to replace RSS seems like folly to me.

Reply to this note

Please Login to reply.

Discussion

It's not replacing RSS, it's still an xml feed, like it always has been. It's just adding a redundant delivery mechanism. If your http server goes down, how does anyone get your feed? Wouldn't it be nice if there were other servers with your feed an app could go to get your feed in case your server went down. And your server would still send the feed over http like it always has. Doesn't replace anything, just gives you an additional means of distribution.