New answers tagged

0

Everyone has already answered your question, so I'm not going to go there :) My comment is more a suggestion. Please avoid ethereal time stamps like: "Today", "Yesterday", "10 minutes ago", "A week ago". We don't want to think how long was "10 minutes ago" from the time we're reading the content; let alone "A week ago". I suggest to always use the date ...


0

Events happen in a "point in time", stated as numbers. For example an event that happens at 4PM in London will be seen as happening as 1PM in Buenos Aires. Two different times (numbers) that denote the same point in time. Now, how you depict it depends on the particular application. For example if you want to see the events distribution along the hours ...


0

I don't think it would be logical to append since everyone sees their device local time. Instead you may state how long ago the action was performed for easier understanding. An user friendly algorithm can be drawn up. For example, if less than 1 minute, show in seconds, if less than 1 hour show in minutes, etc.


0

I can think of 2 other options 1.To display time in international format (if thats not so currently) hh:mm:ss Additionally we can add the timezone like IST 17:09:27 This should remove any confusion for the user, and not take up too much space.


3

Specifying the timezone directly in the timestamp is neither good nor bad practice. The answer to your question has more to do with your user experience than any documentation or timestamp formatting. You stated one or more of your users requested the timezone be added to your timestamps. This would imply your timestamps are currently ambiguous, which is ...


2

It depends on the other timestamps you display on your site/app. However, timestamps are almost always used to compare events relatively in a single timeline, so in almost always, it's better to stick to one timezone. Give the user an option to select their timestamp. Always load the user-selected time zone, and convert all timestamps to that timestamp. ...


0

I assume you're finding the dashed list "easier to scan" because dashes make your dates appear as single strings.


0

In general I wouldn't say that dashes make dates easier to scan, however... From looking at your screenshot, the dashes do make the date a little easier to scan in this scenario because it makes the day month year look like they are grouped together relative to the time component (gestalt principles). i.e. in the spaces only version your brain groups them ...


0

The 'Last seen' feature can be useful in a handful of situations. Mediating communication Some IM media like Facebook Messenger or Google+ Hangouts can be used both as synchronous media or asynchronous. Knowing that a person is currently offline allows you to understand that they may not be able to reply to you. If you need an immediate answer, you may ...


1

Last Seen is used to show how active this person is, in sites like Stack Exchange it makes sense, if im browsing a user account its usually in order to have an insight of how active this user is, and/or whether the user is reliable or not. For social networks if you dont see when was i last online i am likely to be more active. In Social Networks it will ...


1

It’s indeed an unnecessary extra step to manually calculate the age (a number, often floored) from a birth date (a 3-tuple), but you may be able to save the user another step, because all they need to know (from privacy and discriminatory POVs as well) is whether the candidate has turned 18 by a certain date. That‘s a Boolean value with just 2 states, true ...



Top 50 recent answers are included