August 1st the YouTube v2 API is no longer available. The videoProvidesCaptions assessment relies on this API and now no longer works because of it. The problem with switching to v3 is that it requires authentication with a Google account. I'd propose that we remove the YouTube test from this assessment for now.
Considering we're looking into a more modular approach to Quail already, I'd suggest creating a separate repo for Quail tests that require signing in with a Google account. We've previously talked about using different Google APIs in Quail as well, so it would make sense to have this YouTube test be part of that.
mlewand
commented
9 years ago
August 1st the YouTube v2 API is no longer available. The videoProvidesCaptions assessment relies on this API and now no longer works because of it. The problem with switching to v3 is that it requires authentication with a Google account. I'd propose that we remove the YouTube test from this assessment for now.
Considering we're looking into a more modular approach to Quail already, I'd suggest creating a separate repo for Quail tests that require signing in with a Google account. We've previously talked about using different Google APIs in Quail as well, so it would make sense to have this YouTube test be part of that.