#1

Hello! I just somehow could not find to contact Twitter developer support so I just write here. Starting from beginning of March our firehose streaming feed does not work any more. It worked before (i’m using some php library). Now script still works but I just do not get any messages from streams.

I’m filtering this firehose by user id-s. My account should have all the permissions. I feel that somehow internally in twitter.com something has changed but I just cannot understand what to change from my side.

Below is just a code what i’m using for tracking. This code was working before so it’s not anything to do with coding errors.

$sc = new MyUserConsumer(OAUTH_TOKEN, OAUTH_SECRET, Phirehose::METHOD_FILTER);
$sc->setFollow($followarray);
$sc->consume();

I hope some Twitter support sees the message.

Greetings
Toomas

#2

Hi @newsstation - Have you checked your authorization lately or any messages to the email address on the app owner’s Twitter account? You can check connection using twurl for example:

twurl -t -H stream.twitter.com -A "Accept-encoding: none" -d "follow=123456" -X POST "/1.1/statuses/filter.json" --unbuffered

#3

Hello! Thanks for quick reply. Technically everything works (also with twurl). But the problem seems to be that if my follow list is for example 4000 items long then I will see traffic but if my follow list is 5000 items long then no traffic is coming in any more. But my follow list is a lot longer than that. This large follow list has been in use for 5+ years and i guess internally something was capped in the beginning of March.

My Twitter account name is the same as forum name (if you want to check something from inside).

#4

The technical limit on statuses/filter with the follow parameter is an upper cap of 5000 user IDs. Depending on the specific IDs and their size, there may also be a cap on the size of the URL parameters that you are providing to the API.

#5

Hello! Thanks again for reply. I know about normal situation where 5000 is the limit. But our account has special status (it was called “shadow role”) so there was no limit. We went through reviews and whatnot. Using this account with the “shadow role” from 2010 and it worked till March day.

Greetings
Toomas

#7

Thanks for clarifying. You’re referring to an access option that was for private functionality, and which is no longer available. Please use the regular streaming endpoints and available options. If you have a requirement to track larger numbers of terms or users, then we have an enterprise PowerTrack product which may better suit your needs.

#8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.