Trying to handle Rate Limiting errors got account banned (I think) #489
Replies: 1 comment
-
Random twist: when the suspension first happened I sent an appeal in, but for whatever reason I never got any confirmation email / case number that they usually send. Waited a day and sent another one, and this time got the confirmation and that was the thread described in my original story. However, then yesterday evening out of nowhere I get a confirmation of the original appeal request? Was going to leave it, chalk up to something getting lost in transmission....but then I was like, what the hell, might as well restate my case. Guess what? They came back with "Sorry, it's unsuspended"!! "A little background: we have systems that find and remove multiple automated spam accounts in bulk..." Really? ¯_(ツ)_/¯ So now without any further information about if anything I did tripped it, I might be able to continue on.....even with the API key switching? Does anyone have any suggestions about how to manage the tweet load with delays other than what I've described? |
Beta Was this translation helpful? Give feedback.
-
I run a small but active bot account that posts regularly every day some news story updates/blog updates. Been humming along fine for years but of course some API changes recently on the platform and all of a sudden tons of 429 Too Many Requests errors etc.
It's not clear what rate limiting is exactly as understandably a bunch of API calls in a short time trips something, but also there's this data in the response about limit & remaining that seems to count down. With still having whatever remaining, I figured it was just the too many attempts thing. So balancing the load was the issue in my mind, not exceeding some kind of load. A "back off" type issue I thought.
I have a few other dev accounts/handles for some other bot projects and they aren't active right now, so I thought, they have x cycles available to them also. So to balance the load I authorized them to post on behalf of my main bot and generated corresponding tokens. To spread the load around a bit I set a timer to use different tokens overnight etc.
In my mind this should be fine because those other handles have available API slots and far as I understand there's no limit on tweets (I mean, this is at some point but like 50-100 daily tweets has been fine for years), so just controlling where they're coming from should be fine.
Within 24 hours the account was suspended.
An appeal for reinstatement was met with a straight "No, violation of terms" with no explanation or direction as to what rules were in violation. (tweet counts? rate limits?)
I understand they don't have time for this perhaps but it sure isn't clear what rate limiting is or why using totally authorized tokens to make calls, even spreading the load out to twitter's benefit, would be a bannable offense.
Not clear what I should have been doing otherwise since ideally I wouldn't be hitting the 429 Too Many... wall, but instead just I duno... collecting tweets together so I use 'less tweets'?
Kinda annoying when wasn't really engaging negatively with the platform and followers seem to appreciate the account/beneficial to the platform.
Beta Was this translation helpful? Give feedback.
All reactions