Seeing "NaN days ago" about tweet HOT 9 CLOSED

Odd. I can't reproduce this; the error isn't present now. Please can you give an indication of which browser/OS you were using, and which example block on the page appeared to be broken?

from tweet.

Seems resolved now. After a few minutes the api seemed to go a bit wonks. Maybe the post time was the first to drop. Thanks for the response. I appreciate it :)

from tweet.

Oops, meant to close as well.

from tweet.

I'm getting the NaN issue in IE, on your demo site, seems to only happen in the 2 demos using the "username" property. Works fine in FF and Chrome.

from tweet.

Those examples use non-search API calls, and it looks like Twitter's currently returning dates in a different format for those calls: the user_timeline call (e.g. http://api.twitter.com/1/statuses/user_timeline/sanityinc.json?callback=?) returns "created_at" timestamps like this:

"Wed Apr 29 08:53:31 +0000 2009"

whereas the normal format (as returned by a search API call, e.g. http://search.twitter.com/search.json?q=sanityinc) would be:

"Mon, 22 Mar 2010 15:05:01 +0000"

I guess that IE won't parse the first format correctly. I'll have to look into solutions. Which IE version are you using?

(A temporary workaround is to use the query option instead of username in order to force use of the search API call, but this has key disadvantages, most notably omitting tweets older than 30 days.)

from tweet.

Thanks for response purcell, I'm on IE8. Yeah I did try the query option but didn't return an item from 2 days ago, only from 1 day ago for some reason...

I found this thread which may be of help? (I'm not clever enough to hack it myself!)
http://forums.whirlpool.net.au/forum-replies-archive.cfm/1171219.html

from tweet.

I'll look into patching it. It seems the issue has been known since 2008, and is documented here: http://code.google.com/p/twitter-api/issues/detail?id=206

from tweet.

I believe I've fixed it with this commit: http://github.com/seaofclouds/tweet/commit/6365a615dfd3870cbee151ef5fccb03bcc255400

Could you please check and confirm?

from tweet.

Works for me, nice job, thanks!

from tweet.