Live data from Hacker News

The audacity of Apple Podcasts

basta.substack.com

11–20 of 327 posts

Re: The audacity of Apple Podcasts

#11
post #2

I deliberately don't use any of Apple's services, even though I own an iPhone. The only thing I use is the App Store, and even then I'm a minimalist as to what I install. If I want to listen to podcasts, I use the VLC Player app, and grab the podcast from the Podcast's official site, and then use iTunes to transfer the .MP3 to VLC, over USB. Cause I'm oldskool like that. If the podcast in question doesn't have a site…

I appreciate the sentiment of not wanting to give into vendor lock-in for convenience but why manually download podcasts and go through the whole process when you can use RSS and ask podcasters to keep supporting RSS feeds? You get good ergonomics while still keeping the process decentralized and without vendor lock-ins?

I agree-- RSS feeds are wonderful. I just wish more podcasts kept a complete feed. I'm a "completionist" and it turns me off when I have to scrape episode archive pages to get download links for past episodes that have dropped off the RSS feed. That's the biggest barrier for me to start listening to a new podcast.

I own an iPhone but also don't use Apple's built-in functionality unless the feature supports standards-based services can self-host (CalDAV, IMAP, etc).

I pull podcasts into my forked version of tt-rss[0] and use a script to pull down the enclosures onto my local webserver. I play the episodes using Safari (which, admittedly, is a sub-optimal experience) on my iPhone. (In my dreams I'd write an HTML5 front-end to play episodes, mark them to retain after listening, keep bookmarks, etc...)

[0] https://tt-rss.org/

Re: The audacity of Apple Podcasts

#12
Perhaps there were special deals in place for high profile podcasts?

I’ve never used the Apple Podcast app, and only learned about the Apple only features while listening to John Carreyrou‘s podcast during the Theranos trial. They had member only episodes (paid) which were only accesible using Apple’s app, but they also had a public RSS feed which excluded those members only episodes.

Re: The audacity of Apple Podcasts

#13
Apple Podcasts does not have a silence-trimming feature, which is reason enough to not use it.

It would be nice if you could have a single podcast RSS backend with multiple client apps, like you can with text RSS.

Re: The audacity of Apple Podcasts

#14
I listen to hours of podcasts each day (dog-walking, walking, running etc) and am fully immersed in the Apple ecosystem, but the Apple Podcast app is a turkey. Shallow feature set, bugs that never get fixed and an environment that doesn't evolve. It's software that can only be developed by a company that hates its user base. Ugh. I've been using and loving iCatcher for years [1].

[1] - https://joeisanerd.com

Re: The audacity of Apple Podcasts

#15
> You could sign up to allow Apple to host your show and its audio (for a cool $20/year). In exchange, you could charge a subscription fee to your listeners... If you host your show with Apple, the only listeners you can have are folks with the Apple Podcasts app... The audio will be protected with DRM.

The author presents this as "audacity" and bad... but doesn't it make perfect sense? If you're charging a subscription fee then it makes sense that the podcast lives in a walled DRM'ed garden. Also, if Apple is hosting it for nearly free ($20/year is nothing), why would you expect Apple to make it available to competing podcast apps? If you post something on TikTok it doesn't show up on people's Facebook feeds.

Apple isn't taking away self-hosted RSS podcast feeds. It's presenting a separate paid subscription experience within its Podcasts app. No "audacity" about it. If you don't want that as a creator, don't use it.

Re: The audacity of Apple Podcasts

#16

> You could sign up to allow Apple to host your show and its audio (for a cool $20/year). In exchange, you could charge a subscription fee to your listeners... If you host your show with Apple, the only listeners you can have are folks with the Apple Podcasts app... The audio will be protected with DRM. The author presents this as "audacity" and bad... but doesn't it make perfect sense? If you're charging a subscript…

This service doesn't give podcast hosts a way to retrieve their own material. It doesn't inform them that they'll be completely locked into Apple's service. If creators were aware of this upfront, then sure, I'd say "just don't use it" too.

Re: The audacity of Apple Podcasts

#17

> You could sign up to allow Apple to host your show and its audio (for a cool $20/year). In exchange, you could charge a subscription fee to your listeners... If you host your show with Apple, the only listeners you can have are folks with the Apple Podcasts app... The audio will be protected with DRM. The author presents this as "audacity" and bad... but doesn't it make perfect sense? If you're charging a subscript…

[deleted]

Re: The audacity of Apple Podcasts

#18
post #3

"Under the hood, Apple stopped having each device request a copy of RSS feeds." Yes, because this was creating DDoS levels of traffic to podcast hosting providers. Now Apple simply pings madly away at all known podcast RSS feeds and updates clients when there is a new episode. What would be far greener -- and efficient! -- would be for them to get on board with PodPing[1] to not only deliver feed updates much faster…

> creating DDoS levels of traffic Author here. This has never been a problem, both in terms of volume and cost. I host ~0.25% (maybe more? I haven't checked recently) of all podcasts listed on Apple and up to a few years ago, I wasn't even using a CDN. Two Heroku dynos at ~$250/mo (25 customer subscriptions today) running a Python back-end with no caching at all was able to keep up without trouble. In fact, the only…

The entirety of all the podcasts on iTunes/Apple Podcasts RSS feeds downloaded is around 200-250GB across the 2.5M+ pods. Hosting the RSS feed should be an easy task. Add in caching via ETag and server-side (host the feed as a static file, only re-render when user updates something), and your server load goes down drastically.

It gets a bit complex if your hosting company supports dynamic audio/ad insertion depending on how you accomplish that, but as far as retrieving the RSS XML feed, that has no impact.

Re: The audacity of Apple Podcasts

#19

> You could sign up to allow Apple to host your show and its audio (for a cool $20/year). In exchange, you could charge a subscription fee to your listeners... If you host your show with Apple, the only listeners you can have are folks with the Apple Podcasts app... The audio will be protected with DRM. The author presents this as "audacity" and bad... but doesn't it make perfect sense? If you're charging a subscript…

This service doesn't give podcast hosts a way to retrieve their own material. It doesn't inform them that they'll be completely locked into Apple's service. If creators were aware of this upfront, then sure, I'd say "just don't use it" too.

Why would there be any expectation that a podcast distribution service should also serve as a private file archive? And why would podcast hosts even need to retrieve their own material?

If there are podcast hosts who don't hold onto their original audio files they had before uploading them, then what are they thinking? That's like sending a project to a client and then deleting your own copy of it.

I understand that the author tries to provide an "import from Apple Podcasts" service for convenience, but that's merely a convenience. It really shouldn't be too hard for a podcaster to just re-upload their original audio files and descriptions to a new service. Nobody's "locked in" to anything here as far as I can tell.

Re: The audacity of Apple Podcasts

#20

> You could sign up to allow Apple to host your show and its audio (for a cool $20/year). In exchange, you could charge a subscription fee to your listeners... If you host your show with Apple, the only listeners you can have are folks with the Apple Podcasts app... The audio will be protected with DRM. The author presents this as "audacity" and bad... but doesn't it make perfect sense? If you're charging a subscript…

> Apple isn't taking away self-hosted RSS podcast feeds. It's presenting a separate paid subscription experience within its Podcasts app. No "audacity" about it. If you don't want that as a creator, don't use it.

It sounded to me like the audacious part was that they don't make it clear that, once you sign up for this service, your users cannot get your podcast in any other way than using Apple Podcasts, and you will never be able to change that. The audacious part is this:

> They say that your podcast will be available to listeners on Apple Podcasts, but they don’t explicitly say that your podcast won’t be available to anyone else. When you upload your audio, they say it will have DRM, but they don’t make it clear what the consequences of this are. They tell you your show won’t have an RSS feed, but they don’t tell you what you’re giving up by not having one. This is predatory.

Which, I agree with the author, is a really, really wild thing to do, which few companies could think they'd get away with. You can just imagine a PM saying "ayy, they don't like it? screw 'em, we're Apple!"

Post reply on HN