Yeah probably, I think this is so a client is able to locate the corresponding RSS ...

2024-08-08 18:22:39

Yeah probably, I think this is so a client is able to locate the corresponding RSS feed for all the content metadata, which is within the podcast namespace. merryoscar (npub1unm…d0j2) Does that sound right? https://github.com/Podcastindex-org/podcast-namespace

I suppose this is a transitional period until everything becomes nostr native in the future? Not sure how the RSS/nostr relationship will wind up looking down the road. Could wind up being redundant/parallel systems? 🤷‍♂️

Here is a fountain example using the same `i` tag format:

quoting nevent1q…cdvl
Great track! 🔥⚡️

https://fountain.fm/track/TkkuS3WcuzwEampdiezY

nevent1q…nkrq

Author Public Key

npub1j0shgumvguvlsp38s49v4zm8algtt92cerkwyeagan9m6tnu256s2eg9a7

Seen on

wss://relay.nostr.band

Show more details

Published at

2024-08-08 18:22:39

Kind type

1 Short Text Note

Event JSON

{ "id": "4ae8982e5e45be7bf71ac21f1d772b35a354fa112446a68bfb114fd5e8e02f39", "pubkey": "93e174736c4719f80627854aca8b67efd0b59558c8ece267a8eccbbd2e7c5535", "created_at": 1723141359, "kind": 1, "tags": [ [ "p", "e4f695f05bb05b231255ccce3d471b8d79c64a65bccc014662d27f0f7e921092", "", "mention" ], [ "e", "ce70a5d4eaae560e120900d217d2068cffadc3243c1d9b7d9a2356c3cbfb91f6", "", "mention" ], [ "e", "d92eb3fd17523d87f88d3d7855df281a5a3eda4265b6a757215f087311c69d61", "wss://relay.primal.net", "root" ], [ "e", "791e175e15415f4a1312020cc7cb1e581cbd28ae956d1b8f8fcea930dac3a8e5", "wss://relay.primal.net", "reply" ], [ "p", "6538925ebfb661f418d8c7d074bee2e8afd778701dd89070c2da936d571e55c3" ], [ "p", "2250f69694c2a43929e77e5de0f6a61ae5e37a1ee6d6a3baef1706ed9901248b" ], [ "p", "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322" ], [ "p", "93e174736c4719f80627854aca8b67efd0b59558c8ece267a8eccbbd2e7c5535" ], [ "p", "604e96e099936a104883958b040b47672e0f048c98ac793f37ffe4c720279eb2" ] ], "content": "Yeah probably, I think this is so a client is able to locate the corresponding RSS feed for all the content metadata, which is within the podcast namespace. nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2 Does that sound right? https://github.com/Podcastindex-org/podcast-namespace\n\nI suppose this is a transitional period until everything becomes nostr native in the future? Not sure how the RSS/nostr relationship will wind up looking down the road. Could wind up being redundant/parallel systems? 🤷‍♂️ \n\nHere is a fountain example using the same `i` tag format: \nnostr:nevent1qqsvuu996n42u4swzgysp5sh6grgeladcvjrc8vm0kdzx4kre0aeraszyrrtam5st3nvh0kwwuupx7jj775dyyl42gx2cce9gzusslyx8qqf5lxcdvl", "sig": "42051c8eba70277d0cf71af131952020567c80c3061713682c2db0b0e569829e76e5b067ad0969164a54203888ca8d3d58c06e4b766db55f840fb3b4df28d56b" }

JoshR on Nostr: Yeah probably, I think this is so a client is able to locate the corresponding RSS ...