In Europe, that would be 11:11 11/1/11
Disrupting the Borg is expensive and time consuming!
Google Search
-
Recent Posts
- Mission Accomplished
- Both High And Low Sea Ice Extent Caused By Global Warming
- Record Sea Ice Caused By Global Warming
- “Rapid Antarctic sea ice loss is causing severe storms”
- “pushing nature past its limits”
- Compassion For Terrorists
- Fifteen Days To Slow The Spread
- Maldives Underwater By 2050
- Woke Grok
- Grok Explains Gender
- Humans Like Warmer Climates
- Homophobic Greenhouse Gases
- Grok Explains The Effects Of CO2
- Ice-Free Arctic By 2027
- Red Hot Australia
- EPA : 17.5 Degrees Warming By 2050
- “Winter temperatures colder than last ice age
- Big Oil Saved The Whales
- Guardian 100% Inheritance Tax
- Kerry, Blinken, Hillary And Jefferson
- “Climate Change Indicators: Heat Waves”
- Combating Bad Weather With Green Energy
- Flooding Mar-a-Lago
- Ice-Free Arctic By 2020
- Colorless, Odorless CO2
Recent Comments
- Disillusioned on Mission Accomplished
- Bob G on Mission Accomplished
- James Snook on Both High And Low Sea Ice Extent Caused By Global Warming
- czechlist on Mission Accomplished
- arn on Record Sea Ice Caused By Global Warming
- Disillusioned on Record Sea Ice Caused By Global Warming
- Gamecock on “Rapid Antarctic sea ice loss is causing severe storms”
- Disillusioned on “pushing nature past its limits”
- Disillusioned on “pushing nature past its limits”
- czechlist on “Rapid Antarctic sea ice loss is causing severe storms”
What does that equal in binary?
Curiously enough, the answer is “it depends”. While a date and time may appear to simply be numbers, they are actually more complex representation of a specific notation system.
1st, binary is a base 2 system but typically was applied into a framework of 8 bit notation. thus 00000000 represents a 8 bit digit which could be translated into 0.
However, in computers the 8 bit digit is typically translated into ASCII where each of the 256 hexadecimal iterative forms of the 8 bit digit equals a standardized symbol, so that 00000000 now equals “null” and 31 equals 1, etc
Now, secondly we have an issue of how the calender is represented. Early computers abbreviated the year with only 2 hexadecimal digits to save storage space and also it got complicated by binary coded decimals introduction with and without floating points. As you can see, this is starting to get pretty complicated. In fact, it was complicated enough to generate the Y2K bug scare, if you recall some 10 years ago.
Needless to say, computers also need a mechanism for encoding time, which could be translated into a 24 hour military day and that numeric sequence stored as hexadecimal 00:01 or encoded into something else.
I am guessing you really don’t want any more detail, but if you do, there is enough here to get you on your way, rofl.
This was just a warm up for the real day 11:11 11/11/11 which is preparing us for 12:12 12/12/12. You will be sorry you did not listen to the warnings! It is going to be worse than we thought and we have not seen anything like it since measurements began and we will not see the event again within our lifetimes!
Take Heed the event draws near!
Indeed and so does the day after. 12:12 13/12/12 or 12:12 12/13/12, if you are a descendant of a former colonist.
Actually, in Europe and other SI (Système International) locales it would be (logically):
(20)11-1-11-11:11
I prefer this format 2011-01-11 11:11:11
Most software understands this format, and you can store dates in this format as strings and easily sort.
If you remove the – and the : you will get an auto grow number and easily sort.
20110111111111
20110111111112
20110111111113
…
20110111111159
20110111111201
…
tipping points
…
20121221122112
CO2 explodes in the atmosphere
EOF / EOW