Hah. Is T logarithmic back-off in general, or is that 15/60 a reference to twitter, specifically?
-
-
Replying to @generativist
Yeah, just one of the Twitter endpoint limits and hugely variable amount of network data. But it could just as well be a logarithmic back-off if I check back on a Monday morning and realize that I put an exception handler in the wrong line of code - stranger things have happened!
1 reply 0 retweets 1 like -
Replying to @ColditzJB
Hrm. What library are you using?
1 reply 0 retweets 0 likes -
Replying to @generativist
I was half joking about the back-off issue. Using Twython with some custom streaming code built on top: http://github.com/CRMTH/RITHM/
2 replies 0 retweets 1 like -
Replying to @ColditzJB
Ah okay. I wrote this library sporadically over the past year. It's in a broken state right now -- I'm fixing it soon -- but if you were doing SNA, it's really useful in that it lets you aggregate accounts seamlessly to get around rate limits.https://github.com/jbn/brittle_wit
2 replies 0 retweets 1 like -
Replying to @generativist
I took a quick look at the code. That is a pretty slick idea - aggregating multiple users' endpoint limits. I imagine that it is still capped at the overall app limit, but should still result in more data coming in faster from most endpoints. Well played!
1 reply 0 retweets 1 like -
Replying to @ColditzJB
The app cap is pretty high. Without revealing how many accounts I have, I was able to cursory studies similar to this one...erm, very quickly. (Some of the async patterns in that repo are ugly AF though. Those got pulled out on my local branch.)https://dispatches.artifexdeus.com/who-follows-james-damore-7874104e81ab …
1 reply 0 retweets 0 likes -
Replying to @generativist @ColditzJB
They also made it clear in their docs at one point that they expected some people to use multiple client credentials to get around limits at one point. Not sure if that's still in there though.
2 replies 0 retweets 0 likes -
Replying to @generativist
A quick afterthought on this as I'm working with my API implementation, but still not using multiple user credentials... I can get some bonus API calls by alternating between OAuth1 (user calls) and OAuth2 (non-user calls), as they seem to count independently in the API limits.
1 reply 0 retweets 1 like -
Replying to @ColditzJB @generativist
Nevermind - I was wrong... the OAuth2 calls also deplete the OAuth1 calls... now testing the timestamps and figuring out if bonus API calls are at all possible in this kind of scenario. My foot is squarely in my mouth.
1 reply 0 retweets 1 like
It may have routed to a different shard? I got passed some lad-members-to-list limits by routing myself to the UK before. They don’t sync right away.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.