24 ms·
I have a related question. How do you bypass them in the context of an RSS reader/podcatcher? I was building a service to parse some podcast feeds into JSON, an
by ndarilek 8y ago
I have a related question. How do you bypass them in the context of an RSS reader/podcatcher? I was building a service to parse some podcast feeds into JSON, and noticed they were failing on NPR podcasts. Pulled up the URL fine on my laptop, but it failed in Hetzner.
Of course, it failed because it was getting some sort of GDPR page at the podcast feed URL. I'm wondering if there was some way around this, because it's not like podcatchers can opt into something via an RSS feed...can they? I'm pretty sure I passed headers only accepting feed content-types, but even that wasn't enough.
Sure I can host elsewhere, but I just didn't care enough about the project to do that. But if there's a way around this, then I might pick it up again.
- josh64 8y agoWe're getting the same issue in our RSS reader (Vienna RSS). Not sure how to deal with it currently.
- raverbashing 8y agoYeah, rss should be machine readable, that seems like a bug on their end
- zaarn 8y agoI ran into this issue with a few tumblr blogs I follow via RSS. The RSS reader (TTRSS) gained a sorta-unofficial plugin that would fake the GDPR consent cookie. I did contact support and they promised to fix this bug. Though overall, for your podcast it's a bug too. You don't need GDPR consent to display a RSS feed document at all unless you sell IP addresses to third parties.
- Rjevski 8y agoThat's a bug on their side. The RSS feed should not require any consent since it doesn't have tracking (I don't think you can even embed trackers in an RSS feed). If they want tracking they can link to outside pages in the RSS feed and put the consent notice on those before displaying the content that requires tracking.