Hi Turadg.

This is something I've been meaning to do for quite a while. It will
return a "timezone" element on the "location-hierarchy" element
containing something recognizable by tzinfo (e.g. America/Los_Angeles)
IF the application has been authorized at the city level or higher.
In the JSON responses, it would show up as "timezone" under user.
E.g.:
{ "user": { ..., "token": "blah", "timezone": "America/Los_Angeles" } }

I'd totally dig an app that reset the timezone of my laptop when I
opened it up for the first time in a new place.

I'll document this theoretical behavior and get it up tomorrow. ;-)

seth

On Wed, Aug 20, 2008 at 6:54 PM, Turadg Aleahmad <turadg@...> wrote:
> Have you given any thought to offering a "timezone" access level in
> the API? I know it doesn't fit into the hierarchy well and it
> requires calculating the timezone from the location, but it would open
> up some interesting applications.
>
> e.g. I'd like my calendars, iCal/OSX and Google Calendar, to update
> their timezones when my Fire Eagle learns I'm in a new time zone.
>
> It's pretty easy to get a timezone from a ZIP, in the US. I don't
> know how to convert Town or Regional to timezone. But for an
> application interested only in time zone, it would be helpful to the
> user to only grant that level of access and helpful to the developer
> by saving them the location->timezone conversion. Adding this access
> level and calculation into the API could lead to a new set of
> compelling applications built on your system.
>
> -Turadg
>
>