31–40 of 62 posts
On a mac, you can keep track by opening the terminal and running the command "date +%s" (no quotes).
To see the countdown, you can use: while true; do echo $((1500000000 - `date +"%s"`)); sleep 1; done
Now, 500 million seconds later I'll be watching the counter on an ubuntu laptop. Not quite as late as I'm in Washington DC on business, and I abandoned /. a couple of years ago.
It amazes me how much changes, but also how little things change.
some info to save someone else from having to look it up 1 400 000 000 was 5/13/2014, 11:53:20 AM 1 600 000 000 will be 9/13/2020, 7:26:40 AM 1 000 000 000 was 9/8/2001, 8:46:40 PM 2 000 000 000 will be 5/17/2033, 10:33:20 PM 2^32-1 (4 294 967 295) will be 2/7/2106, 12:28:15 AM 100 million seconds is a little over 3 years 1 billion seconds is almost 32 years.
I remember 1e+9 because it shifted a log file over by 1 character. And less than a week later I was out of a job (travel industry).
I remember the 1234567890 celebrations. I saved the IRC log from #1234567890 on Freenode.
pastebin pls!
http://jordi.platinum.linux.pl/1234567890_prelim.txt.gz
I don't know what's going on with some of the encodings there, but I expect people were simply sending pre-UTF8 encodings.
Back in 2001 my social circle had a "gigasecond party" where we got together to cheer the moment of 1000000000. Like New Years, except that it was during the afternoon.
some info to save someone else from having to look it up 1 400 000 000 was 5/13/2014, 11:53:20 AM 1 600 000 000 will be 9/13/2020, 7:26:40 AM 1 000 000 000 was 9/8/2001, 8:46:40 PM 2 000 000 000 will be 5/17/2033, 10:33:20 PM 2^32-1 (4 294 967 295) will be 2/7/2106, 12:28:15 AM 100 million seconds is a little over 3 years 1 billion seconds is almost 32 years.
I remember 1e+9 because it shifted a log file over by 1 character. And less than a week later I was out of a job (travel industry).