A bug report was found on the BBS regarding Twitter embeds displaying UTC time instead of local time riking. codinghorror questioned how this could be implemented while maintaining the philosophy of oneboxes being baked in at the time of post creation. riking proposed reusing existing date and timezone semantics. codinghorror agreed to the idea as long as it’s easy to implement and retains the original onebox functionality. However, dylanb asked if the fix was ever implemented.
Bug report found on BBS: WATCH LIVE: Trump rioters break through barrier and are attempting to break into the Capitol - #426 by alahmnat - boing - Boing Boing BBS
Wait, where is it 11 PM? Where is he tweeting from? Can he tell us what’s going to happen in the next 5 hours, east coast time?
BBS pulls in tweet embeds with UTC timestamps for some reason.
Embeds with timestamps should be using local-dates if possible.
Given that the general philosophy of oneboxes is for them to be baked in at the time of post creation, how do you envisage this working? Will it show relative past times? Will it update in real time? Lots of unanswered questions here, some of them kinda complicated..
I was proposing to literally reuse this:
2021-01-06T20:34:00Z
Just keep whatever semantics we came up with for that.
Right, as long as it’s easy to do, and leverages the code we already have, I’m for it!
But the general philosophy of oneboxes is they bake in at the time of post for posterity, so we want to retain that. I’ve rebuilt HTML on posts where the tweet was deleted and then it goes from “useful onebox!” to “broken link that results in a sad lonely 404” 
Was a fix for this ever implemented?