StevenB on Nostr: All very valid points worth exploring. 1) Is there a way to get around sharing links ...
All very valid points worth exploring.
1) Is there a way to get around sharing links to a proprietary platform, and would the platform be interested in sharing those links? I suspect even nostr devs would prefer you use their app and are incentivized to share a link to a note that takes you to their app, podcast apps for sure are.
2) How else would search be done? The centralized registry is an issue, and one that is acknowledge and solutions are being thought about on how to remove needing an Index as a single point of failure/control.
3) Yeah, I'm not sure having a monolithic file is the best solution. I think it would be cool that each episode was it's own file, and it's doable, but highly unlikely with 20 years of precedence. Here's a super small feed that has links to three episodes that aren't in the feed itself, so it is possible. https://lnbeats.b-cdn.net/playlists/eeeb0e31-f3da-54f2-909f-4fd640c684cc.xml
4) That's an app design. But here's a link for you, you can listen to this single episode in which they discuss decentralizing the podcast directory, and you can choose the podcast player of your choice if you want. https://episodes.fm/1584274529/episode/UEMyMC0yMTA
5) Being tied to a single, specific DNS domain/server is problematic. It's a single point of failure/censorship. Having duplicate feeds on multiple servers is one way around this, very similar to how notes are stored on several servers.
1) Is there a way to get around sharing links to a proprietary platform, and would the platform be interested in sharing those links? I suspect even nostr devs would prefer you use their app and are incentivized to share a link to a note that takes you to their app, podcast apps for sure are.
2) How else would search be done? The centralized registry is an issue, and one that is acknowledge and solutions are being thought about on how to remove needing an Index as a single point of failure/control.
3) Yeah, I'm not sure having a monolithic file is the best solution. I think it would be cool that each episode was it's own file, and it's doable, but highly unlikely with 20 years of precedence. Here's a super small feed that has links to three episodes that aren't in the feed itself, so it is possible. https://lnbeats.b-cdn.net/playlists/eeeb0e31-f3da-54f2-909f-4fd640c684cc.xml
4) That's an app design. But here's a link for you, you can listen to this single episode in which they discuss decentralizing the podcast directory, and you can choose the podcast player of your choice if you want. https://episodes.fm/1584274529/episode/UEMyMC0yMTA
5) Being tied to a single, specific DNS domain/server is problematic. It's a single point of failure/censorship. Having duplicate feeds on multiple servers is one way around this, very similar to how notes are stored on several servers.