You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have enabled future support (because some of my posts have an "expiration date").
The problem now is that some users are reporting seeing "less than a minute from now" (more specifically, in French "d'ici moins d'une minute", which mean 1 minute into the future).
They see this I assume when they just posted something, so the current time is very close to the post date. It looks funny and wrong. As if they've just posted something into the future...
The text was updated successfully, but these errors were encountered:
Interesting. Do you have a proposed solution to this problem? Do you know how far off peoples machines are from true time? Do you think a ~5 second buffer that helps the fuzzy timestamps assume their in the future (within 5 secs) would help?
We've experienced this too. Our solution was to tweak the library to be able to allow future only one some elements by using a data attribute. If future is not allowed and the time is in the future, we just use the just now label.
If that sounds like a good solution to this problem for you too, we can clean the code up a bit and submit a pull request.
I have enabled future support (because some of my posts have an "expiration date").
The problem now is that some users are reporting seeing "less than a minute from now" (more specifically, in French "d'ici moins d'une minute", which mean 1 minute into the future).
They see this I assume when they just posted something, so the current time is very close to the post date. It looks funny and wrong. As if they've just posted something into the future...
The text was updated successfully, but these errors were encountered: