It appears on normal timelines the created_at field is Wed Mar 25
22:04:55 + 2009
On DMs it's now formatted Tue Nov 23 16:47:09 UTC 2010 which causes a
number of parsers to fail if they are looking for offsets rather than
timezone codes.
On Nov 23, 4:41 pm, Rich rhyl...@gmail.com wrote:
Thanks Taylor
I'm coding defensively now to actually check for this in future :)
Richard
On Nov 23, 4:47 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
This was unintentional and should be fixed later this morning. For
notifications on transient issues like this, I recommend
There's a third date format for tweets returned by the Search API.
Time for me to check my parsers again. There's a Perl module that will
literally parse any imaginable date format, but it's hopelessly slow
for the kind of volume Twitter delivers.
--
M. Edward (Ed) Borasky
