Fri, 10 Apr 2026 19:46:47 +0000 https://bugs.horde.org/ticket/10341 Facebook events show up on wrong date I have a problem with a facebook event: In Facebook it takes place on 22.10. 19:30 till 23.10. 5:00. In Kronolith it shows up as 23.10. 7:30 to 23.10. 17:00 Is there something wrong with my setup or is the timezone parsing wrong (my Kronolith uses UTC) Thu, 14 Jul 2011 21:16:04 +0000 https://bugs.horde.org/ticket/10341#t66335 This is Facebook's fault. FB has a *horrible* strategy for dealing with timezones in the events API. Facebook stores the event time as if it were in Pacific Standard Time. i.e., I'm on the east coast of the US, I enter an event to start at 4:00EST. They store the event as 4:00PST translated to UTC. So, when using the API you need to do the calculations yourself. That would be fine, except to do the translation properly, you need to know the event *creator's* timezone, which we don't know. I took a best fit approach, and do the translation based on the Horde user's timezone. This works correctly on Facebook's website since they have access to all users' timezone information. Thu, 14 Jul 2011 21:45:16 +0000 https://bugs.horde.org/ticket/10341#t66336 Thats a shame on facebooks part. In my case probably all events will originate from the same timezone. I am guessing that for most users this scenario is the most likely (or not?!). Would it be possible and usefull to introduce a user definable "standart correction factor" with wich Facebook events are corrected so that the calendar works at least for event creators in one timezone as a workaround? > This is Facebook's fault. FB has a *horrible* strategy for dealing > with timezones in the events API. > > Facebook stores the event time as if it were in Pacific Standard > Time. i.e., I'm on the east coast of the US, I enter an event to > start at 4:00EST. They store the event as 4:00PST translated to UTC. > So, when using the API you need to do the calculations yourself. That > would be fine, except to do the translation properly, you need to > know the event *creator's* timezone, which we don't know. I took a > best fit approach, and do the translation based on the Horde user's > timezone. > > This works correctly on Facebook's website since they have access to > all users' timezone information. Thu, 14 Jul 2011 22:06:33 +0000 https://bugs.horde.org/ticket/10341#t66338 I typically shy away from introducing settings to work around other application's shortcomings, but in this case, I think it makes sense. We are already hacking the time information to workaround it, no harm in customizing the value we use to do the hacking. Thu, 14 Jul 2011 22:38:27 +0000 https://bugs.horde.org/ticket/10341#t66340 Moving to Horde base, as this is where the pref will be implemented, right along with the rest of the Facebook prefs. Thu, 14 Jul 2011 22:40:07 +0000 https://bugs.horde.org/ticket/10341#t66342 Changes have been made in Git for this ticket: Fix timezone conversion (Bug #10341). Use smaller square icon. 2 files changed, 34 insertions(+), 37 deletions(-) http://git.horde.org/horde-git/-/commit/724edbc5d8dbc82bec4c19b70092092583ea5ff6 Thu, 28 Jul 2011 23:21:02 +0000 https://bugs.horde.org/ticket/10341#t66644