You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I just have 2 questions before I jump into using this library (which looks quite nice):
The official Trends endpoint seems to be limited to Academic researchers/journalists, so I was just wondering how you get the json data? Is this a reliable endpoint that will be probably be available for a long time to come? Since there does not seem to be a key/secret per user, does that mean a user of this library is truly at the mercy of arbitrary and invisible rate limiting, which could be ended by Google without a whisper?
Secondly, while I understand that the sub-state regions available on the trends UI are DMAs, where to get a list of DMAs is not very clear to me (and, such list, would probably need to be well organized with relationships to the state/country obviously)
In your readme you have a link, unfortunately this link goes nowhere:
Hello, I just have 2 questions before I jump into using this library (which looks quite nice):
The official Trends endpoint seems to be limited to Academic researchers/journalists, so I was just wondering how you get the json data? Is this a reliable endpoint that will be probably be available for a long time to come? Since there does not seem to be a key/secret per user, does that mean a user of this library is truly at the mercy of arbitrary and invisible rate limiting, which could be ended by Google without a whisper?
Secondly, while I understand that the sub-state regions available on the trends UI are DMAs, where to get a list of DMAs is not very clear to me (and, such list, would probably need to be well organized with relationships to the state/country obviously)
In your readme you have a link, unfortunately this link goes nowhere:
I'm sure with enough searching I could find one (this is a good start) but do you have a go-to?
The text was updated successfully, but these errors were encountered: