Atom wasn’t being used in podcasting because it wasn’t supported by key podcasting platforms! I know from my research of multiple entities that tried to use Ato

Atom wasn’t being used in podcasting because it wasn’t supported by key podcasting platforms! I know from my research of multiple entities that tried to use Atom (since it’s obviously and unambiguously superior), particularly because of some things that claimed Atom was supported, but gave up because it turned out that even most of the platform things that claimed support didn’t actually support it, either at all or fully. As for things like JSON Feed, that’s never been a serious contender. This Apple Podcasts update saying “we no longer support Atom” genuinely surprises me, because when I looked a couple of years ago, as far as I could tell as an outsider with no access to any of their software, they didn’t support Atom, and never had. I’m not certain what you’re referring to as “the podcasting industry and standards bodies”, since I haven’t been paying attention to the space (a couple of years back it seemed a bleak wilderness). If it’s things like https://podstandards.org/ https://podstandards.org/, well, “Apple has created some thoughtful vendor-specific extensions to the RSS standard”… bleh. I cannot understand how anyone could have anything but scorn for the mess that is podcasting RSS. It’s shamefully bad, and the paragraphs there are rather baffling to me in their untempered praise for Apple and condemnation of (unspecified) others. As for their standard, they’re explicitly standards-washing certain Apple interests (though I will admit that most of the iTunes namespace stuff is generally useful), adding stuff that has no place in a “required standard” (funding!? And what happened to the <link rel> mechanism for some of that stuff, which would obviously be appropriate? There really looks to be a lot of poorly-thought out stuff in this).