Discord sends the message first and the unfurled embed seconds later as a MESSAGE_UPDATE carrying only embeds. discord.rs:2999 ignores an update with no content change, so that second event is dropped and the preview never renders — the link stays a bare URL forever.
Done looks like: an update carrying embeds patches the stored message's embeds even when content is unchanged. runtime.update_message already takes embeds.
Discord sends the message first and the unfurled embed seconds later as a `MESSAGE_UPDATE` carrying only `embeds`. `discord.rs:2999` ignores an update with no content change, so that second event is dropped and the preview never renders — the link stays a bare URL forever.
**Done looks like:** an update carrying embeds patches the stored message's embeds even when `content` is unchanged. `runtime.update_message` already takes embeds.
Salastil
added the bug label 2026-09-03 13:11:27 -04:00
Finished. Discord re-sends a message once it has finished unfurling a link, with no edited_timestamp — which the handler read as "nothing worth updating" and skipped, so the one thing that update did carry, the embed, was dropped. Most previews take a second, so most of them never appeared.
Only the embeds are taken from it. That update is a partial message object with no content, so reading a body out of it would replace what somebody wrote with an empty string — the stored body and attachments are kept as they were.
nobilis 6403192
Finished. Discord re-sends a message once it has finished unfurling a link, with no `edited_timestamp` — which the handler read as "nothing worth updating" and skipped, so the one thing that update did carry, the embed, was dropped. Most previews take a second, so most of them never appeared.
Only the embeds are taken from it. That update is a *partial* message object with no `content`, so reading a body out of it would replace what somebody wrote with an empty string — the stored body and attachments are kept as they were.
nobilis 6403192
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Discord sends the message first and the unfurled embed seconds later as a
MESSAGE_UPDATEcarrying onlyembeds.discord.rs:2999ignores an update with no content change, so that second event is dropped and the preview never renders — the link stays a bare URL forever.Done looks like: an update carrying embeds patches the stored message's embeds even when
contentis unchanged.runtime.update_messagealready takes embeds.Finished. Discord re-sends a message once it has finished unfurling a link, with no
edited_timestamp— which the handler read as "nothing worth updating" and skipped, so the one thing that update did carry, the embed, was dropped. Most previews take a second, so most of them never appeared.Only the embeds are taken from it. That update is a partial message object with no
content, so reading a body out of it would replace what somebody wrote with an empty string — the stored body and attachments are kept as they were.nobilis 6403192