Speech to text audiofile limit request [closed] - google-cloud-speech

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 12 months ago.
Improve this question
Our company using speech to text API for making searchable audiobooks. Some of our audio files reach 20 hours, but as we noticed, the basic limit for using Speech to text is 480 minutes.
Please let me know how can we request to enlarge our limit to 1200 minutes?

You can request a higher limit from Google. The process is described here, and there is an interactive guide here.
To request a higher quota limit by using the Google Cloud Console:
Go to the Quotas page:
On the Quotas page, find the quota you want to increase in the Limit name column.
You can use the Filter search box to search for your quota.
Select the checkbox to the left of your quota.
Click EDIT QUOTAS. The Quota changes form displays.
In the Quota changes form, enter the increased quota that you want for your project in the New limit field.
Complete any additional fields in the form, and then click DONE.
Click SUBMIT REQUEST.
While the above procedure applies to most quota increase requests, you
might encounter one of the following exceptions:
In some cases, the Google Cloud Console redirects you to a separate form to request an increased limit. After you submit the
form, Google Cloud acknowledges your request by email.
Some quotas cannot be updated using the Google Cloud Console. If you find that you cannot change a quota from the console, request the increase from Cloud Customer Care. The Billing team does not handle quota limit increases.

Related

Difference between Twitter's user and application rate limits

The Twitter's API documentation is quite confusing for me.
It says that rate limits for statuses/update are 300* per user; 300* per app
Does it mean that each of the users can do 300 tweets/retweets? Or it means that all users can do 300 tweets/retweets together per time window?
Thank you for attention!
This announcement may help to clarify the information. At an overall application level, it is not possible to post more than 300 Tweets and/or Retweets inside that window, regardless of the number of users, unless you've applied for elevated access to the API.

How to protect google analytics mobile tracking ID from hacking [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
Is there any solution to protect google analytics from receiving fake information from Spammers ? The problem is anybody can send information by knowing tracking id.
I found the following solution, filter domain. But that's for web and how to implement for mobile app ?
https://blog.kissmetrics.com/protect-analytics-from-hacking/
Thanks
Visible Tracking ID
On a website you can right click, Show source but you can't on a mobile application. Therefore your trying ID can't be find from your clients application. Nonetheless, if your code is pushed to a public repository (Github for example) robots may find it.
Random spammers
Even if your trackingID is kept secret you'll have some bot spamming your account randomly (they try every possible tracking ID). Google added a tool to prevent this: go to Admin > View > View settings > turn on Exclude all hits from known bots and spiders. Then Google will automatically filter hits from the known fake domains.
Hostname security hack
Even with Google's automatic filter you may still see some spam. This can be fixed with what they explain in the link you provided.
In your article they create a custom dimension and use it to filter real data from spam data. You can also use this with your mobile application, the thing is, it does not need to be a host name it just need to be a string only known by you, its sort of a new secret added to your tracking ID (which should already be secret).
This works because bots can handle the try of every trackingID but they can't try every custom dimension with every possible value, it's too much work for them.

Google Books API rate limiting information?

I can't find any information on rate limiting with the Google Books API. I'm interested in doing ~300K total ISBN queries to retrieve lists of book categories, and I want to throttle my requests to stay under their limit. I have a developer API key, but not OAuth. Does anyone know what the rate limits are for the Google Books API, or at least have a ballpark?
According to this post,
https://groups.google.com/forum/#!topic/google-api-java-client/_TFuPpAKSew
Around 100k/day is not a problem.
You can also request more quota, if you need it, as follows:
Go to the API Console (https://code.google.com/apis/console)
Select "Quotas" on the left navigation pane.
Click on the "Request more..." link and submit the form.
"Your quota request should be processed within a few business days at most. Basically we want to hear from our developers so we know what type of traffic they are sending, so we can add resources to accommodate them as necessary. But from what you describe, perhaps 100K/day, should not be a problem."

An effective way using Disqus API

Background info:
iOS app on iOS 7.0+
Moqod iOS library ( https://github.com/moqod/disqus-ios )
App would load comment for any time user view the wordpress post detail.
Case Description :
This question is mainly raised by the 1000 requests limit per hour from Disqus API. For my app, I load the comments when user views a post detail. If 1000 is the limit, it will be reached if there are more than 1000 people view post detail within a hour. I believe it is really easy to reach. Try to think about if there is 1 000 000 users are using my app. if 1% of the pool view posts within an hour. It will be broken.
I haven't count it takes extra call to obtain the thread ID which used on posting message and the number of posting comment.
Question :
How do people usually design an iOS app would satisfy the above case ??
Or Do I have an incorrect approach of using the Disqus API ??
Please kindly help.
Thanks

Is there a way around twitter's rate limit? A pricing plan perhaps?

I am working on a project which requires getting tweet and user information from twitter. I can't even test the current system because I keep hitting twitter rate limit. Is there any way around it?
Basic information that I am looking to extract from each status is:
Status text
User follower count
User following count
Retweet count
Geo location co-ordinates
I am using Twitter4J API to do this.
Any help will be appreciated. Thanks in advance.
EDIT
I am using twitter's search API to get list of tweets.
One option is to use a Twitter Data Reseller (e.g. GNIP) who can sell tweets.
Another option is to maximize your use of the API. Here are some tips:
Check Rate Limit Status for each API you're use to make sure you don't go over and when the rate limit resets (currently every 15 minutes).
Look at the parameters to make sure you request a count of the maximum number of tweets for that API. e.g. a count can default to 20, but you can set it to 200, depending availability and limits on the specific endpoint. This potentially reduces the number of queries you have to make.
Page your results according to the Twitter's Working with Timelines guidance. Use SinceID and MaxID to make sure you're only requesting new tweets. This could reduce requests by reducing the number of tweets you need (through increasing the opportunity to stay within max count) and reducing the number of requests by avoiding queries for tweets you already have.
Essentially, you want to examine endpoint parameters with a perspective for how to decrease bandwidth and reduce the number of queries you have to make.

Resources