Update: We just deployed a fix for this bug. the format should be back
to normal.
Thanks;
— Matt Sanford / @mzsanford
On Jun 23, 2009, at 7:24 PM, Matt Sanford wrote:
This was not intentional and I'm trying to get to the bottom of it
now.
Matt
On Jun 23, 2009, at 7:05 PM, Chad Etzel wrote:
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
Finke<[email protected]> 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
+0000" to
"2009-05-15 14:41:50 UTC". Was this change intentional? If so, was
it communicated anywhere? We had to rush out a fix to our app in
order to change the format string we were using to parse the date.
(The true issue, of course, is that Python needs a strtotime() like
PHP. :-)
Chris
