Time banner makes no sense
-
"Now" didn't move, forum. Now is now. The previous post was 13 days ago.
-
@Yamikuronue You're the 56329563874th to notice, yet the 1st to actually post it as a bug
-
@RaceProUK That's why I'm in QA ;) I actually report and, occasionally, fix things
-
@Yamikuronue said in Time banner makes no sense:
"Now" didn't move, forum. Now is now. The previous post was 13 days ago.
We're just preparing for when the IoT let's us access data from the future.
-
"XX time-units from now" usually means "XX time-units in the future" in my experience.
"XX time-units ago" implies that the event was XX time-units in the past, anchored from now.My recommendation would be "XX time-units later" which indicates that there was that span of time between what just precedes the banner and what immediately follows it. I seem to remember seeing that phrase, but I don't know when it changed.
Filed under: English, yo!
-
An example of where neither "from now" nor "ago" makes sense, but "later" does:
-
@djls45 I think you mean
-
@djls45 said in Time banner makes no sense:
My recommendation would be "XX time-units later"
Didn't it used to say that until recently? I know it said "later" on Discourse, but I could have sworn this is a recent change for nodebb too
-
@djls45 said in Time banner makes no sense:
I seem to remember seeing that phrase, but I don't know when it changed.
This morning's update.
-
@Yamikuronue said in Time banner makes no sense:
"Now" didn't move, forum. Now is now. The previous post was 13 days ago.
It says 13 days from now. It doesn't say in which direction.
-
@xaade said in Time banner makes no sense:
let's us
-
@Yamikuronue yeah, while it could technically be valid English, it's definitely confusing
-
@sloosecannon It's valid English in that it's a sentence structure that contains the necessary parts. But it means something other than the author's intent. I don't know of any dialect that would consider "[time] from now" to mean "[time] before the present moment".
-
@Zecc said in Time banner makes no sense:
@xaade said in Time banner makes no sense:
let's us
ATM machine!
-
@RaceProUK said in Time banner makes no sense:
@djls45 said in Time banner makes no sense:
I seem to remember seeing that phrase, but I don't know when it changed.
This morning's update.
Ok, so I wasn't in a psychotic break when I swore to myself when I started reading this thread "Wait, I was just looking at a thread yesterday with one of these breaks that said "X days later""...
-
My top suspicion is that they're using the same localized string in multiple places and didn't realize how it was used in different places.
-
@boomzilla said in Time banner makes no sense:
My top suspicion is that they're using the same localized string in multiple places and didn't realize how it was used in different places.
The actual reason is that @julianlam enabled time in the future and nodebb-plugin-tdwtf-customizations accidentally relied on not having that enabled causing all time differences being considered to be in the past.
I'm working on a quick update to fix that and not being able to add tags to new topics on the Recent and Unread pages.
-
@boomzilla My top suspicion is that this line has been lost somehow.
-
@Zecc said in Time banner makes no sense:
@boomzilla My top suspicion is that this line has been lost somehow.
-
@ben_lubar If that's consistent, isn't the fix just a simple flip of the difference around?
No. It's obviously not enough, as accalia explains below. The fix is to not use timeago at all.
-
-
@ben_lubar said in Time banner makes no sense:
@Zecc said in Time banner makes no sense:
@boomzilla My top suspicion is that this line has been lost somehow.both of those are wrong as they measure in words. they don't describe a time span that occured at a point that is not present.
"Two Weeks Later" is correct for a gap of two weeks between posts when the newer post happened three months ago, "Two Weeks Ago" isn't and "Two weeks from now" also isn't
-
@accalia Of course. ď correct.
-
@Zecc said in Time banner makes no sense:
@ben_lubar If that's consistent, isn't the fix just a simple flip of the difference around?
No. It's obviously not enough, as accalia explains below. The fix is to not use timeago at all.
Actually, the link you crossed out shows the problem @accalia described is already fixed.
-
It was fun while it lastedâŚ
-
I propose 'then 8 suns set...'
-
@coldandtired said in Time banner makes no sense:
I propose 'then 8 suns set...'
WHAT A HORRIBLE NIGHT TO HAVE A CURSE.
THE MORNING SUN HAS VANQUISHED THE HORRIBLE NIGHT.
-
For the night is dark and full of terrors.
But still I'm filled with determination.
Because the spice must flow.
-
@Zecc said in Time banner makes no sense:
the spice must flow
Is that what you kids call it these days?
-
@coldandtired said in Time banner makes no sense:
I propose 'then 8 suns set...'
Technically, it's one sun setting 8 times. Unless you live on a different planet than I do.
-
-
@HardwareGeek Fix your software clock perhaps?
Anyways... sorry about that one @ben_lubar ... and here I was thinking it wouldn't affect anyone...
-
@julianlam aren't you supposed to come here and tell us we're all using your software wrong?
-
I told him his system clock wasn't set properly, isn't that the definition of doing it wrong?
-
@julianlam said in Time banner makes no sense:
@HardwareGeek Fix your software clock perhaps?
Somebody's clock is off, but I don't think it's mine. Mine's synced to time.nist.gov, and even after taking the time to force a "sync now," my post was still in the future.
-
Oh, this also happens if the server clock is slow. Paging @ben_lubar ... run
ntpdate
maybe
-
@julianlam Can't it just use server time for both "post time" and "now"?
-
@loopback0
I mean, how would that even work? "Oh, here, let's send the server time this post was recorded at. And then keep a separate web socket open to push server time every second, so that the client side javascript can update the time differences since the post was posted."Filed under: Brought to you by DiscoSolutions
-
@izzion said in Time banner makes no sense:
And then keep a separate web socket open to push server time every second, so that the client side javascript can update the time differences since the post was posted
No, obviously each second the client creates a post containing the time and the server replies with its time. Every 100 seconds a new topic is started.
-
@izzion said in Time banner makes no sense:
@loopback0
I mean, how would that even work? "Oh, here, let's send the server time this post was recorded at. And then keep a separate web socket open to push server time every second, so that the client side javascript can update the time differences since the post was posted."Filed under: Brought to you by DiscoSolutions
I guess the proper way would be to just generate the "n minutes ago" blurb server-time, or send a difference in seconds. You miss the live updates, though, and infiniscroll will likely result in a pretty weird chronology.
And the Disco-solution would be for Jeff to tell you your time perception is wrong, and you should align your time axis with Discourse. CLOSED WONTFIX
-
Or you can ignore small differences that don't actually make sense and treat them as "now", assuming that the server/client time sync is just a bit off.
I've been getting a lot of these "a minute from now" on posts/chats I create or observe recently.
-
@Maciejasjmj said in Time banner makes no sense:
And the Disco-solution would be for Jeff to tell you your time perception is wrong, and you should align your time axis with Discourse. CLOSED WONTFIX
DISCOTIME CDN!
-
@Maciejasjmj said in Time banner makes no sense:
I guess the proper way would be to just generate the "n minutes ago" blurb server-time, or send a difference in seconds.
The proper way would be to just display a timestamp and forget the stupid ago/from now BS.
-
@Maciejasjmj the most obvious answer is to have the server send the time that it has, and let the client-side script calculate how much of an offset there is. After that, the client can use its local clock's time plus that offset.
-