Does "<1m" make any sensitive difference to "1m"?

AI-generated summary

A discussion is underway about the display of timespans on a topic list. meglio suggests replacing <1m with 1m for aesthetic purposes and to remove a special case for timespans under one minute. codinghorror agrees, calling the current display “info-porn” and advocating for simplification. However, elijah prefers the alternative “just now” for very recent posts, but meglio counters that it becomes outdated too quickly and doesn’t fit the existing timestamp format. elijah ultimately disagrees with the proposal, finding the current display nicer and more readable. An alternative suggestion by mcwumbly to show 0m for posts under 1 minute is made. eviltrout later commits a change to the code, implying the proposal has been implemented.

Just looking at this list:

Note how the first of the latest topics says <1m, then the next says 31m.

I might be mistaken, but it seems that for aestethics, <1m should be changed to 1m. This change will make little to no difference in meaning, but will remove that special case for timespans less than one minute.

6 Me gusta

I definitely agree with this and have thought so for some time. @eviltrout can we simplify this code to not do the less-than thing? It’s clearly info-porn in my book..

I’m kind of fond of “just now” for very recent posts.

I think “1m” is simpler, shorter, and less code / translations.

2 Me gusta

“just now” will become outdated too quickly and would need to be changed to “1m” eventually. Also, it does not fit into timestamps formatting of the older topics, which was one of the main points of this simplification proposal.

3 Me gusta

Find go hate on idea. I think it looks nicer and reads nicer. I’ll go off in a huff now.

(Not really. :slight_smile:)

1 me gusta

For the sake of bike shedding, we could round down and show 0m for posts <1m ago.

1 me gusta

7 Me gusta

https://github.com/discourse/discourse/commit/78e8aa823d9e03d4acf276ca667370edb0dd9f13

8 Me gusta