This was actually caused by the hurricane failover and our silly decision to seize FSMO roles. When you do this to an AD environment, you have to setup the new PDC Emulator master as the authoritative time source on the network.
We, uh, didn't do that, so as a result all manner of time desynchronization has occured. I get to take the blame for it, but I ...
Shog brought this question's revisions (10K only) to our attention today and I immediately said "LINQ2SQL".
Turns out that /review wasn't loading audit posts detached from the current DataContext, so any changes to its properties (audit posts have most visible properties altered) are tracked and an errant SubmitChanges could persist invalid data.
I have no idea how much effort it would take to implement this, but I do have some idea how much utility it would have. Almost none at all. Moderators editing comments should be exceedingly rare. They should only be doing this to remove profanity or spam links from otherwise useful comments. Since useful comments that contain profanity and spam links are so ...
I'd say this is status-bydesign
We're not all British, so using UTC/GMT for relative timings doesn't make much sense.
Instead, as @lunboks mentioned, "yesterday" means "more than 24hrs but less than 48hrs". This is yesterday for half the world.
Use "relative" yesterday: No prejudice, each time zone will agree with the "yesterday" half the ...
Accept votes used to be deleted with the question owner - by mistake. Looks like this is one of the answers caught by that bug.
I have searched but cannot find the bug report (though it may have not been reported...).
If you are referring to date asked, you can search answers:0 (add [tagname] to the search if you wish to search by tag) and then select the "newest" tab. Here is a link to an example of that search method pre-done. If you want to search by date of lastest activity instead of date asked, do the steps above and use the "active" tab instead of the "newest" tab.
This is a really bad browser bug. And while we don't officially support FF 52, it seems used widely enough (because it's ESR) that this issue is probably worth working around.
Basically, the layout engine decides that the timestamp has a width of zero pixels, and we have to force the browser to re-calculate the layout.
This workaround is deployed here on ...
Please stop using weird date formats, it is very unfriendly and hard to read, specially the year! Having to do "mouseover" to understand the date is a big usability fail. Checking the date format by country you can see that most countries will find this MMM dd'YY format very weird.
Dates should all change to ISO style (YYYY-MM-DD HH:mm:ssZZ). They are ...
The soft answer is: Often enough so that you usually have a good idea about the timing of previous conversations, but not too often for them to be annoying clutter.
You probably want the hard answer, though:
A monologue (one of the "speach bubbles" that combine subsequent messages by a single user) gets a time stamp if
its first message is at least 15 ...
Stack Overflow, and the rest of the Stack Exchange network of sites uses UTC days, not local times (such as GMT with / without DST).
Will have to look at the reset you mentioned - this may indeed be a bug.
The time resolution on the message is why this is happening. During conversion to a relative time string, if the delta is over an hour but less ...
It used to be shown only on dates 360 days, almost a full year, ago or older, but this has changed: now it's shown on all timestamps not belonging to the current calendar year. So you have to wait until 2020-01-01.
If you can't wait, note that hovering over most (all?) timestamps (relative or absolute) will always show the full timestamp, including the year:...
It's a bit easier to see if you look at a chat that has a bit more activity than the one in your example but we use a three-letter abbreviation for chat messages up to a week old.
So, something posted today just has the time, while something the prior day says "yst" for yesterday. Further out, we switch to days of the week, so "Sun" and "Sat" for Sunday and ...
I don't think it's a big deal, but I prefer the status quo to your proposal. But that's because of a major dissonance I see in your proposal which is easily fixed. If it's 20 June 2013 and I see a post dated “22 June”, I'm going to first assume June this year, then do a double take. When in June 2013, all posts dated June should have a year mark.
The no ...
I can sort of see this for inbox notifications, but even then... if you keep the emails, they sure do look weird.
This is fixed up now and we're using explicit date and time in both inbox notifications and tag filter emails. Let me know if you see any other emails that are using relative times.
span elements with the class relativetime are found by this js, which includes
return e.minutes+" mins ago"
Thus why the conversion to n mins ago. Server-side, the short notation is being output: e.g., nm ago.
I think the two should be consistent, where I'd personally prefer the formatting currently implemented client-side.
You are sorting questions by recent activity, in which case the last active timestamp in the question list includes the most recent answer, comment or edit.
Although the question was posted in 2013, a new answer was posted to that question a short while ago, the timestamp reflects the last time that answer was edited.
Knowing the order of answers coming in is pretty valuable to me.
Even three weeks later, being able to see the date and time in comparison with the other posts is useful to me. I admit that I may be an unusual case but you've failed to show what harm it does, so even a small benefit to some makes it of value.
Think about this... I ask a question... and ...
Check the clock on your computer - my guess is that you've mixed up AM / PM. The auto refresh happens client side and does depend on having a somewhat in sync clock.
I think Jeff is the only one who can give the real reason, he wrote the code himself back in the early days of Stack Overflow, asking for help himself.
I can only make assumptions using my common sense and own opinions.
My best guess what Jeff was thinking is that showing relative time save trouble of different time zones for recent posts. If you show "...
While the '12 does make it look a bit older than it actually is, I don't see what the harm is in doing that.
Besides, adding what is imho an inconsistency to the timestamper would confuse users much more than the '12 ever did, and would probably lead to people asking for it to be reverted.
All relative times are calculated based on your system clock. If your system clock or timezone is incorrectly configured, then the relative time displayed will be incorrect.
It sounds as if you have ...
We now correct for incorrect system clocks by doing the differential from page load with a server offset in account. Basically we just record the difference between your time and server time when we load the page, then add it to the differential when doing relative date calculations.
Bottom line: when it says "2 minutes ago" and updates past that, it ...