[twitter-dev] Re: Since_ID and Search Problem

2009-11-04 Thread twitter-development 

I think a few people including myself have seen this. Best guess is
that it's a caching issue on the twitter server side. Here are some
other threads with similar issues:

http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e368ccc88f393885/a4f217e36b0d0657?#a4f217e36b0d0657

http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e6289b6439c1d26d/01bcafab31516f7a?lnk=gst&q=since_id#01bcafab31516f7a

http://groups.google.com/group/twitter-development-talk/browse_thread/thread/ed72429eef055cb3/23cf597ef030ca62?lnk=gst&q=since_id#23cf597ef030ca62



On Nov 4, 3:45 am, Spode  wrote:
> Hi,
>
> I've been noticing some strange behaviour since last night - but
> that's not to say it's not been going on longer.
>
> http://search.twitter.com/search.json?q=JournoTwit&rpp=100&since_id=5...
>
> Performing this search turns up 0 results when it should show 4.
>
> http://search.twitter.com/search.json?q=JournoTwit&rpp=100&since_id=
>
> Run it with no since_id and it works. Then straight away run the
> original query...
>
> http://search.twitter.com/search.json?q=JournoTwit&rpp=100&since_id=5...
>
> And you get the expected 4 results.
>
> What's going on?
>
> Spode (journotwit.com)

[twitter-dev] since_id and lang issues on search api

2009-11-02 Thread twitter-development 

Hi,

I've been noticing issues that when I add a language to my search api
request I don't always get back the proper data. When I hit the api
without lang=en I get the expected results. When I hit the api with
lang=en I get nothing back even though the tweets are marked as "en"
in the call that works properly. (I'm wondering if it's just co-
incidence and it's a bizarre caching issues because I see similar
behavior when adding/omitting different params from the request, the
fail safe seems to be to remove since_id all together) Below are a
couple wget's that show what I mean:

first request is "from:emantwitt17" since_id=5371461978 and lang=en
(get nothing back).
second request is "from:emantwitt17" since_id=5371461978 (get tweet
back at least one tweet that is marked as "en").

 BEGIN FIRST CALL **
[r...@hostname www]# wget -S -O - "http://search.twitter.com/
search.atom?callback=none&q=from
%3Aemantwitt17&since_id=5371461978&lang=en"
--18:43:46--  
http://search.twitter.com/search.atom?callback=none&q=from%3Aemantwitt17&since_id=5371461978&lang=en
Resolving search.twitter.com... 168.143.162.43
Connecting to search.twitter.com|168.143.162.43|:80... connected.
HTTP request sent, awaiting response...
  HTTP/1.1 200 OK
  Date: Mon, 02 Nov 2009 23:42:14 GMT
  Server: hi
  Status: 200 OK
  X-Served-From: sjc1c133
  Content-Type: application/atom+xml; charset=utf-8
  X-Served-By: sjc1h004.twitter.com
  X-Timeline-Cache-Hit: Hit
  Cache-Control: max-age=15, must-revalidate, max-age=1800
  Expires: Tue, 03 Nov 2009 00:12:14 GMT
  Content-Length: 970
  Vary: Accept-Encoding
  X-Varnish: 251678383
  Age: 0
  Via: 1.1 varnish
  X-Cache-Svr: sjc1h004.twitter.com
  X-Cache: MISS
  Connection: close
Length: 970 [application/atom+xml]
Saving to: `STDOUT'

 0% [] 0   --.-K/
s 
http://base.google.com/ns/1.0"; xml:lang="en-US"
xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/"; xmlns="http://
www.w3.org/2005/Atom" xmlns:twitter="http://api.twitter.com/";>
  tag:search.twitter.com,2005:search/from:emantwitt17
  http://search.twitter.com/search?q=from
%3Aemantwitt17" rel="alternate"/>
  http://search.twitter.com/
search.atom?callback=none&q=from
%3Aemantwitt17&since_id=5371461978&lang=en" rel="self"/>
  from:emantwitt17 - Twitter Search
  
  http://search.twitter.com/
search.atom?callback=none&lang=en&q=from
%3Aemantwitt17&since_id=5374137131" rel="refresh"/>
  2009-11-02T23:42:14+00:00

100%[===>] 970 --.-K/s
in 0s

18:43:46 (474 KB/s) - `-' saved [970/970]
 END FIRST CALL **

 BEGIN SECOND CALL **
[r...@hostname www]# wget -S -O - "http://search.twitter.com/
search.atom?callback=none&q=from%3Aemantwitt17&since_id=5371461978"
--18:43:51--  
http://search.twitter.com/search.atom?callback=none&q=from%3Aemantwitt17&since_id=5371461978
Resolving search.twitter.com... 168.143.162.43
Connecting to search.twitter.com|168.143.162.43|:80... connected.
HTTP request sent, awaiting response...
  HTTP/1.1 200 OK
  Date: Mon, 02 Nov 2009 23:42:18 GMT
  Server: hi
  Status: 200 OK
  X-Served-From: sjc1c136
  Content-Type: application/atom+xml; charset=utf-8
  X-Served-By: sjc1h007.twitter.com
  X-Timeline-Cache-Hit: Hit
  Cache-Control: max-age=15, must-revalidate, max-age=1800
  Expires: Tue, 03 Nov 2009 00:12:18 GMT
  Content-Length: 3316
  Vary: Accept-Encoding
  X-Varnish: 1742128020
  Age: 0
  Via: 1.1 varnish
  X-Cache-Svr: sjc1h007.twitter.com
  X-Cache: MISS
  Connection: close
Length: 3316 (3.2K) [application/atom+xml]
Saving to: `STDOUT'

 0% [] 0   --.-K/
s 
http://base.google.com/ns/1.0"; xml:lang="en-US"
xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/"; xmlns="http://
www.w3.org/2005/Atom" xmlns:twitter="http://api.twitter.com/";>
  tag:search.twitter.com,2005:search/from:emantwitt17
  http://search.twitter.com/search?q=from
%3Aemantwitt17" rel="alternate"/>
  http://search.twitter.com/
search.atom?callback=none&q=from
%3Aemantwitt17&since_id=5371461978" rel="self"/>
  from:emantwitt17 - Twitter Search
  
  http://search.twitter.com/
search.atom?callback=none&q=from
%3Aemantwitt17&since_id=5376548009" rel="refresh"/>
  2009-11-02T23:39:47Z
  15
  
tag:search.twitter.com,2005:5376548009
2009-11-02T23:39:47Z
http://twitter.com/emantwitt17/
statuses/5376548009" rel="alternate"/>
one more test of the api
one more test of the api
2009-11-02T23:39:47Z
http://s.twimg.com/a/1256928834/
images/default_profile_6_normal.png" rel="image"/>


web
en

  emantwitt17 (Emmanuel Job)
  http://twitter.com/emantwitt17

  
  
tag:search.twitter.com,2005:5376507702
2009-11-02T23:38:07Z
http://twitter.com/emantwitt17/
statuses/5376507702" rel="alternate"/>
retesting the api
rete