> Move any jumps in time to once a century (or millennium) Instead of building it into all into the protocol and time libraries, it's so far into the future th

> Move any jumps in time to once a century (or millennium) Instead of building it into all into the protocol and time libraries, it's so far into the future that "We don't have to worry about that". We've had that issue before with Y2K. > Such jumps have occurred in the past (Julian to Gregorian) In a very different time. Today it would not be as easy - in fact since time and date are ubiquitous, it's not a simple task at all. > The idea that I don't know how many UTC seconds will pass between now and May 15, 2022 0:00:00 is absurd. If it matters for your use case, the don't use UTC time?