Mention YouTube API services and link to Google Privacy Policy #9339
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
🚀 Updated review app: https://pr-9339-badges-shields.fly.dev |
chris48s
approved these changes
Jul 1, 2023
|
Thanking you for taking on this effort @PyvesB! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been in discussions with the YouTube API Services team in order to get an API quota increase (see #8605). Unfortunately, there has been some push back, and the changes I made in #6304 are no longer deemed sufficient, even though the YouTube Developer API policy has not changed since then.
The latest response I got from the YouTube API Services team states the following:
To that effect:
The YouTube API Services have imposed a deadline for making these changes before July 7th, let's get this reviewed and deployed sooner rather than later.