“Valid” and “disingenuous” mean very different things. How would you feel about editing that README point to be explicit that you use an unofficialundocumented YouTube API?
For the record, I don’t think “InnerTube” would be considered unofficial, legally. It’s authorized by YouTube, since they made and use it internally. That’s the definition of “official.” This is a small part of why I think the wording in the TOS makes the TOS apply to “InnerTube.” What makes you think that it doesn’t?
The policy only applies to the API you can get “officially”.
Repeating this doesn’t make it true.
I don’t see the TOS saying it doesn’t apply to internal APIs, in fact it seems quite clear that it does. Let’s read a bit more of the TOS then, emphasis mine:
The “YouTube API Services” means (i) the YouTube API services (e.g., YouTube Data API service and YouTube Reporting API service) made available by YouTube including those YouTube API services made available on the YouTube Developer Site (as defined below), [omitted items (Ii)-(iv)]. By accessing and using the YouTube API Services, and in return for receiving the benefits of the YouTube API Services provided to you by YouTube, you agree to be bound by the Agreement (as defined below).
It says “including” the APIs you are calling “official” but nowhere does it limit itself to those. It says it applies to any YouTube API made available by YouTube… which the “InnerTube” certainly seems to fit.
Also, why do you keep putting “officially” in quotes? You’re not quoting it out of the TOS, the word “officially” does not appear in that excerpt defining the YouTube API Services. Do you have a different source that you’re quoting from?
The InnerTube isn’t the YouTube API, far from it. So it’s still valid.
“Valid” and “disingenuous” mean very different things. How would you feel about editing that README point to be explicit that you use an
unofficialundocumented YouTube API?For the record, I don’t think “InnerTube” would be considered unofficial, legally. It’s authorized by YouTube, since they made and use it internally. That’s the definition of “official.” This is a small part of why I think the wording in the TOS makes the TOS apply to “InnerTube.” What makes you think that it doesn’t?
The fact that it isn’t “the YouTube API”. The policy only applies to the API you can get “officially”.
Repeating this doesn’t make it true.
I don’t see the TOS saying it doesn’t apply to internal APIs, in fact it seems quite clear that it does. Let’s read a bit more of the TOS then, emphasis mine:
It says “including” the APIs you are calling “official” but nowhere does it limit itself to those. It says it applies to any YouTube API made available by YouTube… which the “InnerTube” certainly seems to fit.
Also, why do you keep putting “officially” in quotes? You’re not quoting it out of the TOS, the word “officially” does not appear in that excerpt defining the YouTube API Services. Do you have a different source that you’re quoting from?