Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Privacy implications of each person using their own YouTube (Google) API key #19

Open
Gitoffthelawn opened this issue Nov 25, 2019 · 4 comments

Comments

@Gitoffthelawn
Copy link

What are the privacy implications of each person using their own YouTube (Google) API key?

When everyone was sharing a few keys, if people were not logged in to Google, then I think the most Google could track was the calling IP address (and browser fingerprint, if not obscured). If the user used a different IP address, Google could no longer track them.

With people all using their own YouTube (Google) API keys, it seems like it will be trivial for Google to track people across IP addresses.

Is this correct? Is there anything that can be done to prevent it?

@elliotwaite
Copy link
Owner

Correct. If you visit a youtube.com URL and have this extension enabled with your personal YouTude Data API key set in the settings, Google will receive an API request that contains both your API key and your IP address, so they will be able to associate the two. If anonymity is a concern, then you probably want to avoid using this extension with your own API key.

The only potential solution that comes to mind is if you could somehow set up your network settings to make all your API requests (requests for URLs starting with https://www.googleapis.com) get routed through a VPN or something, but I'm not very familiar with this area of knowledge.

@FatOrangutan
Copy link

@elliotwaite Have you considered using Invidio.us' API? E.g. https://invidio.us/api/v1/videos/aqz-KE-bpKQ?fields=rating

@elliotwaite
Copy link
Owner

@FatOrangutan Thanks for pointing that out, I hadn't heard about invidious before. I added the option to use their API by setting the API key on the extension's settings page to "invidious", however, because their API doesn't allow for bulk video requests, and you have to request the data for each video one at a time, it is much slower than the YouTube data API. However, this does add an alternative for people with anonymity concerns.

I also opened a feature request for invidious to add support for bulk video requests (iv-org/invidious#936), which, if implemented, would probably make using the invidious API a very good alternative.

Thanks for the suggestion.

@SolveAllProblemsRightNow

google doesnt care, g has way more than enough data, they dont care about you

  1. did the steps
  2. looks you dont need cookies on for this to work
  3. looks like you dont have to be logged in
  4. now i can see how much quota i use, curious

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants