Closed plonknimbuzz closed 7 years ago
Hi @plonknimbuzz,
You're absolutely on the right track, the setCount parameter does do what you want. Unfortunately, they have restricted this functionality to twitter accounts with special privileges, see here: https://dev.twitter.com/streaming/overview/request-parameters#count
You would deep to apply to the Twitter team to be able to use this functionality.
The general approach they recommend is to use a mix of the REST and streaming API if you want to backfill past tweets.
@fennb your answer very usefull for me. ok, i will mix REST API and STREAMING API. actually: i already doing it right now,
may i ask something more the doc said:
When reconnecting to a streaming endpoint, elevated access clients may include the count parameter to attempt to backfill missed messages ....
and you said
You would deep to apply to the Twitter team to be able to use this functionality.
the meaning is: i only can used this count parameter if i become paid client or using gnip, isn't?
thanks for your great work. Awesome
hi, sorry for my stupid question here. I read twitter streaming API, phirehose wiki and the whole source code and example. but i dont get my answer. And i ask this same question in stackoverflow but still didnt get answer until now. I need this answer before i go forward.
I work with REST API for a month. Now i decide to using STREAMING API. I try several experiment
The problem is, when my server down for certain reason or my console disconnected (need time to reconnect), i assume that i will lose some tweets (i have 40 keywords and more). is this right?
i use filter-track.php for experiment
i also read
so i change filter-track.php to
but i always face
thanks for any explaination.