I’ve been using Overcast (on IOS) for years and for the most part love it, but having explored the privacy reports in its settings, I’m wondering if there is any way to actually do something about all the trackers podcasts are using these days.

I’ve tried blocking the specific trackers with AdGuard DNS, but when I do that, the podcast refuses to play at all.

Using a VPN helps to obscure some of the gross invasively personal dynamic ads, but is pretending I’m in Amsterdam really the best I can do? Doesn’t feel like it’s actually addressing the problem :/

  • Oliver Lowe@lemmy.sdf.org
    2·
    1 year ago

    I know where you’re coming from. Right now the way many of podcasts’ audio files are served is via HTTP CDNs. The podcast client fetches the RSS feed, then fetches the linked-to audio file. The VPN, as you say, just changes the source address of that request.

    What we could work on is reducing the number of requests to those CDNs.

    One idea: A service which serves a mirror of the podcast feed and audio files. Users would need to manually enter podcast feed URLs into their client, rather than select the podcast from a convenient in-app search. You’d have to trust the service operator isn’t collecting and sharing its usage data.

    Going further, we could use Bittorrent to distribute episodes between mirrors. Mirrors could subscribe to a RSS feed of torrents for particular shows.

    I could imagine some community-run effort in this space.