Post Aw3YIhJE7Wl6GjoR5U by podcastguru@podcastindex.social
(DIR) More posts by podcastguru@podcastindex.social
(DIR) Post #Aw3YIhJE7Wl6GjoR5U by podcastguru@podcastindex.social
2025-07-12T11:37:18Z
0 likes, 0 repeats
Currently being bullied by a podcaster because an ancient episode from their podcast (that's no longer in their feed) is cached on someones phone (new subscribers won't see it), and they are trying to get Apple to boot us of the app store because of this.On top of this (at least in their video evidence) the audio still plays because they haven't removed the content from where ever they are hosting it from.
(DIR) Post #Aw3YIih0yZNgYnwwnw by adam@podcastindex.social
2025-07-12T11:52:59Z
0 likes, 0 repeats
@podcastguru i can reset the feed in the index if that helps?
(DIR) Post #Aw3ZazdCpya4GFRgLg by podcastguru@podcastindex.social
2025-07-12T12:07:35Z
0 likes, 0 repeats
@adam Thanks Adam, but the feed isn't the issue, like every other podcast app, we don't nuke content just because it's no longer in the feed, that's standard practice. They are complaining because it's still playable in the app because the user cached it (just the episode level details with the item tag) previously and they haven't bothered to take down the audio content so the play link still works.
(DIR) Post #Aw5Y2HGnYQanC0lbPM by podcastguru@podcastindex.social
2025-07-12T12:11:27Z
0 likes, 0 repeats
@adam technically we do -try- to detect deleted content, so if a feed has an item before / after something (it has to be bracketed by later episodes) we do assume that item got deleted and we remove it from the cache, but in this case their feed only goes back to 2023, and the episode they are complaining about is from 2017! I have no technical way to purge a users cache in this case.
(DIR) Post #Aw5Y2InRsWItvZ3BwG by adam@podcastindex.social
2025-07-13T10:59:29Z
0 likes, 0 repeats
@podcastguru gotcha.