I have a quick question regarding the rate limits for Twitter Favourites - specifically the GET favorites/list call. I built favourites.io to keep track of my favourites. It lets you search and organise your favourites.
Anyway, it works as follows:
You sign up and authorize the application
It imports your favourites (every 15 minutes it makes a call to GET
favourites/list and imports any new tweets that you favourited)
It uses the user's access token to make the call
When checking the log file I noticed that one of the import jobs failed for a particular user. The error was: "Rate Limit Exceeded".
My understanding was that an authorized user could make 15 requests in a 15 minute window (and each request could return a maximum of 200 favourited tweets)
My job was running once every 15 minutes, so I'm not sure why that user is getting the "Rate Limited Exceeded" error.
Why might this be happening?
Thanks in advance,
Ross
It really comes down on how you built your script. If you're doing the timer from your side, it might not coincide with the one Twitter has.
For example if you send 1st call at 12:00:00 PM there's some latency lag (minor) by the time it gets to Twitter let's say 12:00:02. Now twitter expects the next call no sooner than 12:15:02, but if you have the timer script running every 15 minutes from your side, it'll send the second one at 12:15:00 < 12:15:02 so twitter rejects your call.
I would say start increasing the timer by 1-3 seconds (1 to be liberal, 3 conservative) until you give some room for Twitter to get and process your request.
Related
I am using multiple platforms to run a business. I provide 14 tutorial videos to my users after they create an account. What I want is when user sign up, my system should send 1 video / day to that user. Like this
video 1 on day 1
video 2 on day 2
...
...
video 14 on day 14
I want to make a setup in zapier to do that. Zapier should send each video a day unto 14 days a user gets registered.
Can anyone guide me how I can Achieve that target?
It's possible with Zapier, but will use a lot of steps + tasks. You could make a many-stepped zap that is structured like:
New User trigger
Delay until "tomorrow" (Zapier translates this into the correct date at runtime)
Send email w/ video 1
Delay until "2 days"
Send email w/ video 2
etc...
This will work, but probably be too expensive (that's a lot of Zapier tasks). Instead, look into drip email campaigns from any of the popular mail-sending services (such as Mailchimp).
I'm not sure I've stated the title correctly, but I have what I think is an unusual issue. Not something I'm terribly worried about but curious. If I'm tagging this inappropriately I apologize.
I have a google ad running and track clicks using Final URL. So I track keywords, Ad_ID, Location, etc. Looking at the database I noticed that I am getting a hit on my website from what appears to be one user fairly regularly (sometimes minutes apart - other times days - 3200 entries) for the last 2 years, at least to when I started tracking this way. The entry shows the same keywords and the same location - which is local - a mobile device - but not an Ad_ID or a referring URL. I take the google info from the query string in the url so the query string would have to be the same every time.
I recently added a tracking cookie (long expiration) on the user end and this activity shows up with a different cookie value every time meaning either its either a different device or the device doesn't accept cookies. Each hit also starts a new session.
These hits do not show up as clicks on Google Ads so I'm not being charged, it also means that someone is not actually out there clicking on the ad.
I don't see where this is causing problems but am curious as to where this may be coming from. I don't know if there is a way to stop it.
So nothing critical but ideas on what might be causing this would be appreciated. I also get a ton of spam or bot hits on the site but that's a different issue.
Thanks!
The documentation says that an app can ask a User three times per year via SKSToreReviewController to place a rating.
Most suggest to save a variable in UserDefaults and call the function after a couple of uses. What happens if you call the function more than three times per year? Will the App Store just ignore the calls and after a year asks for a rating again or will you get some kind of error?
And what happens if the app has been updated (ie. a jump from version 1.0 to version 2.0)? Will the 3 requests be reset?
In short, you choose the appropriate time to display the alert, but the system will decide whether to actually show the alert or not. So don't worry about "over-calling" as long as you don't call it as a response to user interaction.
Although you should call this method when it makes sense in the user experience flow of your app, the actual display of a rating/review request view is governed by App Store policy. Because this method may or may not present an alert, it's not appropriate to call it in response to a button tap or other user action.
Highlight mine.
https://developer.apple.com/documentation/storekit/skstorereviewcontroller/2851536-requestreview
As for your second question, the only reference I can find regarding how many times it might be displayed is "3 times per year". It doesn't mention 3 times per app version or update. Use this API wisely.
I'm working on a mobile game with increasing daily bonuses based on the number of consecutive days they played (up to 7 days in a row before resetting). I'm looking to increase retention by using push notifications to remind players to log in for their Daily Bonus.
The support staff at our push notification service said this: "This is possible however we don't have any automatic tracking in place for this. It can be done with tags but you will need to add the logic in your app. You could do this by saving the last time the user used your app and then when they come back to your app compare the time. Each time they come back you can just increment your local consecutive days value and then set a tag to match."
If anyone could give advice on how to set this up that would be great. I appreciate the help.
I have been trying to create an app for my Twitter developer account. Everything has been going good for a while now but now when I create a new app, I get a "Rate limit exceeded" error. I think this error comes with the API but I am only creating a new app. Any idea why I might be suffering from this problem?
UPDATE: Bug seems resolved. I was able to create an App.
OP is creating an App and seeing this error in the Web UI. The App is used to get the required OAuth credentials. Only after you have those credentials you can start to use the API.
Apparently there is currently an error which prevents creation of apps.
Twitter acknowledged the problem and is investigating: https://twittercommunity.com/t/does-not-allow-me-to-create-a-new-app/32528/9
The HTTP Headers mentioned by DWRoelands are sent back when one is actually using the API and exceeding rate limits (as described in the document he linked)
You'll want to start here: REST API Rate Limiting
Definitely take some time to read and understand that document. It will help you a great deal.
The responses that you get back from Twitter contain headers with important information about your current rate limit status:
X-Rate-Limit-Limit: the rate limit ceiling for that given request
X-Rate-Limit-Remaining: the number of requests left for the 15 minute window
X-Rate-Limit-Reset: the remaining window before the rate limit resets in UTC epoch seconds
By examining these headers, you can help your application make smart decisions about how often it makes requests.