Access to YouTube API Services disabled due to inactivity

  • Resolved mvanleeuwen86

    (@mvanleeuwen86)


    3 years, 11 months ago

    I just got the following e-mail out of nowhere:

    “We’ve identified you as an owner or creator of one or more Google Cloud Platform projects which have been granted access to the YouTube API Services. The following projects have not accessed the Services in more than 90 days, and their API quota has been revoked in accordance with the Terms of Service.

    If you plan to resume use of the Services, you can request quota using the form linked below.

    REQUEST QUOTA”

    I found a previous support topic for this plugin and it stated that it was because of the cache, i.e. video’s are cached and no calls are made to the YouTube API after that. That’s nice and all, but this is the first e-mail I got from Google and I’m already past that point.

    See for yourself where they send you to request quota: the quota form.

    There are 30 questions on this form, some of which I have no clue what they even mean. On top of that, at the end they request the following:

    “Send documents (e.g., design documents, etc.) relating to your implementation, access, integration and use of YouTube API Services by each of your API Client/If the API Client is not accessible publicly, please upload a detailed screencast of each YouTube API Service functionality and YouTube data, content and information as displayed on, or integrated into, this API Client.”

    Yeah, that’s going wayyyy too far for me. Do you, as the plugin maker, have a solution for this problem which many other users at some point will also have?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    3 years, 11 months ago

    ppffff … guess I’ll have to add some logic to ensure cached data gets updated very (2-3) month(s) or so :-/ I’ll put it on my todo list (as part of a rewrite of LYTE).

    Thread Starter mvanleeuwen86

    (@mvanleeuwen86)

    3 years, 11 months ago

    Yeah, probably! Their demands for API usage are starting to border on crazy. Is there anything I can do until then? For example, can I close the project & start a new API project for the exact same website? Or will the website now be on some kind of blacklist for the YouTube API?

    Basically, I want to keep using the plugin without having to start a whole legal ordeal/vlogger-like experience just so they can understand I’m a “user of …” and not “a creator of … “

    Deslaw

    (@deslaw)

    3 years, 11 months ago

    I received the same message today and don’t understand why. The API key should be getting traffic as people are using the Youtube embeds on my websites that the key is being used for.

    Is there any way I can artificially create traffic?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    3 years, 11 months ago

    I’ll see if I can add some simple logic tomorrow/ the day after (will be in the Github version first and foremost), I’ll ping you when it’s time to test (indeed with a new API key)! 😉

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    3 years, 11 months ago

    OK, small change committed, can you download https://github.com/futtta/wp-youtube-lyte/archive/main.zip and replace the current version of WP YouTube Lyte with it?

    You’ll probably need to create a new API key, but once you added that things should start working again an LYTE should update all cached YT API reponses if they are older then 2 months.

    That way YT should see more activity while results are still cached (to avoid having to request the data for every page visitor which would slow things down).

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    3 years, 11 months ago

    any feedback @deslaw and @mvanleeuwen86 ? itching to push that release button on wordpress.org to ensure every user has this fix .. 😉

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    3 years, 11 months ago

    Well, I was to eager, so I released the update 🙂

    Thread Starter mvanleeuwen86

    (@mvanleeuwen86)

    3 years, 11 months ago

    @optimizingmatters created a new API key, cleared the cache, etc. after installing the update and everything seems to be working fine now. Obviously, we won’t know for sure until after the cache clearing moment 2 months from now haha, but so far so good! Thanks a lot!!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    3 years, 11 months ago

    You’re welcome, feel free to leave a review of the plugin and support here! 🙂

    groeten uit België,
    frank

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Access to YouTube API Services disabled due to inactivity’ is closed to new replies.