Thank you Andy for responding. We have reviewed the policies about how often (falling within the account limits) statuses can be done and programmed based on those numbers. Even when doing so, we were write restricted on the app.
We tried to explain that an end user’s token/secret would not write/post more than 7 times within a 15 minute window, when the policies dictate that a user’s statuses/update is allowed 25 posts within a 15 minute window. But we were told it’s “too aggressive”, even when it fell within the policies set forth by Twitter.
We have also reviewed the policies closely regarding automation and spam as defined in the Twitter Rules
We tried to get a response from Twitter that would help us to adjust our coding that met the requirements as Twitter saw fit, even though the existing code still fell within the limits of what Twitter states in their policies. But the ticket got closed out and we couldn’t reply any further to it.
When you mention “aggressive repeated postings” does that include retweets as well? If different people have scheduled the same retweet using their own individual token/secret combo is that what you mean by ‘repeated postings’ - or do you mean the same post on different accounts? Because our system allows people to schedule retweets.
We just wish someone from Twitter would take a moment to look a little deeper and see that we have set this up so that it meets the requirements of automation, meets the requirements of API limits per an individual’s account, meets the requirements of not being spammy content and help us to determine what is an acceptable rate limit. We have internal rate limiting in place that controls how quickly statuses/updates happen, and even at a 2 minute rate limit, which calculates to just 7.5 updates within a 15 minute window, it was “too aggressive”.
I ask that you not close out this thread until we could get some sort of definitive answer as to how quickly we can send out statuses/updates to a user’s account. We just want to get this resolved, that’s all.
I also wanted to mention that presently write restrictions are removed, and we’ve made some adjustments so that the lowest time interval is 10 minutes apart to help with not being so aggressive. But again, the policy says that 2,400 updates are allowed in a day, which calculates down to 25 statuses/updates are allowed within a 15 minute window, and we aren’t allowed to do 7 within that window without being write restricted.