dangeredwolf
commented
11 months ago Duplicate of #120, the main issue is that Discord's (now-broken?) original embeds are essentially bot/webhook embeds which is an important distinction because they offer richer functionality than 3rd party websites are able to offer using their completely different kind of embed. What this means is that referencing dates in a relative way (i.e. 24 minutes ago) doesn't work as we can't update it, and absolute dates (i.e. 2023/11/06 @ 12:30) presents a number of unique issues:
- We can only guess date localization based off of tweet language as we have to handle this manually, it isn't handled automatically like with bot/webhook embeds
- We can't display the user's local time because we have zero way of knowing it
- We can assume this for some languages (i.e. for Japanese, Japan Standard Time is a fair assumption), but not for English and many others
- We could display the time in UTC, but this may be confusing for the less technically-inclined
For these reasons, I chose not to implement them. If I could find some kind of way to add the date without delivering a compromised experience then I certainly would, but at the moment it doesn't seem to be possible. I would love to be proven wrong or for Discord to add more functionality to their embeds, though.
(Also no, you can't use Discord formatting in website embeds either)
Old twitter embeds in discord used to include a timestamp, this was very useful and is sorely missing in current fixtweet embeds in discord.