Relative timestamps should be relative

(#1030) Feature Closed: Shipped markdown

Problem

Fluxer uses the same timestamps like Discord, but it makes the strange decision to replace relative timestamps (<t:0000000000:R) with something useless. The following message as it appears on both chat apps: <t:1771945200:t> is <t:1771945200:R> Discord: image Fluxer: image

Proposed solution

It should look the same way as it does on Discord. The JavaScript library they're using to get the relative time is called Moment.js, so assuming Fluxer is using it too (and I hope they are rather than reinventing the wheel!) it is as easy as just using the existing function.

3 comments

Sign in with Fluxer to comment and vote.
Comment by @Atakku
RexSystem 1 vote originally by @Atakku on GitHub 1 reply
To note, Discord has a flaw in the relative timestamps that doesn't make sense. For example, on discord I have <t:990914400:R> which shows my age incorrectly (it rounds instead of flooring years) image while on Fluxer, im happy with rounding down image
Comment by Chai
Chai 1 vote originally by @Chailotl on GitHub OP
This is just how the Moment.js library works, and is meant to reflect how people round time. For example, if a date was 24 years and 10 months ago, I would just say "25 years ago".