- General Use of the Service—Permissions and Restrictions
YouTube hereby grants you permission to access and use the Service as set forth in these Terms of Service, provided that:
C. You agree not to access Content through any technology or means other than the video playback pages of the Service itself, the Embeddable Player, or other explicitly authorized means YouTube may designate.
F. If you use the Embeddable Player on your website, you may not modify, build upon, or block any portion or functionality of the Embeddable Player, including but not limited to links back to the YouTube website.
Circumventing the desires of the content owner to not allow in an Embeddable Player is also not necessarily a good idea and probably why this is in the TOS. I am going to assume that Invidio.us is not authorized by YouTube.
We have traced a bit of the issue for the Embeddable Errors as being a generic error thrown after other internal YouTube errors have been tossed. For example, our API key was recently shown to be over limits.
There was a PR submitted.
What will be seen if this Nightly Build is used (and once it folds into the stable) is:
[12-14-2018 @ 10:18:40.304 MST] [ERROR] [GetData()@YouTubeAPIv3.java:180] YouTubeAPIv3 Error: [Domain] usageLimits [Reason] keyInvalid
[12-14-2018 @ 10:18:40.309 MST] [ERROR] [youtubePlayer.js:746] YoutubeVideo::exception: This video is not allowed to be embedded (ID: vY_kyk8yL9U)
This way we know what is really an embedded error and what isn’t.