Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a "back-up" for the Podcast Index #172

Open
atdrago opened this issue Mar 1, 2022 · 2 comments
Open

Create a "back-up" for the Podcast Index #172

atdrago opened this issue Mar 1, 2022 · 2 comments
Projects

Comments

@atdrago
Copy link
Owner

atdrago commented Mar 1, 2022

The idea is that this would serve as

  1. A way to patch common issues that occur within the Podcast Index. (truncated descriptions, erroring enclosure references, etc.)
  2. A sort-of internal cache against the Podcast Index.
  3. An internal way to reference podcast feeds and/or episodes. (This would help solve Add support for custom feed URL input, especially for those that exist outside the podcast index #82 )
@atdrago atdrago created this issue from a note in Podcasts (Future) Mar 1, 2022
@djdmbrwsk
Copy link
Collaborator

How would you know to make a patch? Just an ad hoc when-you-see-it type approach for now?

@atdrago
Copy link
Owner Author

atdrago commented Mar 1, 2022

How would you know to make a patch? Just an ad hoc when-you-see-it type approach for now?

Yea, it would be ad-hoc, case-by-case thing. For example, with enclosure URLs, we could perform an initial HEAD request and check that it responds with a 200-level status. If not, double-check the feed itself and make sure the enclosure URL is the same. If it changed, and a HEAD request responds with a 200-level status, patch it in our index. Open to other suggestions on how to do it though! I wouldn't want it to slow down page loads and it sounds like it very easily could

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Podcasts
Future
Development

No branches or pull requests

2 participants