My experience attempting to debug a freaking podcast feed reminds me of how far we as an industry need to go with regards to developer experience.
-
Show this thread
-
I don’t think any of the following commentary is unique to Apple, although they do seem to be notably below the AppAmaGooBookSoft bar for developer experience.
1 reply 0 retweets 13 likesShow this thread -
So the underlying problem is I changed something about my implementation, they became unable to parse my feed, and they delisted me from the main podcast discovery service. This was totally silent. No email, etc, despite them having it and it being in the (broken?) feed per spec
1 reply 0 retweets 9 likesShow this thread -
So after noticing this I log into Podcast Connect, whereupon I get the helpful message: This podcast is not in the iTunes Store. A technical error happened when downloading its feed, artwork, or episode files.
1 reply 0 retweets 5 likesShow this thread -
This is surprising to me, as people who use podcast clients written by companies who can write software continued interacting with the (previously working for years) podcast w/o incident, but maybe there is some fun parsing bug. Finding it is impossible with that error message.
1 reply 0 retweets 3 likesShow this thread -
I then go to their documentation about submitting podcasts and error states, and promptly wished I hadn’t. Their actual suggestion with regards to debugging feeds is to pass them through a 3rd party validator and pray, because they have no first party way to validate.
2 replies 1 retweet 6 likesShow this thread
(They do, of course; something needed to crawl my feed and try to download episodes. But because it is entirely opaque they hope that other software is broken in exactly the same way theirs is. Sadly, this is not the case.)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.