Yes, we're fixing that presently.

On Mon, Mar 9, 2009 at 15:53, feedbackmine
<[email protected]> wrote:
>
> Sometimes I got no result, sometimes I got same old tweets
> (1300721813-1300738909). It has been like this for a few hours.
>
> For example:
> GET /statuses/public_timeline_partners_nrab481.xml HTTP/1.0
> User-Agent: Wget/1.10.2
> Accept: */*
> Host: twitter.com
> Connection: Keep-Alive
>
> HTTP/1.1 200 OK
> Date: Mon, 09 Mar 2009 22:15:47 GMT
> Server: hi
> Content-Encoding: UTF-8
> Content-Type: application/xml
> Content-Length: 83
> Set-Cookie: JSESSIONID=19EBF930711384DEA614920DC9D6A213; Path=/
> Cache-Control: max-age=1800
> Expires: Mon, 09 Mar 2009 22:45:48 GMT
> Connection: close
>
> <?xml version="1.0" encoding="UTF-8"?>
> <statuses type="array">
>
>    </statuses>
>
> Is this a known problem?
>
> Thanks.
> feedbackmine
> http://twitter.com/feedbackmine
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

Reply via email to