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
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
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
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
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
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
