Since the API does not return the timezone offset, the wrong date can be displayed to different people. In my case when I searched for "Orange Is the New Black", it told me that the article from NY Journal of Books was published on April 5, 2010, but what we actually wanted to display was April 6, 2010 (http://www.nyjournalofbooks.com/review/orange-new-black-my-year-women%E2%80%99s-prison).

![screen shot 2013-10-01 at 11 57 42 am](https://f.cloud.github.com/assets/81969/1247284/fe1b24bc-2ab9-11e3-8713-ae475a2290a8.png)


I didn't know what was happening at first, but then I tried these:
```javascript
> new Date("2010-04-06").toString()
"Mon Apr 05 2010 20:00:00 GMT-0400 (EDT)"
> new Date("2010-04-06").toUTCString()
"Tue, 06 Apr 2010 00:00:00 GMT"
```

What's happening is that the date passed to the `Date` constructor is converted to the ["number of milliseconds since January 1, 1970, 00:00:00 UTC."](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/parse?redirectlocale=en-US&redirectslug=JavaScript%2FReference%2FGlobal_Objects%2FDate%2Fparse), and then that is converted to the local time. That time is actually yesterday in my timezone:

![screen shot 2013-10-01 at 1 00 38 pm](https://f.cloud.github.com/assets/81969/1247358/0f1bea70-2abb-11e3-9b27-538d9abb93c3.png)

One solution to that is to use the methods `getUTCDate` etc.