Skip to main content
8 events
when toggle format what by license comment
Feb 5, 2017 at 23:36 history undeleted animuson
Feb 5, 2017 at 1:48 history deleted user31914 via Vote
Mar 14, 2014 at 0:51 comment added Jason C @Bob You are confusing display with intent. The SE timestamp's purpose is not to tell you what time of day it is. It's not something you would ever look at to, say, determine that you have an appointment in 10 minutes. The timestamp's purpose (and the UTC clock's purpose) is to give you an idea of the relative time that an event on the site occurred, and it is a useful piece of relevant information to that effect. Its presence is not a justification for the usefulness of time-telling clocks on web sites. UI should match intent.
Mar 13, 2014 at 12:57 comment added Bob @LegoStormtroopr Just in case you were referring to the question/comment/answer/edit timestamps and are unaware of the clock, yes, it exists.
Mar 13, 2014 at 12:50 comment added Bob @LegoStormtroopr The SE timestamp is effectively a clock - if you watch it for a while you'll notice it updates itself (every 60 seconds, actually). It shows the current time, therefore it is a clock. But even if it only reflected the time at page load, it would still be useful in the same way. And my point would still stand, with many other examples available.
Mar 13, 2014 at 12:29 comment added user31914 @Bob StackExchange doesn't have a clock anywhere that I've seen. It has text-based timestamps for things everywhere, but no clocks per se.
Mar 13, 2014 at 9:27 comment added Bob > Secondly, it is very unlikely that a user of a web application will need a clock in your application. For local time, that's correct. But there is an exception for server time, which can be significant - StackExchange is one such example; they use UTC for a new day (reputation, etc.) and therefore display time in UTC so the user does not have to look elsewhere.
Mar 13, 2014 at 3:48 history answered user31914 CC BY-SA 3.0