Yes indeed. It's a weird one.
Thanks for the feedback.
JS
On Jul 19, 4:36 pm, Taylor Singletary
wrote:
> Hi Developers,
>
> Along with a host of other issues we've been keeping you in the loop
> onhttp://status.twitter.com-- we have another issue that a number of you have
> pointed out:
>
> *
Any update on these messed up responses? I'm currently seeing users/
lookup.json responses get truncated if I request more than a small
number of users.
Hayes
On Jul 19, 4:28 pm, jsleuth wrote:
> Yes indeed. It's a weird one.
>
> Thanks for the feedback.
>
> JS
>
> On Jul 19, 4:36 pm, Taylor Si
+1
On Jul 19, 9:25 pm, Cameron Kaiser wrote:
> > Any update on these messed up responses? I'm currently seeing users/
> > lookup.json responses get truncated if I request more than a small
> > number of users.
>
> Ditto for direct_messages.json, although the main timeline is a bit better.
>
> --
Hi,
Thanks for the announce, I just wish I'd noticed it 4 hours ago ;(
'Tis indeed bizarre, and sends cURL loopy :)
Good luck!
- Paul
look forward to the fix soon Taylor!
-Raj
On Jul 19, 1:36 pm, Taylor Singletary
wrote:
> Hi Developers,
>
> Along with a host of other issues we've been keeping you in the loop
> onhttp://status.twitter.com-- we have another issue that a number of you have
> pointed out:
>
> *Our HTTP responses
Incase it helps anyone investigating...
users/lookup.json returns a complete response when I access it through
a web browser or fiddler.net
users/lookup.json returns a partial response when I access it
programmatically through a .NET WebRequest or through curl from an OSX
command line
I original
Except that I find status.twitter.com is the last place to look for
any information about faults.
We're getting the flak from users for around 3-4 hours before anything
relating to the issue appears on status, and the only official tweets
come from the twitterapi account which none of the users fol
> Any update on these messed up responses? I'm currently seeing users/
> lookup.json responses get truncated if I request more than a small
> number of users.
Ditto for direct_messages.json, although the main timeline is a bit better.
--
personal: http://www.
We continue to work on the issues and will be posting updates to
http://status.twitter.com as we have news. Please check there for the most
up to date details.
Thanks for your patience and support as we work through these issues.
Best,
Matt
On Mon, Jul 19, 2010 at 10:08 PM, Jason LaFollette <
j
