If I'm going to be looking at a timestamp, I'm going to be thinking. Often times what I'll be comparing to is-- (or might be, because of ambiguity)-- a local time. Hovering my mouse is not a dealbreaker.
At least let people mouse over, or click on the time, and get a real timestamp.
Some of these tools seem to be copying from designs intended for social media websites, instead of something work related.
As an Australian this is actually a lot better for me.
If there's a time like "10:43am" I have no idea whether that's UTC , my timezone, or some American timezone.
You could argue that they should put the timezone there, but they don't, or they will but only for American TZ.
and I don't want to dig around my profile settings to find it.
Even hacker News is relative. I know that I am responding 34 minutes after your post.
I am in New Zealand so I understand your perspective, I just don't think it's a major problem.
Do you have data to back that up?
I'm not calling for ISO 8601 by force (not seriously anyway) and it's not just relative vs. absolute. Relative timestamps must be a better choice for some use cases. But the horrors I'm describing are not just relative timestamps, they're non-linearly quantised (probably not a strictly correct term), obfuscated, and relative.
Because most people I know, even en especially older persons, if you say 2 weeks ago, they will look at their calendar and count days to see what day it was exactly.
Let's suppose I tell you: you will have a free concert in 3 weeks. First you will want to know the exact day, then you will still want the correct date because otherwise you don't know if it is in may or in June, Beginning or end of the month,...