The iTunes namespace is Apple's API, not an open spec
Quote
you should think of the items namespace not as a namespace not as an open spec, but as an A API. The iTunes namespace is the API that you use to control
Episode 141: Boosting is Loving (episode page, opens in a new tab) 00:39:52 (play audio from this timestamp, opens in a new tab)
Speaker-labeled
Summary
Apple published the iTunes tags to control how feeds behave inside Apple's ecosystem and never promised anything beyond that. The industry adopted it as a de facto standard, causing conflicts like the iTunes block tag being honored by some and ignored by others. The only fix is a truly open namespace, and you shouldn't answer private APIs with more private APIs.
Also said
Episode 141: Boosting is Loving (episode page, opens in a new tab) 00:44:29 (play audio from this timestamp, opens in a new tab)
So there is a fundamental mismatch of desire and intent between the open podcast community and the actors within it. And Apple, the most dominant player in that community.
Speaker-labeled