Your Discord bot's timestamp says the year 58970 (I tested 16 edge cases)

Discord turns <t:1798765200:F> into a date shown in each reader's own time zone. The format is documented, but what Discord does with bad input isn't. Bots generate these strings, and bots get the input wrong, so on 4 November 2026 I sent 16 malformed or extreme codes to a private server from the Discord web client and read back what rendered. Code What it tests Discord showed <t:1798765200:F> Normal Friday, January 1, 2027 at 6:30 AM <t:1798765200000:F> Milliseconds by mistake Tuesday, August 7, 58970 at 9:30 PM <t:0:F> Zero Thursday, January 1, 1970 at 5:30 AM <t:-86400:F> Negative Wednesday, December 31, 1969 at 5:30 AM <t:2147483648:F> One past the 32-bit limit Tuesday, January 19, 2038 at 8:44 AM <t:8640000000000:F> Largest JavaScript date Saturday, September 13, 275760 <t:8640000000001:F> One second past that raw text <t:0001798765200:F> Leading zeros renders normally <t:1798765200> No style lett