In Europe, that would be 11:11 11/1/11
Disrupting the Borg is expensive and time consuming!
Google Search
-
Recent Posts
- UK Green Energy Record
- UN Is Upset
- “Fascist Salute”
- Record Warmth Of January 1906
- Heat Trapping Difficulties
- Visitech – Data Made Simple – Antarctic Sea Ice
- Visitech – Data Made Simple
- California Governor Refused Firefighting Help
- Internet For Drowned Island
- A Toast To President Trump
- 97% Of Government Experts Agree
- Green Energy Progress
- Scientists Concerned
- New Data Tampering By NOAA
- Magical Thermometers
- Responsive Government In California
- Collapse Of The Antarctic Sea Ice Scam
- NPR : Cold And Snow Caused By Global Warming
- Snow Forecast In All 53 States
- 97% Consensus
- “Melting ice reveals millennia-old forest buried in the Rocky mountains”
- America Burning
- Mediterranean Britain
- Californians Celebrate Annual Wildfire Tradition
- June 17, 1917 In California
Recent Comments
- Francis Barnett on UK Green Energy Record
- Greg in NZ on Record Warmth Of January 1906
- Disillusioned on “Fascist Salute”
- Francis Barnett on “Fascist Salute”
- Yonason on “Fascist Salute”
- Yonason on “Fascist Salute”
- Yonason on “Fascist Salute”
- Yonason on “Fascist Salute”
- Bob G on “Fascist Salute”
- arn on “Fascist Salute”
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