That is a known caching issue.
On Mon, Jun 1, 2009 at 17:16, RC wrote:
> Can this also explain why on a few accounts I'm seeing a discrepancy
> between the number of ids in the following JSON versus what Twitter is
> showing when you see the account on the web? I have at least two
> accounts th
Can this also explain why on a few accounts I'm seeing a discrepancy
between the number of ids in the following JSON versus what Twitter is
showing when you see the account on the web? I have at least two
accounts that seem to be hung up in the 2,000 following/follower
hurdle. The JSON array on
Thanks!
On Jun 1, 1:12 pm, Doug Williams wrote:
> We're continuing to fight with the limits of MySQL scalability. This is
> contributing to problems with user related data such as social graph lists,
> which is resulting in 500s. Operations is working hard and focusing on the
> fix.
> Thanks,
>
We're continuing to fight with the limits of MySQL scalability. This is
contributing to problems with user related data such as social graph lists,
which is resulting in 500s. Operations is working hard and focusing on the
fix.
Thanks,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.
Seems to be working now. Would like to know why this might have been
failing though...
On Jun 1, 11:28 am, Trevor Livingston wrote:
> I said "tlivings" in the original message. That is the only user that
> seems to fail.
>
> Thanks!
>
> Trevor.
>
> On Jun 1, 10:49 am, Matt Sanford wrote:
>
>
I said "tlivings" in the original message. That is the only user that
seems to fail.
Thanks!
Trevor.
On Jun 1, 10:49 am, Matt Sanford wrote:
> Hi there,
>
> The rate limit returns HTTP 400, as stated in the documentation
> [1]. A 500 indicates some server-side error so knowing what use
Hi there,
The rate limit returns HTTP 400, as stated in the documentation
[1]. A 500 indicates some server-side error so knowing what user this
is for might help us find the root cause.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
[1] - http://apiwiki.twitter.com/Rate-limitin
