Hi, Jerusalem timezone's DST (Daylight Saving Time) has started 2 weeks ago and should now be GMT+3:00 while it was GMT+2:00 before it's DST has started. Twitter's API still returns 7200 as it's UTC offset while it should now be 10800 (GMT+3:00). Twitter's site seems to display correct dates in users feeds but the 'Settings' section still says Jerusalem is GMT +2:00 and the API still returns 7200 as UTC offset. This must be causing many inaccurate times in many applications using the Twitter API's UTC offset for calculating stuff.
What would be the best way to contact Twitter for getting this fixed? Thanks! Saggi Malachi