Yeah, all of my timestamps are now busted and I'm just finding out...
It looks like this was just a change in the Search API format, and not
the REST API format? Is that correct?
Going bonkers,
-Chad
On Tue, Jun 23, 2009 at 9:02 PM, Christopher Finkecfi...@gmail.com wrote:
Around 7:45pm
yes, I found this as well.
-Jeff
On Jun 23, 6:02 pm, Christopher Finke cfi...@gmail.com wrote:
Around 7:45pm Central time, I noticed that the format of the
created_at timestamp changed from Fri, 15 May 2009 14:41:50 + to
2009-05-15 14:41:50 UTC. Was this change intentional? If so, was
Hi,
After the change, the API started to return status code:403 when there
is no matching tweets.
It used to be returning status code 404.
Will this be a permanent behavior?
---
[Wed Jun 24 12:50:31 JST 2009]GET
http://search.twitter.com/search.json?q=from%3Atwit4j+doesnothit
[Wed Jun
I'm seeing that, too. Can you open a ticket?
http://code.google.com/p/twitter-api/issues/list
Thanks,
Doug
--
Do you follow me? http://twitter.com/dougw
2009/6/23 H12山本 裕介 yus...@mac.com
Hi,
After the change, the API started to return status code:403 when there
is no matching tweets.
