I've noticed this before but always tried to deal with it as a bug on
my side. It is, however, now clear to me that from time to time
Twitter Search API seems to ignore the since_id.
We track FollowFriday by polling Twitter Search every so often (the
process is throttled from 10 seconds to 180
the cause of your issue?
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
[1] -http://groups.google.com/group/twitter-development-talk/browse_frm/th...
On May 15, 2009, at 7:50 AM, briantroy wrote:
I've noticed this before but always tried to deal with it as a bug on
my side
been
removed. Does that sound like the cause of your issue?
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
[1] -http://groups.google.com/group/twitter-development-talk/browse_frm/th...
On May 15, 2009, at 7:50 AM, briantroy wrote:
I've noticed this before but always tried
Matt -
Are we still on for 2pm Pacific? That is roughly 40 minutes out from
right now.
Please confirm for us we are still on (cause if we aren't I want to go
to the pool :) )
Thanks!
Brian Roy
justSignal
On Jun 12, 11:30 am, Matt Sanford m...@twitter.com wrote:
Hello again,
The
This just started today. It was working fine before and early this
morning.
I'm send in user updates from a widget via API. My server is
whitelisted and I've got a registered service. I get a HTTP 409 on
every attempt to submit a status.
Not sure why... You can try it here:
Sorry... these are HTTP 408s...
On Aug 6, 1:20 pm, briantroy brian.cosin...@gmail.com wrote:
This just started today. It was working fine before and early this
morning.
I'm send in user updates from a widget via API. My server is
whitelisted and I've got a registered service. I get a HTTP
They went away for a bit... and now not only am I getting 408's on
update but validate credentials is failing as well
On Aug 6, 2:56 pm, briantroy brian.cosin...@gmail.com wrote:
Now twitter search API calls are hanging... just stall until they time
out on my side
On Aug 6, 2:30 pm
:59 pm, Jennie Lees trin...@gmail.com wrote:
Getting the same thing using the track function of the API.
On Thu, Aug 6, 2009 at 9:43 PM, briantroy brian.cosin...@gmail.com
wrote:
Sorry... these are HTTP 408s...
On Aug 6, 1:20 pm, briantroy brian.cosin...@gmail.com wrote
I have a php/memcache based Twitter Throttle if anyone needs a
reference implementation. Just drop me an email at brian dot roy at
cosinity dot com
On Aug 7, 11:49 am, Greg Avola gregory.av...@gmail.com wrote:
This is happening all my applications.
Clicking Allow - just causes the App to
I'm actually clean - no problems for the last 2 days. I do, however
have my app just following all re-directs. If it would help I can pull
the follow on 302 and let you know what happens.
Brian Roy
justSignal
On Aug 9, 10:42 am, Dewald Pretorius dpr...@gmail.com wrote:
On Aug 9, 2:34 pm, Ryan
Everything below ONLY PERTAINS TO THE SEARCH API:
1) Since late last week I've noticed a significant number of 403
errors (403 Error from JSON: since_id too recent, poll less
frequently). These usually indicate I'm hitting a server with an
older view of the search index - since it thinks the ID
DEBUG: 06:02:45 PM on Mon October 26th Old max: 5182676703 New max:
5182676703
As you can see I'm getting 0 tweets and a new max_id... that isn't
good.
Please advise.
Regards,
Brian Roy
justSignal
On Oct 26, 12:47 pm, briantroy brian.cosin...@gmail.com wrote:
Everything below ONLY PERTAINS
.
Brian Roy
justSignal
On Oct 26, 12:47 pm, briantroy brian.cosin...@gmail.com wrote:
Everything below ONLY PERTAINS TO THE SEARCH API:
1) Since late last week I've noticed a significant number of 403
errors (403 Error from JSON: since_id too recent, poll less
frequently). These usually
I have a question about the streaming API.
I am currently whitelisted for the standard search API on several IP
addresses. I'd like to begin moving to the streaming API (at least to
test) but am blocked by the one connection per account limit.
Is there a way to be whitelisted (by IP or
/group/twitter-development-talk/browse_frm/th...
-John Kaluckihttp://twitter.com/jkalucki
Services, Twitter Inc.
On Nov 18, 2:46 pm, briantroy brian.cosin...@gmail.com wrote:
I have a question about the streaming API.
I am currently whitelisted for the standard search API on several IP
in question is: 174.129.117.107
It is (one of several) whitelisted under my username briantroy.
Please advise ASAP.
Brian Roy
602.325.3393
brian@justsignal.com
We are doing are last bit of testing before cutting over to the
streaming API and we see occasional errors:
PHP Warning: [json] (json_encode_r) double INF does not conform to
the JSON spec, encoded as 0. in /root/src/justsignal-twitter-stream/
twitter-track-class.php on line 154
PHP Warning:
=andrew%20badera
On Sat, Mar 13, 2010 at 5:23 PM, briantroy brian.cosin...@gmail.com wrote:
We are doing are last bit of testing before cutting over to the
streaming API and we see occasional errors:
PHP Warning: [json] (json_encode_r) double INF does not conform to
the JSON spec, encoded
We seem to consistently miss replies to users using the streaming api.
Our methodology:
If one of our users specifies a twitter user name we both follow the
user (using the folllow= predicate) and track on the user's username
(using the track= predicate).
Our assumption was that this would get
Mark -
Two separate threads (one user is restricted track, the other is
shadow).
Track user/thread is running track=briantroy (along with 230 something
other terms). The Follow thread/user is follow=4246611 - which is my
userid (along with 60 something other user id's).
Both threads have
your account
and the time, in UTC, that you logged in the stream, I can look to see how
many limit messages we've sent to you.
-John Kaluckihttp://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Tue, Mar 23, 2010 at 2:28 PM, briantroy brian.cosin...@gmail.com wrote:
Mark -
Two
during this period.
Brian
On Mar 23, 4:05 pm, briantroy brian.cosin...@gmail.com wrote:
John -
We rarely get limit messages - and no, none have coincided with
missing replies. Our last limit message was yesterday at: NOTICE:
TRACK - NOTICE: Mon, 22 Mar 2010 22:52:28 -0400 Stream is limited
, briantroy brian.cosin...@gmail.com wrote:
John -
Here is a good example:
These two tweets came in 2 minutes apart from 2 different 3rd party
clients. We got one and not the other:
http://bit.ly/cG9emM(Got this one)
http://bit.ly/aFvimS(Not this one)
No limit messages, re-connects
23 matches
Mail list logo
