For example, take this event:
210489449014070 Facebook Event / Graphical API
This event was created back in September 2011. When it was created, it correctly showed Friday, November 11, 2011, 11:11 pm, as the date and time of the event.
But now it shows Saturday, November 12, 2011, 12:11 as a date. This also happens for future events such as 426044564103401.
However, this does not even happen, for example, in the current month, like 330237680381087.
Which shows the correct date (same as on the chart.) This one was created a few months ago.
My suspicion is that he is still applying the DST offset to the date. For example, right now, peacetime is 7 hours with UTC (because DST is valid, therefore PDT.) On 2012-11-04, DST will end and it will return to 8 hours with UTC. He "falls" in the fall.
The date on the Facebook.com interface shows that it is still using a 7-hour shift (this is an hour earlier than it should be.) My guess / guess is that in 2012-11-04 02:00: 00, he will start show the correct date. Hooray? But at this point, dates that are now true will probably not display correctly (because he will no longer use DST.)
I assume that this means that internal events, not including time zones, are now considered worldwide as "-07: 00" or "-08: 00" based on the current UTC offset, and not on a relative date.
Should I pull out all 186 272 events and update all of them to use timezone dates to fix this (also affecting the external interface for other users and possibly influencing other parties that interact with these events through FQL or so on. d.)?
Thanks for any help.