Hi all,
I have a question regarding web traffic to the Twitter API.
My app allows users to block other users en masse, and currently deals with well over 1 million blocks and mutes per day. This would be larger, but the Twitter API is giving my app an effective bottleneck, because only one block or mute operation can be performed at a time (and so much of my server’s time is spent waiting for API responses).
At the moment I have tried to mitigate this problem by running several PHP threads in parallel, all making requests independently. Solutions I am investigating (in lieu of a mass-block API call functionality being put into the API) involve either using an asynchronous Twitter API library, or trying to restrict thread CPU usage: in either case, it would result in my server making very large numbers of API calls simultaneously for long periods from a single server.
What I’d like to know is what Twitter’s view is on this: would this be seen almost as a form of DDoS attack, given the sheer number of API calls involved from a single source? Is it against something in the rules (to the letter or otherwise) to make this many API calls at once?
There are no rate limit issues here, as each thread is calling on behalf of users with their access token and not via bearer token.
3 Likes
system
Closed
#2
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
