I know that Twitter cannot reveal details of the anti-spam or anti-automation bots used to automatically restrict applications, and I also understand that it uses machine learning to discover patterns and evolve using that data.
However, other than the general rules outlined in the documentation, are there more specific guidelines that could be shared to help prevent legitimate applications from being flagged by the bots without giving away too much information about the bots’ internals?
For example, it seems from experience that an app that sends direct messages where some percentage of them link back to the same site can get an app flagged. What I’m looking for are general tips/guidelines like:
- Don’t send too many direct messages with links to the same site (whether a number of percentage of total DM’s sent by the app)
- Don’t send too many direct messages with any links (in general, to any site)
- Same as above 2 for mentions
- Don’t tweet the same link too many times (or too high a percentage of all tweets from the app)
- Don’t make a lot of requests while in a rate limit timeout
Now I know it will never be confirmed publicly (or privately for that matter) that there are apps that are whitelisted from being flagged by these bots. But I know this as a fact because implementing the same features as existing applications has lead to write access restriction while older apps are doing this on a much larger scale without issues. So I’m not requesting comment on other apps.
But, my request is really for more specific guidelines on things we can do to prevent getting restricted as little guys for whom whitelist or increased rate limits or protection from anti-spam bots is not given to?
Our application has features that could easily have problems if there are criteria like this that isn’t officially published and it would be tremendously helpful if some more specifc guidelines were made available.