One problem podcasting has, and the Podcast Index is no different, is for it to be widely searchable, a directory is needed. That's what the Podcast Index is. They upload the database every Saturday for anyone that wants to use it instead of relying on the Index, but you'll always be 1-7 days behind the Index. The reality is though, most PC2.0 apps rely on getting feed info from the Index. One thing nostr may be good for is having several copies of the Index available so if one server goes down, the others are available as a back up. I don't know enough about nostr to say how that would work or if it would, but if any of you nostriches are up to the challenge, having the Index across several relays would be huge.

Here's the latest upload of the database. https://public.podcastindex.org/podcastindex_feeds.db.tgz

Reply to this note

Please Login to reply.

Discussion

There's probably a few ways of going about this. for publishing the database file you could use NIP-94 k:1063 events to build a directory of the database files https://github.com/nostr-protocol/nips/blob/master/94.md

You could also publish the file using NIP-35 and https://dtan.xyz to publish the file as a torrent

Then it would be cool to build a simple self hostable podcast index server that would listen for the events and automatically download the database and update

This would be super cool. especially if it was possible for the inexperienced people (like me) to use a Start9 or Umbrel to be part of the podcast index party even if we don’t necessarily want to host a public Nostr relay.