Spencer on Nostr: On nostr relaying RSS data: Some say "with nostr we don't *need* RSS. Maybe, but we ...
On nostr relaying RSS data:
Some say "with nostr we don't *need* RSS.
Maybe, but we already have RSS. There are over 4.3 million feeds in the Podcast Index.
As a nostr dev, do you convince 4.3 million feeds to republish their data in nostr format? Or do you grab 4.3 million RSS feeds, build a web of trust within them based on what you want, and relay those without any other work needed to be done by the publisher?
I know what I'd pick.
Published at
2024-12-17 20:41:48Event JSON
{
"id": "f2e4921f1f3d9161105fa5f9e0853bfcf649b12e7ae8d8bbdf76cdf546a713ef",
"pubkey": "2321831583d871b7636468f67ff78068668e6eb3c9cdbb230a6d478e9866f2ed",
"created_at": 1734468108,
"kind": 1,
"tags": [
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "On nostr relaying RSS data:\n\nSome say \"with nostr we don't *need* RSS.\n\nMaybe, but we already have RSS. There are over 4.3 million feeds in the Podcast Index.\n\nAs a nostr dev, do you convince 4.3 million feeds to republish their data in nostr format? Or do you grab 4.3 million RSS feeds, build a web of trust within them based on what you want, and relay those without any other work needed to be done by the publisher?\n\nI know what I'd pick.",
"sig": "119e4147a40bb382efd5615f1c971a121632c52feb60245462e8d7cfbb1f64a6c0e8630e03ffb95b594d88982c778fa8ef51a196bdcfe9c31d5b58c3db7df8e6"
}