Timestamps in embeds don't seem to render

(#269) Bug Closed: Fixed embeds

Summary

The client does not seem to render timestamps in embeds. Debugging shows that they are part of the message object, but not included in the AST.

Steps to reproduce

  1. Send a message with the following data:
    {"embeds":[{"description": "t", "timestamp": "2026-02-21T22:14:25.975Z"}]}
  2. See the issue

Environment (optional)

stable (5b0afb2), 2026-02-21 14:40:38 UTC, Electron 39.2.7, Linux 5.15.0-170-generic (x64), desktop stable 0.0.8

Logs or screenshots (optional)

image Message record:
{
  "id": "1474892047499169838",
  "channel_id": "1471691162301679192",
  "guild_id": "1471691126960477817",
  "author": {
    "id": "1471590207182442969",
    "username": "SmileyBot",
    "discriminator": "1176",
    "global_name": null,
    "avatar": "b66e125c",
    "avatar_color": 15708190,
    "bot": true,
    "system": false,
    "flags": 16,
    "pending_bulk_message_deletion": null,
    "traits": []
  },
  "type": 0,
  "flags": 0,
  "pinned": false,
  "mention_everyone": false,
  "content": "",
  "timestamp": "2026-02-21T22:14:26.292Z",
  "mentions": [],
  "mention_roles": [],
  "mention_channels": [],
  "embeds": [
    {
      "color": 0,
      "description": "t",
      "timestamp": "2026-02-21T22:14:25.975Z",
      "type": "rich",
      "id": "embed_45"
    }
  ],
  "attachments": [],
  "stickers": [],
  "reactions": [],
  "call": null,
  "state": "SENT",
  "nonce": "17863863655622150162",
  "blocked": false
}
Message AST:
{
  "embeds": [
    {
      "embed_index": 0,
      "embed_type": "rich",
      "description": {
        "content": "t",
        "ast": {
          "nodes": [
            {
              "type": "Text",
              "content": "t"
            }
          ]
        },
        "parseTime": 0.10000000149011612
      }
    }
  ]
}
  1. Jackuczys changed the status from Awaiting confirmation to Fixed

3 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote edited
Status changed from Fixed to Awaiting confirmation
This may be fixed in the current version. If it still happens for you, please say so here.