You could always append a timestamp to the text of the status you're
trying to post to differentiate it.
On Fri, Dec 12, 2008 at 09:53, LeeS wrote:
>
> You should know it also ignores updates through the Twitter site
> itself. As of now, our bot's updates haven't been accepted for the
> last ho
You should know it also ignores updates through the Twitter site
itself. As of now, our bot's updates haven't been accepted for the
last hour, so I logged into Twitter.com and tried to make an update
manually, but that also doesn't work.
Lee
On Dec 12, 10:24 am, LeeS wrote:
> Thanks Alex. L
Thanks Alex. Let me know if there's anything I can do on my end.
Lee
On Dec 11, 3:36 pm, "Alex Payne" wrote:
> You're not the first to report this issue, I'm afraid. This crops up
> from time to time due to some low-level, complicated caching logic in
> our system. We're constantly ironing
You're not the first to report this issue, I'm afraid. This crops up
from time to time due to some low-level, complicated caching logic in
our system. We're constantly ironing out this code, but I'll
double-check the update method and see if there's any glaring issues
there.
On Thu, Dec 11, 200
I have a twitter bot running at http://twitter.com/shortyawards for
the site http://shortyawards.com. I'm noticing in our logs that many
of our status updates using the json API are being ignored. The
'text' field of the json response comes back with the previous status,
ignoring the new status
Just to clarify, here is an example of the request we are sending and
the json that's returned:
REQUEST
http://twitter.com/statuses/update.json?status=%40sixuntilme%2C+you+were+nominated+by+%40jakerutter+for+a+%23personal+Shorty+Award+http%3A%2F%2Fbit.ly%2FLAIv
STATUS CODE
200
RETURNED
data={"i
