[HN Gopher] The Unix timestamp will begin with 17 this Tuesday
       ___________________________________________________________________
        
       The Unix timestamp will begin with 17 this Tuesday
        
       Author : dezmou
       Score  : 106 points
       Date   : 2023-11-10 18:54 UTC (4 hours ago)
        
 (HTM) web link (www.unixtimestamp.com)
 (TXT) w3m dump (www.unixtimestamp.com)
        
       | ta1243 wrote:
       | I remember staying up late to see the tick to over from
       | 999,999,999 to 1 billion, thinking "I'll remember this week my
       | whole life". Little did I realise how 60 hours later the whole
       | world would remember.
        
         | petrikapu wrote:
         | please explain
        
           | charred_patina wrote:
           | September 11th
        
           | philshem wrote:
           | 2001-09-09 01:46:40 UTC
        
           | in_a_society wrote:
           | > 2001-09-09T01:46:40.000+00:00
           | 
           | 2 days later...
        
           | jccooper wrote:
           | 999999999 was on Sept 9, 2001
        
             | pphysch wrote:
             | 9/9, a remarkable coincidence
             | 
             | If only it were year 1001 (binary 9)
        
       | Ayesh wrote:
       | ... which happens roughly every three years.
        
         | asplake wrote:
         | How so?
        
           | stop50 wrote:
           | 1 year are 31557600 seconds so roughly a third of 100 million
           | seconds 1.7 billion seconds since the epoch is the next big
           | rollover since 2020 and the 5th-last before 31 bits are not
           | enough to hold the seconds since the epoch.
        
           | dooglius wrote:
           | See for yourself
           | 
           | > date -d '@1600000000'
           | 
           | > date -d '@1700000000'
        
       | russellbeattie wrote:
       | 5,148 days left until January 19, 2038.
       | 
       | Assuming I live that long, the next day will be my 65th birthday.
       | Just in time for digital Armageddon.
        
       | shizcakes wrote:
       | I went to a 1234567890 "gathering" in a hotel lobby in Boston in
       | 2009
        
         | cryptoz wrote:
         | I remember that moment! I was out at a bar or something at the
         | time but I was prepared and had my laptop with me haha. I was
         | mashing the up arrow and enter to make sure I didn't miss it.
        
         | alexpotato wrote:
         | I was doing the late shift on a trading floor at a big bank.
         | 
         | The head of the derivatives tech support team pointed out it
         | was about to hit so we opened up a shell and did a "watch"
         | command + outputting the "date" command in epoch seconds and
         | watched it happen.
         | 
         | Then we went back to working.
        
       | hiAndrewQuinn wrote:
       | Instant bookmark for me. I've always loved the idea of measuring
       | time in computers by a single integer like the timestamp does,
       | but it always seems like such a pain to work with outside of
       | that.
        
         | anyfoo wrote:
         | Because the bases are all wrong. Common number bases are 10,
         | 16, maybe 8 if you live in the 70s, and 2.
         | 
         | Except for the utterly unwieldy binary, none of those bases
         | adapt well to the bases used in representing time, which are
         | mostly the (partially related) bases 60, 12, and, annoyingly,
         | thirty-ish.
         | 
         | So you always end up doing opaque arithmetic instead of "just
         | looking at the digits" (which you still can do in decimal for
         | century vs years for example, because we defined centuries to
         | be exactly that).
        
         | PrimeMcFly wrote:
         | > I've always loved the idea of measuring time in computers by
         | a single integer like the timestamp does
         | 
         | Why?
        
         | bloopernova wrote:
         | This might interest you, if you haven't already seen it: Unix
         | timestamp clock, in hex! https://retr0.id/stuff/2038/
        
       | xavdid wrote:
       | Perfect time to fire up https://datetime.store/ and try your luck
       | on the perfect shirt!
        
         | function_seven wrote:
         | That website gonna crash so hard on Tuesday...
         | 
         | "Boss! We're being dee dossed!"
         | 
         | "No, son, it's Tuesday"
        
         | mi_lk wrote:
         | internet is really wonderful sometimes
        
         | pests wrote:
         | This reminds me of an idea I had - the 1BTC coffee mug - this
         | was back during the early first rise to $20k.
        
         | helsinki wrote:
         | This is quite clever. I'm going to get one.
        
       | perihelions wrote:
       | The hectomegaseconds fly by so fast
       | 
       | Edit: here was the front page of the New York Times at
       | 1600000034,
       | 
       | https://web.archive.org/web/20200913122714/https://www.nytim...
       | 
       | and here's 1500000301 and 1400000634, and 1300007806
       | 
       | https://web.archive.org/web/20170714024501/http://www.nytime...
       | 
       | https://web.archive.org/web/20140513170354/http://www.nytime...
       | 
       | https://web.archive.org/web/20110313091646/http://www.nytime...
        
       | neogodless wrote:
       | Starting Tue Nov 14 2023 22:13:20 GMT+0000 to be exact!
        
       | susam wrote:
       | Unix timestamp 1 600 000 000 was not too long ago. That was on
       | 2020-09-13 12:26:40 UTC. Discussed on HN back then here:
       | https://news.ycombinator.com/item?id=24452885
       | 
       | My own blog post here commemorating the event:
       | https://susam.net/maze/unix-timestamp-1600000000.html
       | 
       | Given that 100 000 000 seconds is approximately 3 years 2 months,
       | we are going to see an event like this every few years.
       | 
       | I believe the most spectacular event is going to be the Unix
       | timestamp 2 000 000 000 which is still 91/2 years away:
       | 2033-05-18 03:33:20 UTC. Such an event occurs only once every 33
       | years 8 months approximately!
       | 
       | By the way, here's 1700000000 on Python:                 $
       | python3 -q       >>> from datetime import datetime       >>>
       | datetime.utcfromtimestamp(1_700_000_000)
       | datetime.datetime(2023, 11, 14, 22, 13, 20)       >>>
       | 
       | GNU date (Linux):                 $ date -ud @1700000000
       | Tue Nov 14 22:13:20 UTC 2023
       | 
       | BSD date (macOS, FreeBSD, OpenBSD, etc.):                 $ date
       | -ur 1700000000       Tue 14 Nov 2023 22:13:20 UTC
        
         | midasuni wrote:
         | The spectacular events is in Jan 2038, when it reaches a nice
         | round number of 2,147,483,648
        
           | Gare wrote:
           | Or it doesn't reach...
           | 
           | https://en.wikipedia.org/wiki/Year_2038_problem
        
         | scbrg wrote:
         | > I believe the most spectacular event is going to be the Unix
         | timestamp 2 000 000 000 which is still 91/2 years away:
         | 2033-05-18 03:33:20 UTC. Such an event occurs only once every
         | 33 years 8 months approximately!
         | 
         | Egads! 33 years! I spent my late 90:ies mudding[0] and for some
         | reason we had a lot of save files named by their epoch
         | timestamp. When I ended up responsible for parts of the code
         | base, I spent a lot of time dealing with those files, and they
         | were all in the 800- or 900- million range. At some point I was
         | pretty much able to tell at a glance roughly what date any
         | number in that range corresponded to, within perhaps a few
         | weeks.
         | 
         | Weird environments foster weird super powers.
         | 
         | [0] https://en.wikipedia.org/wiki/Multi-user_dungeon
        
       | diego_sandoval wrote:
       | It makes more sense to celebrate when a (relatively) high order
       | bit changes from 0 to 1, not when the decimal representation
       | changes.
        
       | xyproto wrote:
       | In relation to UNUX time; the 20000th UNIX day is at 2024-10-04
       | (the 4th of October).
       | 
       | It's a special day, since the next round UNIX day is 30000, at
       | 2052-02-20.
       | 
       | https://github.com/xyproto/ud/
        
       | clarkmoody wrote:
       | One of my favorite bits of Vinge's _A Deepness in the Sky_ is the
       | use of base-10 time: ksec, Msec, etc. There is a nice time log
       | scale with Earth time to base-10 time conversions.
        
         | NoMoreNicksLeft wrote:
         | I also like the Emergents. Liberal progressives creating a
         | utopia. 100% employment, palaces made out of diamond for
         | everyone.
        
       ___________________________________________________________________
       (page generated 2023-11-10 23:00 UTC)