18 comments

[ 3.2 ms ] story [ 44.2 ms ] thread
why for 21:39 it shows events for 439? I understand nothing found for 2139 but why 21: becomes 4?
It seems to pick a random century in this case.
I would assume it would go with 949, weird that it doesn't
I think that this may to prevent a loop-around where the same events are repeated in order twice a day.
My first though was that it would be doing modulo current year, so `2139 % 2023 = 116`. Not the case.
Would be neat if it wrapped around to BCE for future years.
Would be neater if it actually showed future events!
Why does my current time of 8:49PM (20:49) map to 949 and not 849?
"No events for [your time that doesn't have a corresponding event]"
"No events found for [your time, that doesn't have a corresponding event]"
That part I got. What isn’t obvious is how the mapping is being done. Why subtract 1100 and not 1200 (or 1000)
This reminds me of an art installation where the artist had filmed the outside of a Greenland village for one whole year and then compressed the footage so it would fit in roughly one hour. It is one thing to read about the Artic winter, and a very different one to see it take place day after day.

Reading some of the other comments, I’d like to suggest that it might be better to forgo the hour-year correspondence and adjust the simulation so that a whole run fits exactly in 24 hours.

There's a 12 minute a short film and timelapse over an entire year made in a remote and derelict town in the North of Norway as well, called A Year Along the Abandoned Road (Norwegian: Året gjennom Børfjord). The pop band A-HA used this short film in their music video Lifelines. The original short film featured music made by Jan Garbarek. It's well worth a peek.
> What is this?

> I often look at the clock and notice that the time matches the year of a well-known historical event, like 14:53 (the fall of Constantinople). I thought it'd be fun to turn this concept into a web app, using events from Wikipedia. Enjoy!