“Wherever you get your podcasts” is a radical statement
anildash.com
anildash.com
Given Apple's general money-grubbing ways (see: the App Store), this is somewhat surprising. Presumably the podcast directory product happens to be owned by someone in the org who has some idealistic commitment to it being open, and/or the overall podcast industry is too tiny for them to think it's worth the hassle to push monetizing it.
(Now Spotify's the biggest podcast platform, I gather, and I think we should all be glad that they don't have the power to just do unhindered monetization of podcasts because of Apple's counterbalancing them.)
Maybe Apple hosts it because it's a legacy thing that doesn't interfere with Apple-only podcasts.
Caught me somewhat by surprise one day when I walked past a hospital and got an ad in a podcast for that very hospital (GeoIP for my mobile IPv6 is correct at the zip code level).
In fact, Spotify even allows podcasts to deliver their own MP3s (if you meet the requirements for their "Passthrough" program), which gives distributors that don't want to use Spotify's ad platform more control and is probably a condition for them even listing on Spotify.
By default, and presumably also for old Spotify Connect devices that only support Vorbis, they reencode all files and cache them on their own CDN.
In what way does the ecosystem rely on Apple's infrastructure? Do listeners on Android, or even a third-party apps on iOS, use Apple's podcasts directory for search and discoverability?
The fact that Apple haven't attempted to squeeze podcasting is perhaps an indicator that the ecosystem doesn't really depend on Apple (and they know it).
Depends on which client you use. Google Podcasts has its own directory. However, it's approximately-true that any third party app on iOS / Android that aren't run by a big company (Spotify, Google, Amazon) use Apple's directory for their podcast-search. (Pocket Casts, Castbox, etc on Android all definitely use it.)
Or think about Cloudflare. When Cloudflare has an outage, it feels like half the internet goes down. There is no requirement for all these people use to Cloudflare specifically, but a sufficiently large portion of the market has converged on utilizing Cloudflare.
Yes, many third party apps use Apple's podcast directory. Probably many on Android.
The other option is https://podcastindex.org/
More interestingly, Spotify rose to second by investing a gazillion dollars acquiring both a bevy of software tools (Megaphone, chartable, anchor), entire production studios like Gimlet and shelling out huge sums to take the biggest shows like Joe Rogan and Call Her Daddy private so they were Spotify exclusive and no longer available via RSS. In the past few weeks, Spotify has formally admitted defeat and announced Joe Rogan and Call Her Daddy will go back to the public market.
https://overcast.fm/podcasterinfo
I’d definitely be interested in using an independent source for podcast search. (To help reduce the current single point of failure in Apple’s org chart).
edit: Oh someone in thread po-inted to a secondary directory
The iTunes API is poorly documented but completely public. No reason not to use it.
There's basically why. You can manually add RSS feeds to various podcast apps, but Apple just slurps up those same feeds unless not submitted for some reason.
Far be it from me to give Apple credit for altruism or openness, but this narrative isn't quite true. When the iPhone launched, Jobs and the execs at Apple envisioned that web apps would be the way the iPhone functionality could be extended. There was even a relatively straightforward way for web apps to be cached and saved on the Home Screen. The desire for compatability with open standards was even reflected in Jobs' open letter explaining why Flash would not be put in the iPhone.[0]
Public outcry for the native APIs along with prodding from other Apple execs led to the App Store becoming a thing.
[0] https://web.archive.org/web/20100501010616/https://www.apple...
Doesn't pass the sniff test, because
> Public outcry for the native APIs along with prodding from other Apple execs led to the App Store becoming a thing.
Apple's vision of web apps was as second class citizens to Apple apps. The outcry was because those web apps, despite caching and saving and other things could not and would not ever be able to do what an Apple app could.
Sherlocking/f.luxing/Dark Skying (maybe less so, the last) is bad enough as it is, but far worse when those as web apps could never do what an Apple app could (f.lux is a perfect example, there was, and I could never imagine a world where Apple would allow a web app to control color temperature on their phone).
The age of it is the why. Steve was far less focused on service revenue. Plus, podcasts sold iPods and iPhones.
It's because Apple was emboldened by the fact that the original June 2007 iPhone exceeded sales expectations of 10 million units without any 3rd-party apps. The App Store didn't exist until July 2008. In June 2007, consumers were getting in line to buy the so-called "Jesus phone" even though there were no 3rd-party apps ecosystem for it. (Look back at the hundreds waiting in line overnight to buy the first iPhone: https://www.youtube.com/watch?v=_iSE0bBgUsQ)
So, Apple rationally concludes that 3rd-party developers need access to Apple's customer base more than customers need access to outside developers. Back in 2008, the developers en masse could have revolted and said "fuck the Apple iOS SDK, fuck the App Store, and they can fuck off with their stupid rules and 30% fee" -- but they didn't.
Instead, developers grumbled and complained while they were submitting apps to the App Store. Developers -- via their actions -- keep signaling to Apple that Apple has the leverage and not the developers.
That's why you had 2008 articles and threads such as this:
- This Is Why iPhone Developers Put Up With All the Bullshit From Apple (daringfireball.net)
- 46 points by sant0sk1 on Sept 19, 2008 | hide | past | favorite | 23 comments
https://apps.apple.com/us/app/stardew-valley/id1406710800 $5
Combined revenue over all platforms: $300m +
in essence, this means that in order for developers to achieve negotiating power parity, they would need to form a cartel, (an illegal anticompetitive practice they would not be able to defend). As a result, Apple's negotiating power advantage is a matter of law.
While the iPhone was certainly interesting tech, that's not what made a bunch of devs learn Objective C. It was money.
That Apple has only lowered their fees one, one and a half times in that period is how we end up with all the grumbling we have today. but at the time it was much much better than the status quo.
Disagree there. Maybe to preload apps. But in all my Symbian dealings in Nokia-land, almost every app purchased was direct from producer, and pushed to the device by a sync cable, with zero revenue going to the carrier.
At the time I left the industry the carriers had gotten so bold, they were trying to go around Motorola, Nokia, Ericsson and friends and get white label phones straight from the people who manufactured these phones, like HTC (before anyone had heard of them). Then they would have made no concessions to the likes of Nokia to allow what to them would be considered side loading.
If the RAZR hadn’t been ridiculously successful, if the iPhone hadn’t kicked them while they were down, we’d be watching antitrust hearings to break up cellphone carriers right now.
No, they're not.
But AT&T didn't interfere with getting apps on a Nokia phone, be it Symbian or even the Java predecessors. They didn't insert themselves in the middle and demand 70% revenue like your claim.
I owned probably nearly a dozen separate Nokia phones (and maybe half a dozen Sony Ericsson) over the years on different carriers. Hell, I started with a 2110 (now I'm feeling sentimental, so looking over a list: 2110, 6110, 8110, 8210, 3310, 6310, 7650, 9300 Communicator, 3250, N93, N95 before finally calling it quits... Damn.)
This seems apocryphal. Apple famously resisted apps and was dragged kicking in and screaming into supporting native applications.
I listen to podcasts all the time but: (1) never on an iPod or other portable listening device, (2) never find them on RSS feeds. I guess I could (YOShInOn looks at 3000 articles a day on my behalf, some of them are podcasts, I don't really have the right UI for queuing podcasts so I think about putting in a rule or some models for filtering them out) but I don't. In fact I was consuming and mastering "podcasts" before the iPod even existed and before there was RSS. It might well be that the median user has never "used as directed"
It's one of those cases where Apple makes up a word and it is like the way the priest transforms the bread and wine at Catholic Mass.
I find this surprising whenever I hear it. Ditto for spotify. I don't listen to a single podcast via either of these services. Some of the shows I listen to might publish on them too, but I'm subscribed elsewhere.
Most of the shows on spotify seem like the audio equivalent of shovelware anyways.
i recognize art19 as an amazon thing, and megaphone as a Spotify thing (or a thing which Spotify acquired?). i have no idea what any of the others are associated with. is one of those websites run by Apple?
Most (all?) feeds in there are not hosted by Apple. Many non-Apple podcast apps use this to power search and discovery features.
I do not know what you are talking about here. Apple has a podcast index. Podcasts do not need Apple's podcast index for anything. You can find a feed by going to the podcast's site and clicking on it, or googling the name of the podcast + rss. Or in any number of ways, really. Apple is one of many podcast indexes.
So no part of a podcast is hosted by Apple, unless the podcast is actually an Apple podcast.
Your question is the same as: "Why do you care if $YOUR_SEARCH_ENGINE (google, kaggle, duckduckgo) hosts a list of websites?"
The last search engine to host a list of websites was Yahoo!, and nobody did care.
The UX on the latter side is clearly superior.
in the past i've subscribed to a dead feed this way i think because the author changed who they syndicate through. i assume Apple's directory is maintained in a way that largely avoids this (simply by it being the canonical directory).
You could, but I suspect most people search in their podcast app. Which is where apples directory comes in.
Check out:
Listen Notes is an indie run service by a single person.
Not only does it host its own podcast directory, it has advanced search and many other nice capabilities.
The blog also talk about its tech stack.
https://www.listennotes.com/blog/how-i-accidentally-built-a-...
And you can even buy their Podcast Database
Or you can get one with 4M podcasts for free: https://podcastindex.org/
By then the RSS feed tech was already well established along with a few podcast software aggregators.
Apple did not invent or even have a choice.
apple's podcast directory is NOT required to listen to a podcast.
that said, most folks submit their RSS feeds to apple (and google play, etc)
When Spotify entered the market they paid a lot of money for exclusive content, but for the 99% of podcasters their interaction with the space was the same as Apple, submit your RSS and it serves it from your hosting. However, Spotify also bought two podcast hosting platforms: Anchor and Megaphone which ends up blurring that line a bit. As far as I know the Anchor/Megaphone hosted podcasts are not treated differently by Spotify, but that could change at any time.
The recent change from Google with the retiring of Google Podcasts in favor of Youtube Music is a tremendous step in the opposite direction. Youtube Music does NOT use the RSS based distribution method, with podcasters uploading their files directly to Youtube. Google even offers an RSS import.
From all of the metrics I have seen the above three platforms make up 80%+ or so of the podcast user base. So if they made changes to make things less open podcast creators would be forced to follow. Making it feel like the openness of podcasts is, at least in 2023, more of an illusion or an act of charity than anything else.
I already hated YT Music with a passion, but this makes me hate it even more.
In general, I agree with the sentiment here as well, I think podcast hosting and distribution will continue to increasingly be centralized. It makes me sad for the future of open protocols and an open web in general, but the factors are more economic than anything technical.
Sounds right on the nail head to me.
Roman empire, Pax Americana, Apple Podcast Directory. Birds of a feather :P
So the break is already happening in this world...
I guess I am not shocked that they would do something like that. I'm sure they claim that they do it for user experience or some such nonsense.
If they just served podcasts directly from third parties, third parties would be able at least in theory to push potentially malicious data to the Spotify app (and Spotify users' devices).
As for performance, if the third party has an outage, then it would make Spotify look broken. And who knows if the third party site can serve the traffic well enough for a good experience.
That said, they allow distributors to opt into "Passthrough" MP3 delivery to all modern devices (including browsers – just check the network tab in developer tools!), although it's not the default.
I see hope in the Patreon model. I don't mind paying a monthly subscription for a specific show if I get a locked down RSS link.
Though, podcasters on Patreon are getting high on their own supply, asking for way, waaaay too much. "Just" 5 bucks a month? For one show??? Completely out of touch. Come back when it's ad-free @ 50c, or less.
[1]: https://www.bbc.co.uk/programmes/w13xttx2/episodes/downloads [2]: https://podcasts.files.bbci.co.uk/w13xttx2.rss
https://podcastindex.org/ https://blubrry.com/support/podcasting-2-0-introduction/
https://soundcloud.com/user-773474262-525813292/the-history-...
As fragmented as open source efforts usually are, there's usually some network effect that lowers the risk for someone else to try it. Linux, LibreOffice, Lightttpd etc. With crypto it's winner-take-all.
It’s strictly a generalization of a block chain, since the chain is a tree. Also, instead of remaining anonymous and trying to scam pension funds, its creator named it after himself.
It’s also at least a million times more energy efficient, and has better support for federation (i.e., forks).
I really enjoy Podverse and real time transcripts and live shows and chapters, etc…
There are a lot of different reasons people can be fundamentally against crypto, and those reasons have been talked about in great depth over the last few years. Even if you don't agree with them, the various "anti" positions aren't that difficult to understand.
Lightning is nice but it's an unrelated project. Bitcoin itself is still fundamentally flawed and Lightning is basically syntactic sugar on the same decaying infrastructure. It "solves" the same problems Bitcoin did with a loosely agnostic framework around ... the exact same blockchain. It's the equivalent of getting a second-try on a test you failed just to write the same answer down.
And Lighting is one of the good ones. Other L2 chains range from "marginally exploitative" to "broken" to "outright literal scam" depending on the developer.
It "solves" that it is a predatory minefield of grifters, jangling keys of hope in front of people with little to lose?
Since when?
But centralisation has a way of creeping in, so I wouldn't be surprised if a platform came about to attract podcast creators with convenient revenue streams, in the same way Substack has for blogs. There's opportunity on the table.
I dropped my Spotify subscription when it started getting exclusive rights on podcasts. A worrying trend.
Or maybe the open podcast world has enough momentum to remain decentralised? What would lead to the practical decentralisation of video? Peertube has not made a dent yet.
To me, these no longer are podcasts, but are now shows hosted on Spotify. It's not different than any other talk show like Stern or some sportsball talking heads that are exclusive to XM/Sirius/ESPN/etc. It's just their shows don't have a "broadcast schedule". Maybe I'm just being too pedantic
While iTunes was required, it was free and there was no subscription or limitation on what you could sync to the device. Apple actually seemed to be generally anti-DRM at the time, launching the music store with DRM as an industry concession, but eventually removing it and even allowing users to download DRM-free copies of songs that were originally purchased with it.
> The name came from a freelance copyrighter who, after seeing the prototype, thought of the movie 2001: A Space Odyssey and the phrase "Open the pod bay door, Hal!"[2]
1: https://en.wikipedia.org/wiki/Backronym
2: https://www.pcmag.com/news/a-visual-history-of-apple-ipods
It’s like it came from some bizarro universe where only apple allows side-loading of content, but Spotify and YouTube do not (so they can take a chunk of your revenue, and censor/shut out competitors).
Feed burner tried. Spotify tried. I think podcasting is like blogs or email newsletters. There may be value in centralization (dev.to, medium, etc for blogs, MailChimp, substack, etc for newsletters) but there'll always be a space for you to own and run it yourself.
Critically, you can port your subscribers in each of these cases, unlike subscribers to a YouTube channel or a Facebook group. I think thats a correlary of Anil's point. It isn't enough for discovery to be open, you, the creator, need to own the means of distribution.
I read other comments about 'forever redirects' of the RSS feed if you leave a podcast platform and they're a bit worrisome, but I wonder if a year or two of redirect service would be adequate. Probably depends on the growth of your podcast. I think I might have updated a feed URL once or twice in the decade or so I've been a podcast listener. Still safer to set up a reverse proxy under a domain you control.
So the complexity of that is what makes it hard to go totally open in my opinion, at least from the creator standpoint.
That and the fact that there is just too much momentum with YouTube's audience volume, if your goal is viewership.
Audio is easy. Throw up an mp3 and you are done. The basic fundamentals of an audio client have remained largely unchanged since the invention of the tape deck. Video is a while different animal.
That being said, moving to an RSS based model for video would be pretty interesting. I just imagine there would be a lot of work on whatever system consumes those RSS files to make the video playable across the wide spectrum of video players.
* in ear devices
* vehicle audio systems
* phone speakers
* laptops
* mid-range home stereo systems
* high end home stereo/studio monitoring
is quite complex to get right, and generally you can't optimize for more than one at a time. That's even more so if you actually buy into the "immersive audio" hype, where playback is not even stereo anymore.or at least, so is the theory. but i see that most of the shows i listen to aren't available when i search them in Spotify. so i'm not sure how Spotify users interact with podcasts: do they use multiple podcast apps? does Spotify win only those users who previously weren't listening to podcasts (and so don't lose access to anything they valued when moving to Spotify for podcasts)?
As in, "Hey I just started a podcast on youtube!" but literally it's just a yt channel.
That's always worth a laugh. But I have seen actual podcasts that did this, too. They have a real audio podcast, but also put up a YouTube video of them making the podcast.
Do it live on Twitch. Publish video recording on Youtube. Audio as podcast. Transcript as blog/newsletter. Short snippets on Tiktok. Images with quotes on Instagram...
your podcast app should be able to subscribe to a Youtube channel. Youtube links that feed as a recognizable `<link rel=...>` tag, so even if your app doesn't index Youtube you should be able to just paste that 'youtube.com/@MyChannelName` URL into it and it'll figure out the actual feed URL from that.
those RSS feeds have been there for _ages_. i don't see their incentive to change it, unless maybe some competitor decides to scrape it and abuse it in some way which materially harms them.
i guess "reverse engineering Youtube's non-public player API" is that simple for the older videos in the feed? but the newer videos seem to be DRM-encumbered, so if the delayed feed bothers you, that's what yt-dlp is for, right?
FWIW i just gave my podcast client that feed URL and it worked exactly the same as any other RSS feed (except that the entries were delayed): i didn't know it was doing anything special behind the scenes. sure, it's non-standard, but that's not the only non-standard thing podcast apps already have to support. not everyone includes the right `<link rel="feed" ...>` tag on their website, yet for podcasts that do have their own website you can still paste their domain name and your app will magically figure out where the feed is.
gPodder's got an option to use yt-dlp instead of the above method, so i'll toggle that and see how well it works.
The only difference to an audiobook is that Podcasts are usually free and often (but not always) in serial format, but these boundaries are blurring more and more.
That said, I do definitely prefer open RSS distribution than something like "Youtube for Audio", and I'm glad there isn't any such thing (yet), but I wouldn't not call a podcast exclusive to Spotify, Apple etc. "not a podcast", just an annoyingly-distributed podcast.
If I were listening to a talk show on a pocket FM radio while in the gym, would you call that a podcast? What about a an audiobook on a cd player? How about a 30 minute audio recording my wife made to encourage me that I saved in my phone? If not, why not?
I ended up just setting up an endpoint that reverse-proxies the RSS feed served by the platform on my own domain.
Anil also mentions migrating from Mastodon, which has a similar problem: migration is a form of redirect, so the platform you’re migrating from has to continue to exist and not block your migration.
I did the same thing and eventually felt like it was too complicated to maintain a service just for that, so I switched to Bunny CDN and use a custom domain on Bunny to sit in front of the podcast host's RSS feed (just the RSS, not the actual episodes).
It works pretty well, but sometimes the caching does things I don't expect and new episodes don't appear in my player until I manually flush the cache on Bunny. I suspect I could do it more smoothly if I experimented more with Bunny's settings.
FWIW, when migrating from Mastodon instance to another, as long as both instances are online and in agreement during the migration, the ActivityPub protocol will automatically update any followers to use your new instance. The old instance could go down the next day and you wouldn't loose anyone.
However, the posts remain at the old platform - so they disappear if the old instance goes down.
And, of course, any hyperlinks pointing to the old instance will stop working when it goes down.
>Winer has been given "credit for the invention of the podcasting model."
>Winer's advocacy of web syndication in general and RSS 2.0 in particular convinced many news organizations to syndicate their news content in that format.
> Contrast this to other media formats online, like YouTube or Tiktok or Twitch, which don't rely on open systems, and are wholly owned by individual tech companies.
This is a strange argument, unless I just misunderstand. Are they intending to point out that there are more podcast services than video services? Is “podcast technology” different from an mp3?
In other words, is any 1+ set of media files on RSS a podcast?
I know a lot of people conflate "podcast" with "show." Just publishing a podcast feed of your songs might not be something you consider a show per se, and that's fair, but if it's a podcast feed I can subscribe to in my podcast player, then you are podcasting.
Seems a bit misguided, because unless you’ve been pointing to your own domain the whole time, you still depend on the previous platform to 1) offer this feature at all, 2) keep serving that 301 forever or your old subscribers will be lost. Do podcast apps permanently change the feed URL when they see a 301? Am I missing something?
It’s just companies being nice, because the incentives to not be nice haven’t showed up yet.
My feed reader will update the URL if the ending feed has a self URL that points at itself. But I don't think that is very common. In theory a permanent redirect should also be a signal to update the URL.
Being able to look up almost any podcast in any podcast app and find its RSS feed and subscribe to it directly without requiring any intermediary is a huge thing in this era of proprietary silos. That's the point he's getting at.
Apple could go rogue tomorrow and start rehosting all podcasts in its directory, which most apps depend on, and I would still have my list in Overcast to go and get RSS feeds direct from the source.
It’s not content distribution.
> get RSS feeds direct from the source.
But what is the source? Who is typically hosting these? Audio is easier to distribute than video, but aren’t most podcasts hosted on a handful of large services?
There are also a handful of essentially CDNs that host the .mp3 files themselves, but these are more or less completely interchangable. They're just infrastructure for hosting files.
The only player in town that seems to really make a dent in the openness is Spotify which have been aggressively buying out podcast teams and taking them off the open web, and that's one of the prime reasons I cancelled my subscriptions.
Then there's smaller losses like the BBC4 which made most of their podcasts have a 1 month delay vis-a-vis their own app. I have no interest in that. In effect, this just served to curb some of my compulsive newsy consumption. If something isn't important enough to still be heard a month later, maybe I didn't need to hear it in the first place.
Anyhow, I very much agree with the article and I'm happy someone made the point so much more eloquently than I've managed in my many debates about the matter.
But thanks for posting this! Occasionally, I can't find a particular podcast on my preferred site.
Yeah, this is what I thought. RSS will give a URL to a sound file, which is hosted by someone, somewhere. It doesn’t sound like there’s anything inherent to podcasts -- not even RSS even though it’s so ubiquitous -- which prevents the content distribution to be more centralized.
If a podcast recording is exclusively hosted by Spotify, that is where everyone gets that podcast; even if they got the URL for it elsewhere. It’s a bit like saying I get my articles from HN (disregarding that I don’t use RSS for it).
Top Podcast Hosting Companies by Episode Share: https://livewire.io/podcast-hosts-by-episode-share/
Top Podcast CDNs by Episode Share: https://livewire.io/podcast-cdns-by-episode-share/
The vast majority of podcast listeners subscribe a channel on YouTube, Spotify or Apple.
The vast majority of podcasts are served from similar centralized media companies.
Which is why "JRE is moving from YouTube to Spotify for $200 mil" is a thing. If podcasts were decentralized you wouldn't "move" from one content company to another.
(Spotify is trying to break the openness of podcasting but they mostly haven’t managed to do so, yet.)
At the end of the day, the podcast is served by one of these hosts, regardless of how it was discovered. It can be observed that they’re centralized when media companies make exclusive deals as Spotify attempted with JRE.
I wouldn’t disagree that podcasters are in control of distribution; that’s not actually exclusive with the distribution being centralized. The point I was making about the exclusivity deals is just that these platforms have started to try -- and likely will continue to try -- to entice some of the more popular productions into such deals, which would necessarily increase centralization if they go through.
It’s a cynical perspective so maybe best kept to myself but I see all the right pieces for a UX bait-and-switch. I suspect the parent commenter (to whom you asked the initial question) sees the same thing. I think it’s seemingly intentionally misleading to call this decentralized; like “that’s what they want you to think” as a paranoid way of putting it. Regardless of any motives, it seems to serve certain interests that this is seen as decentralized, and I don’t think they’re the interests of podcast fans. Food for thought, I guess.
Spotify signs new deal with Joe Rogan reportedly worth up to $250m
https://www.theguardian.com/technology/2024/feb/02/spotify-j...
Sounds like they got a deal.
Idiotic if you ask me. He’s just like any dimwitted everyman: every single pub in the UK has at least two Joe Rogans. I was sat with my back to one in a coffee shop the other day.
I mean, Android is still the largest platform in terms of users and it doesn't have a dominant podcast app. Spotify for a long time didn't offer podcasts and it still offers only very poor experience for podcasts.
It's really not. They bought his regular anti-intellectual dribble not because podcasts aren't decentralised, but the opposite: because the inexplicable draw of his particular brand of common-sense-insulting prole-feed might convince people that podcasts are something only big services can do, and to compete with other big services trying to do the same things. They want to give the impression that big content is "locked up" by services, when it's not.
In my estimation it hasn't really succeeded (in his asinine, consistency-free, bloviating world or anywhere else).
All they really did is associated their brand with his twaddle.
The sad part is this used to be completely normal. I remember browsing the web and most sites would show that little RSS icon in my browser indicating they have a feed available.
But people are happy to let companies like apple run their lives for them and decide what they are allowed to consume, so now we have to act like this perfectly normal and reasonable thing is special.
Yes, Siri. Thank you, Siri. May I watch another podcast, Siri?
there's the weird email newsletter format (say, Matt Levine's column) which completely ignores RSS, but that's probably tangential to the argument. the biggest offenders i see are less $BIGCO and more individual developers who roll their own blog and overlook RSS. but in that latter camp, every off-the-shelf publishing system or static site generator gets RSS support by the time i'm liable to encounter it in the wild, whether the operator knows it's there or not.
If I give you a podcast URL, you can play it in pocketcast, overcast, or even write a few lines of Python to download it and play it in an mp3 player.
You can play it using a web browser app by going to TikTok's website.
That's the point. Feature-wise, they're all nearly identical. With podcasts, you can just choose your client or even create your own with the same catalogue as any of the big players.
With short-form videos, you can't.
All the surviving shows have moved to YouTube. YouTube could provide the same sort of service, but it's not compatible with Google's dependence on ads.
It's akin to saying "wherever you get your music".
Even with physical media there's only so many big labels, and the rest is vanishingly small.
Who offers podcasts and operates them is so different from these in quantity that it makes a qualitative difference to the medium.
Sure, the streaming services lock you in, but that's part of the deal you make -- small sub fee, all you can eat. I'll make that deal.
But Apple, at least, also offers online PURCHASE of DRM-free audio files. I dunno who else still does (Amazon?), but I don't think any of those vendors are still trying to do DRM or lock-in for purchased music. It's just that, by and large, the mass market has moved to the streaming model instead of the purchased-music model.
Google was still selling MP3s not that long ago but they no longer do since they killed Google Play Music. Amazon also sometimes really nudges you to their subscription and you have to do some clicking around to find a way to buy instead.
If I follow a YouTuber, I follow that person's channel on a particular, closed, privately-owned platform. If YouTube decides to kick them out, I no longer follow them.
Yesterday I actually learned about an app trying to solve that problem [1] through an absolutely bad-ass video response by one of its creators to a takedown notice from Google [2] (the mic-drop part starts at 3:29)
A donation from Apple is not an open ecosystem.
> We do get most of our podcast data from Apple. We even use the same podcast ID as Apple Podcasts.
-- Podcast Republic
As soon as podcatchers offer the UX of being able to search for podcasts in the application instead of hunting down and pasting RSS URLs, then it makes sense to say "Wherever you get your podcasts" which means "Just search for our title in your favorite podcast app" which is what 99% of people want to do including myself rather than manage URLs.
It's basically the same as how, in the hey day of RSS, websites would show a bunch of RSS client icons to indicate "Yes, consume our feed in any of these popular RSS apps".
(That said, the centralization of podcasting and the death trend of RSS are worth talking about.)
What RSS is doing feels like something that should be done with just a few extra HTML tags, not a completely new format. But the idea of HTML as markup language feels kind of lost these days.
And boy does this bring back the memories of XSLT. I’m kinda glad I forgot about that abomination.
And if I put a web URL into my telnet client I just get a bunch of raw HTTP! Not everything on the internet is part of the web. There have always been other protocols: IMAP/SMTP for email, IRC for chat, NNTP for newsgroups, XMPP for instant messaging, and RSS for subscriptions.
The idea that everything has to be done over the web is what’s really undermined “the idea of HTML as a markup language”. If HTML is a markup language, why would you use it for all these other use cases, most of which were handled with much better performance on hardware from twenty years ago?
But have browsers ever widely attempted to be anything other than web browsers? A couple of vendors tried including RSS support at one point, but I don't recall it catching on across the industry.
Media (images, audio, video) browsers, maybe. Technically that is not HTML, but still rendered by most browsers. However, as that content can also be embedded in HTML, requiring browser support to be present anyway, it is a bit grey area.
Didn’t JZW once famously say all software grows until it eventually has an email client?
for blogging, RSS is a mechanism to transfer webpages. so shouldn't this apply?
Although you ultimately raise a good point. Most browsers do support PDF. That's the wide attempt to be something other than a web browser that I was forgetting about earlier. So, there you go, there is precedence.
Although there is still that pesky problem of most people not wanting to use RSS. Apple had good in-browser support for RSS there for a while but they found nobody used it. If Apple can't convince Average Joe to use something, it isn't likely anyone can. RSS has remained relevant for podcasts only because it has found a place in server-to-server syndication. Average Joe isn't visiting Harmony Harold's personal website to subscribe to his podcast either.
https://indieweb.org/sidefile-antipattern
But of course there were ideas to embed the feed data structure directly in HTML as attributes.
In the indieweb/microformats corner there is h-feed which could simply be extended with rel=enclosure links for an embedded podcast feed.
And more formal side you could use RFDa/Microdata and the schema.org vocabulary to annotate the HTML with the logical properties of a feed and podcast episodes:
https://schema.org/PodcastEpisode
Of course there aren’t any podcatchers with understand these vocabularies.
...
I’m a little bit torn. I love good minimal markup and have a soft spot for the idea of RDFa. An early 2000s idealist. But the real world is different.
Netscape’s original RSS came out of a clear need: the markup for table layout of the late 90s was shit and not generally parsable. Which is the same thing today: Today’s markup a wastelands of nested divs which are not generally parsable and often generated by tools nobody really has control over. Just today I had to wade through a Wordpress site builder plugin and its crappy visually generated HTML. That’s the majority of the web, sadly.
"Waking up... To keep Glitch projects fast for everyone inactive projects go to sleep and wake up on request."
Ok so this website appears to be hosted by microservice. "to keep ... fast for everyone." Is anyone else bothered by this line that we're conditioned to accept that microservices are always faster? In my experience, even without the cold starts, they are often slower than traditional VPS hosted apps.
Well then there's scalability... But looks like this still got the hug of death.
You might have seen an app hosted there: https://news.ycombinator.com/from?site=glitch.me
Or heard of its old name, Fog Creek, if you've been around long enough.
https://glitch.com/@glitch/fediverse-of-madness
Some fun stuff in here: https://glitch.com/@community/community-roundup + https://glitch.com/@community/
But I do assume they mean scalability as far as the content service goes.
The term microservice is a bit of a vague general term that just means "we thought about scalability" to me. It doesn't mean anything more than that to me without discussing it in detail.
I think the idea of a server being overloaded at the moment there's something positive like high demand is something deeply ingrained in folks psyche. Accordingly it gets brought up on every sales call (once we're talking to the technical folks) and executives love to say "micro services".
It's not really about microservices, and it's not implying they are fast. You could have this message about any kind of resource, it only means the service is trying to keep it cheap.
I do wonder why a static site like this couldn’t just be put somewhere always-on, like github pages.
Don’t subscribe inside a major integrated streamer since that’s helping them own the entire ecosystem. If they can kill Patreon they can close podcasts.
The thing saving podcasts is that they are free. They continue to be ad supported or not monetized at all. But there is a path forward where they can be monetized in other ways and still maintain the openness they enjoy today.
[1]: https://www.amazon.com/Read-Write-Own-Building-Internet/dp/B...
Of course that, and the PodcastIndex[1] which saved me a TON of time not having to go find RSS feeds... But also gave me lots of podcasts that no one is necessarily looking for which I have to weed through at some point.
I think that the key to this model working is that the podcasters are not (necessarily) reliant on big tech. On twitch and youtube streams for instance, algorithmic ads are used mainly to reimburse amazon/google for their hosting services (+ a significant profit). Since a podcast is small in size and does not need to be streamed on-demand, hosting costs are negligible. It seems like this model could also be effective for websites, but it requires an actual human to find and vet advertisers. I'm not sure what the solution could be for sites like youtube where self-hosting content is a much higher barrier to most content creators.
Try saying "play breaking points podcast" to Google voice assistant. It worked a few times. Now it's broken beyond recognition
- goes to spotify, plays music
- "with Google podcast" plays an unrelated podcast called "breaking point" (singular)
- add "with Krystal and Saagar", plays an old episode of Joe Rogan
I have to pull over, find it manually and play.
But also, the ads sometimes have a human component to them. On networks like TWiT, the ads are all live reads. There’s variability to them, occasionally guests offer their opinion of them, etc. Sure, it’s still an ad, but it’s not as jarring as the one-size-fits-all creatives that get blasted into your ears and eyes until you’re sick of them.
But yeah, I'm fine with using the skip x seconds in my podcast app as well for now.
They are also dynamic based on geographic location from which you download, which results in drastically different ad loads based on where you live. This is probably one of the reasons that a sponsorblock-for-podcasts has not yet happened.
Like no. I will not go to some application with ads I cannot skip.
Podcasting has a special place in my heart.
My software reads RSS feeds and downloads the podcasts.
I never see a file on my phone.
I guess it's time to accept that I'm a regular listener and I'd be much better off with some semi-sane system.
The RSS feed still doesn't have ads last time I checked (at least for me, accessing from the UK), but now aggregates six-week-old political satire. I do have BBC sounds on my phone, but I never remember to listen to it. I always just go to my podcatcher out of habit, and end up listening to something else.
As soon as a podcast announces it is going platform-exclusive, the pipeline becomes extremely visible for everyone except those already subscribing via that platform.
What situations are you encountering this?
* Youtube Music (replacement for Google Podcasts) * Spotify * Apple
Every other podcast platform uses Apple APIs to get your podcast info, and it will be available on, for example Pocketcasts, as soon as it shows up on Apple Podcasts.
There might be a few other smaller players that you still have to specifically submit to, some of them have died off. The ones above will get you to the vast majority of listeners.
I mean, advertisers don't need to say "You can visit advertiser.com with whatever browser you use" but they can just say "advertiser.com". They don't need to say "You can visit us at Unnamed Road 23 by whatever means of transportation you use", but they can just say "Unnamed Road 23".
My mom wouldn't know what is a podcast nor could she fathom what is this "wherever" she usually gets them.
I don't think I know what is a podcast, really. Conan has a new podcast that I'd be interested but I noticed that I need a 10$ monthly subscription to get it. I listen to Conan's other podcast on Spotify, so it's not really available on "wherever I get my podcasts". Finnish Public Broadcasting company is so much into podcasts that they call all their radio shows "podcasts". They are not available on any 3rd party podcasting software and their own services do not offer any 3rd party podcasts.
To listen to "my podcasts", I in fact need several applications and some would require a subscription.
Podcast is still, after all these years a bit like multimedia CD was in 1997. You kind of know it's one after starting to use it, but it's mostly impossible to define it in a meaningful way.
If that's the case, then she cannot operate a TV or a radio either. If you have a Podcast app on your device, it's incredibly easy to find and subscribe to podcasts.
And before anybody says "She doesn't know how to install an app!" – she didn't know how to install cable either, a guy from the company did. And most people know how to install apps.
Presumably they don't use the phrase "wherever you get your podcasts" then? Because theirs is not available "wherever you get your podcasts".
> My mom wouldn't know what is a podcast nor could she fathom what is this "wherever" she usually gets them.
But this phrase usually used in a podcast. So I assume she wouldn't come across it then?
Not the case. I have never listened to a podcast (to my knowledge) and yet I hear this phrase all the time when podcasts are advertised, e.g. on the radio or TV.
but yeah, gnome and kde both have their official podcatchers ("Podcasts" and "Kasts" respectively), and there's a bazillion floating around on Github; i'm sure some of them are distributed to fdroid or wherever. if you don't care about syncing between devices, getting notifications for new episodes, etc, and aren't opinionated about the UI, anything you find with a non-zero install base should do the job. otherwise you just gotta try em out and decide for yourself.
On the page, the post title is "'Wherever you get your podcasts' is a radical statement"
If you submit to HN and the title is automatically edited (presumably to make it less sensational), but you feel it was improperly done, you can edit the title.
If I'd submitted this piece, I would have made sure the "radical" adjective was present.