I still stand my ground though its highly unorthodox to deprecate a feature rich & fully working API, in favor of a work in progress one.
For example, let’s take the “videos” APIs again.
The only “working” APIs associated with videos are now, for some reason, marked as “deprecated”, right? But there is actually nothing else that can be used.
So on paper, the only way to fetch VOD information right now, as we speak, is via deprecated APIs.
It’s just a really strange deprecation strategy. To deprecate an entire API version, when there isn’t actually anything else to substitute it with.
A software company doesn’t usually deprecate APIs until there is a clear path for their developers to transition away from it.
But Barry basically nailed it with this comment.
But since I read that Twitch wanted feedback, so there was my two cents.