There was a timezone issue with their code. Mastodon, in the mastodon way, found a way to contact the site owner and they got everything fixed. People can be great, when given the chance.
Something I find funny is that a lot of people who don’t know Star Trek that well and have only seen a couple of episodes assume Star Trek is the super optimistic view of humanity that is unrealistically positive about humanities future when if you actually look at the timeline in the 2000s and 2100s Star Trek is actually seriously apocalyptic. Humanity doesn’t turn to a good future out of some inevitable human kindness, it tries violence over and over again until some crazy guy makes a warp engine out of the rubble of destroyed civilization and the Vulcans show up.
It appears to be using JavaScript to count down, and JavaScript uses a browser's local time by default rather than something sensible like UTC. Someone else has noticed it in the Mastodon thread: https://aus.social/@[email protected]/111656784005786289
I mean wouldn't any sensible developer just use one of the many npm packages that do count down from UTC?
Which would also be using JavaScript?
Sorry I don't mean to quibble it's just that imo JavaScript has nothing to do with this faulty countdown, it has to do with the developer overlooking edge cases.