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](https://momentjs.com/), 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.Removed: -### Notes (optional)Removed: -Removed: -_No response_Removed: -Removed: -### ChecksRemoved: -Removed: -- ☑ I searched for existing discussions and didn't find a duplicate.Removed: -
Show
Relative timestamps should be relative
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.
Original by Rex
Show
Relative timestamps should be relative
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.
Notes (optional)
No response
Checks
☑ I searched for existing discussions and didn't find a duplicate.