Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
twitter streaming backend is broken #57
the root cause here turned out to be pretty bad. user stream connections are failing with 401 Unauthorized. not sure why yet, except that we have 53 twitter accounts, which may be over the limit for individual user streams from a single IP (or whatever heuristic twitter uses).
same problem happens with a different twitter app key, so it's not that bridgy got blacklisted or something.
things i tried that didn't fix it:
at this point, i suspect twitter has a threshold of 50 user stream per IP. over that, they start blocking IPs. thanks to @bear for suggesting this in IRC. i'll probably switch to scraping for favorites. :/
here's the timeline, just for my own info later:
so, the 401s started immediately when i switched to api v1.1. i wasn't at 50 users yet, but the v1.1 limits may be different from v1. also, i assume twitter finally turned off the old v1 endpoint (/2/user.json) around feb 3 11:10am PST, but it doesn't really matter here.