I’m experiencing a weird issue with Twitter’s rate limiting. I’m using the REST API to make a single call to /trends/place (which works) to grab the top 5 trends in the US, then I start a connection to the streaming API through the Twython library. I’m using a single TwythonStreamer that connects to /statuses/filter and passes a comma-separated list of the 5 trends I identified as “track” argument.
This was all working fine a couple weeks ago until some colleagues I’m working with ran the code with the same credentials simultaneously, resulting in an increased number of 420 “enhance your calm” errors. To combat the problem, I replaced the actual streamer with a mock object that keeps generating mock tweets and connects to neither the REST nor the streaming API.
It’s been weeks since any of us ran the code outside of “mock mode” – but when I tried to connect today, I was instantly getting 420’ed again – surely something can’t be right here?
I’m happy about any hints on what could be causing this.