Stream.twitter.com enhancements: implications and timeline

KBsystema · 2014-04-16T18:35:04.000Z

I’m also seeing this issue

DolarToday · 2014-04-16T20:11:20.000Z

Hi Matt! thanks for clarifying! I already told the developer of the library I use to update it as it will break after this change.

Thanks anyway!

KBsystema · 2014-04-16T22:53:01.000Z

Like @tomsoft, I’m starting to get Twitter stream errors: “Exceeded connection limit for user”.
Errors were not present before.

Please help!

sifferkoll · 2014-04-17T09:35:24.000Z

(As Matt said) It seams like twitter is no more sending complete tweets (but instead any amount of data it feels like at the moment…(no data seams to be missing though)), at least when using the AnyEvent::Twitter::Stream module. This in turn makes the JSON:decode_json function to fail since it needs to decode the full tweet. This will probably make som scripts to reconnect and reconnect, etc.
My quick fix is to comment out decode_json in stream.pm and patch the data together at a later stage before decoding.

SmeshKelsta · 2014-04-22T12:10:00.000Z

We’re seeing a similar problem with 420 “Exceeded connection limit for user” errors here. I posted a thread explaining the details a few days ago over at https://dev.twitter.com/discussions/27717

I’ve now tested that this is happening both with/without gzip Accept-Encoding headers.

We’re using Twython as our client library, which uses Python Requests under the hood. So it doesn’t look like we’re having any problem with the tweets being split across HTTP chunks. We don’t see any issues with JSON decoding the data we receive - just intermittent 420s on reconnections.

@mattklein123 - any suggestions as to whether the 420 problem is related to the change in HTTP chunking, or is some other unrelated change in the way stream.twitter.com is operating? Any help would be greatly appreciated as all our attempts to figure out from here what’s changed have failed so far.

Thanks!

gopalyadao · 2014-05-27T10:48:44.000Z

Facing same problem i prayed to Twitter Support team please make simple way of solutions of all issues please
Thanking you
Gopal

glibc · 2014-06-02T03:02:10.000Z

" HTTP ERROR: 401 Problem accessing /1.1/statuses/filter.json?track=happy reason: Unauthorized. " I’m running command on my pc, It commands offer to me Dev page(curl).
But I receive a error message. How can I fix it?

JoshuaJoejose · 2014-06-13T13:14:05.000Z

on the 9th of june i received an error (ERROR: HTTP/1.1 420 Enhance Your Calm) so i forwarded the error to the email provided by twitter, after some hours i received an email telling me that i have exceeded twitter rate limit as a result of that. Twitter has places temporary limits on actions that can be taken by both user accounts and applications. now the question is how long will this ban be lifted, now that is 5 days since i got this error.

here is my ref: System Reference: ref:00DA0000000K0A8.500G000000PD33R:ref

JoshuaJoejose · 2014-06-13T14:26:04.000Z

if any one knows how to tackle this error please let me know im working on my final year project hoping to submit soon and need the connection to get back to work(project) each day counts against me. once again i will be so glad if any one can help.

kevino · 2014-06-13T15:01:51.000Z

The rate limiting should be temporary. See the docs on rate limiting for streaming [1]

[1] https://dev.twitter.com/docs/streaming-apis/connecting#Rate_limiting

andypiper · 2016-06-23T13:46:16.365Z