Edit history

Earlier versions of `<t:unix:R>` Relative timestamp format not applied for near timestamps, newest first.

Current version | Edited by Rex
Changes
[image](https://feedback.fluxer.com/p/485#f-485)Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing issues and didn't find a duplicate.Removed:
Show

`<t:unix:R>` Relative timestamp format not applied for near timestamps

Summary

The :R relative timestamp format falls back to a static time string for timestamps within approximately ~48 hours in the past and ~8 hours in the future. Timestamps within this window display as Today at X:XX PM or Yesterday at X:XX PM instead of the expected relative string like in X minutes, 2 hours ago, or 23 hours ago. Timestamps outside this window correctly display as relative strings. Hovering over affected timestamps shows the correct relative string in the tooltip, suggesting the calculation works internally but is not being used as the display value within this threshold.

Steps to reproduce

  1. Send a message containing <t:UNIX_TIMESTAMP:R> where the timestamp is within the last 48 hours or within the next 8 hours
  2. Observe that the message displays Today at X:XX PM or Yesterday at X:XX PM instead of a relative string
  3. Hover over the timestamp, the tooltip correctly shows the relative string (e.g. in 5 minutes, 2 hours ago)
  4. For comparison, send a timestamp older than 48 hours, it correctly displays as 3 days ago, last week, etc.

Environment (optional)

stable build 190 (44b6925), 2026-03-27 14:07:52 UTC, Electron 39.2.7, Windows 11 10.0.26200 (x64), desktop stable 0.0.8

Logs or screenshots (optional)

image
Original by bizo
Show

`<t:unix:R>` Relative timestamp format not applied for near timestamps

Summary

The :R relative timestamp format falls back to a static time string for timestamps within approximately ~48 hours in the past and ~8 hours in the future. Timestamps within this window display as Today at X:XX PM or Yesterday at X:XX PM instead of the expected relative string like in X minutes, 2 hours ago, or 23 hours ago. Timestamps outside this window correctly display as relative strings. Hovering over affected timestamps shows the correct relative string in the tooltip, suggesting the calculation works internally but is not being used as the display value within this threshold.

Steps to reproduce

  1. Send a message containing <t:UNIX_TIMESTAMP:R> where the timestamp is within the last 48 hours or within the next 8 hours
  2. Observe that the message displays Today at X:XX PM or Yesterday at X:XX PM instead of a relative string
  3. Hover over the timestamp, the tooltip correctly shows the relative string (e.g. in 5 minutes, 2 hours ago)
  4. For comparison, send a timestamp older than 48 hours, it correctly displays as 3 days ago, last week, etc.

Environment (optional)

stable build 190 (44b6925), 2026-03-27 14:07:52 UTC, Electron 39.2.7, Windows 11 10.0.26200 (x64), desktop stable 0.0.8

Logs or screenshots (optional)

image

Checks

  • ☑ I searched for existing issues and didn't find a duplicate.