Hi there,
JSON and XML both run an equal risk of being wrong at the moment.
I'm taking a look at the issue [1].
Thanks;
– Matt Sanford / @mzsanford
Twitter API Developer
[1] - http://code.google.com/p/twitter-api/issues/detail?id=474
On Apr 23, 2009, at 11:45 PM, Malcolm wrote:
This is definitely not fixed. I was having this problem before on the
json side. Seems fine on the xml side of things. I suggest you try to
implement using xml rather than json.
On Apr 24, 1:45 am, Doug Williams <d...@twitter.com> wrote:
This is still being worked on. Follow issue 419 for status updates.
@dougw
On 4/23/09, Don Park <super...@gmail.com> wrote:
I don't think this is fixed, at least based on responses I am
seeing.
If it was fixed then cache/cluster issues are delaying the results I
am expecting. As to the value type, I am seeing following value of 0
instead of true/false.
--
Sent from my mobile device
Doug Williams
Twitter API Supporthttp://twitter.com/dougw
