Privacy

31934 readers

644 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

Chat rooms

[Matrix/Element]Dead
Discord

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

Are there any privacy respecting podcast clients/methods? (lemmy.ca)

submitted 1 year ago by goji@lemmy.ca to c/privacy@lemmy.ml

24 comments fedilink hide all child comments

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 :/

you are viewing a single comment's thread
view the rest of the comments

[–] otl@lemmy.sdf.org 2 points 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.