[twitter-dev] Re: Time zone support
On Mon, Nov 9, 2009 at 2:03 PM, Emrah e...@ekanet.net wrote: That's the main point of my suggestion! It helps avoiding the need of making calculation to know at what time a Tweet has been posted according to the poster's timezone. It doesn't make sense to see that Jeff said Good morning at 12:30 even though it was 06:30 for him... Of course for a personal timeline I will need to have the 13:30 information, but I would appreciate to have a mention of Jeff's timezone somewhere. For now, I must calculate each post's timestamp, whether it comes from India, Switzerland, New-York or Australia... If tweets all start having variable timezones, it is just another thing that has to be calculated around to get times into the local timezone for end users. I am not going to repeat myself... I still believe this feature would emphasize the international impact of Twitter and improve the user experience. What do you think? I think it's solving a problem that doesn't exist. It doesn't bother me to see my friends in Australia talking about going to bed when it's morning for me. And how are you going to decide whether or not it's a pertinent message? If my mom posts Not feeling well, going to bed at 9pm, are you going to show that message if I'm in another timezone? Or if a friend posts Great night, just getting to bed at 4am their time? Good morning! I slept 18 hours! Seriously, I don't see a) why this is a problem or b) even if you accept that it is a problem, how you'd implement a solution. Now if you could find a way to filter out political message or pro-Yankees posts, THAT would solve a real world problem :-) TjL
[twitter-dev] Re: Time zone support
I actually totally prefer time's to all be UNC / GMT as they are now... it's the same erevywhere, and very easily converted to local timezones for display - which is what I imagine most end users want to see... they don't want to be working out timezones from around the world in their heads! If tweets all start having variable timezones, it is just another thing that has to be calculated around to get times into the local timezone for end users. Please leave as it is. Just my thoughts Simon On Nov 8, 11:33 pm, Emrah e...@ekanet.net wrote: Raffi Krikorian wrote: hi emrah. this sounds interesting -- how do you handle people who are traveling and may not be in their home timezone when they say good morning? :) Timezone code could be set per Tweet as a parameter. E.g.: on mobile phones, the time is usually updated from the network operator and on most computers from an NNTP. Obviously the user experience should not be changed and the timezone must be discovered and set automatically. Regards, Emrah
[twitter-dev] Re: Time zone support
Zaudio wrote: I actually totally prefer time's to all be UNC / GMT as they are now... And that won't change obviously. Messages would be marked with both times (poster's and reader's) it's the same erevywhere, and very easily converted to local timezones for display - which is what I imagine most end users want to see... Again, that won't change of course. But it may be preferable to have both timestamps displayed. they don't want to be working out timezones from around the world in their heads! That's the main point of my suggestion! It helps avoiding the need of making calculation to know at what time a Tweet has been posted according to the poster's timezone. It doesn't make sense to see that Jeff said Good morning at 12:30 even though it was 06:30 for him... Of course for a personal timeline I will need to have the 13:30 information, but I would appreciate to have a mention of Jeff's timezone somewhere. For now, I must calculate each post's timestamp, whether it comes from India, Switzerland, New-York or Australia... If tweets all start having variable timezones, it is just another thing that has to be calculated around to get times into the local timezone for end users. I am not going to repeat myself... I still believe this feature would emphasize the international impact of Twitter and improve the user experience. What do you think? Cheers, Emrah
[twitter-dev] Re: Time zone support
My mistake, I wrote 12:30 and 13:30, and it is not coherent. I ment 12:30 in both cases. Btw, sorry for my English. Regards, Emrah Emrah wrote: Zaudio wrote: I actually totally prefer time's to all be UNC / GMT as they are now... And that won't change obviously. Messages would be marked with both times (poster's and reader's) it's the same erevywhere, and very easily converted to local timezones for display - which is what I imagine most end users want to see... Again, that won't change of course. But it may be preferable to have both timestamps displayed. they don't want to be working out timezones from around the world in their heads! That's the main point of my suggestion! It helps avoiding the need of making calculation to know at what time a Tweet has been posted according to the poster's timezone. It doesn't make sense to see that Jeff said Good morning at 12:30 even though it was 06:30 for him... Of course for a personal timeline I will need to have the 13:30 information, but I would appreciate to have a mention of Jeff's timezone somewhere. For now, I must calculate each post's timestamp, whether it comes from India, Switzerland, New-York or Australia... If tweets all start having variable timezones, it is just another thing that has to be calculated around to get times into the local timezone for end users. I am not going to repeat myself... I still believe this feature would emphasize the international impact of Twitter and improve the user experience. What do you think? Cheers, Emrah
[twitter-dev] Re: Time zone support
hi emrah. this sounds interesting -- how do you handle people who are traveling and may not be in their home timezone when they say good morning? Hi, Any plans to implement timezone support? It's weird to say Good morning at 5h45 from Switzerland and see it appear as 19h45 in the public timeline / on some profiles... It doesn't make sense to me... The time should be written with the mention of the time zone, e.g.: 05:45 CEST. An other suggestion could be to display the time in both formats: e.g.: 05:45 CEST / 10:15 IST | poster's timezone / reader's timezone. Choice should be given to the user whether to display the message timestamps with timezone support or no. Regards, Emrah -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi
[twitter-dev] Re: Time zone support
Raffi Krikorian wrote: hi emrah. this sounds interesting -- how do you handle people who are traveling and may not be in their home timezone when they say good morning? :) Timezone code could be set per Tweet as a parameter. E.g.: on mobile phones, the time is usually updated from the network operator and on most computers from an NNTP. Obviously the user experience should not be changed and the timezone must be discovered and set automatically. Regards, Emrah
