Stream Connection Problems

[hunterlarco]

Stream Connection Problems

[zane-programs]

Interestingly, this quirk does not just occur after restarts. In fact, I just applied for a new Twitter Developer account on my Twitter alt account, and I ran into the stream disconnect issue on my very first use of the new keys.

I don't think this is on @HunterLarco though; it seems to be a quirk with Twitter's streaming API itself. Alas, I'll be polling Twitter for now instead.

[zane-programs]

I can confirm that I am having the same issue. It seems to be due to ratelimiting on the part of Twitter. Has anyone else experienced this behavior?

[HunterLarco]

Unfortunately @zane-programs is correct. Twitter rate limits all streams such that if you're frequently connecting and reconnecting you'll run into a ConnectionException.

Note that:

Each app is allowed one connected client at a time. You can attempt reconnecting up to 15 times per 15 minute period. You can make up to 450 rule changes per 15 minute period.

and

To check connection limits response will return three headers: x-rate-limit-limit, x-rate-limit-remaining and x-rate-limit-reset headers. This is useful to understand how many times you can use the rule endpoint, and how many reconnections attempts are allowed for the streaming endpoint.

If your dev workflow requires several restarts within a 15min period you may want to consider streaming from Twitter with a different process which your binary connects to instead. EG: create a thin JS client that connects to twitter and proxies all streamed data. In fact, that might not be a bad thing to add to this repository as a utility if there's enough interest.