« first day (2696 days earlier)   

3:39 AM
My first thought is "Temple OS", what does that mean about me?
Like, do I link to en.wikipedia.org/wiki/TempleOS or their personal page with their name first? Er, just the "Temple OS" word might trigger people.
I mean, where the psychologists aren't/are not, is news.YCombinator.com, and then they're reading me and thinking "That must be their brain problem."
Then you have to deal with the psychologists that do not know what "C" is.
Then the other psycholiogist who thinks C is a human being.
And some psychologist just saying something about how Temple OS is written.
Oh, and some psychologist may have eventually figured how Temple OS is just one example, but most may only get as far as the Wiki page.
Far, meaning comprehension.
YCombinator threads are like what language is like not having a psychologists to a T.
Somewhat byte code made it to first place before ID checks in C.
Maybe even a DUI test, given alcohol is legal and causes problems.
C_DUI?
C_Psychologist?
C_ID_CHECK
Note for the psychologists who can not read very far but have to say they're understanding, ethically,... C_ID_CHECK does not exist. Sorry, I know you would think somewhat else but me was proposing that first.
C_ID_CHECK is my idea, (CC).
C_Psychology is at the root level of the low legal byte code in my version of Temple OS, might sober the issue.
I call it biblical computation (CC(amIthe1st?)), and you're correct I combined those words, very observcant.
C_Psychology has a logic checker for the Temple OS byte code.
Oh did the bible have an ID check, sorry, is that legal?
How does C not have an ID check at a low level?
You mean the EFF never asked about ID checks?
en.wikipedia.org/wiki/Single_sign-on is not running KYC and ID checks either, C would sollve for these exremeties.
Solve. In C.
Once you do byte code I guess you count that lettering too.
So that's Temple OS and byte hex speak coding, very not original, probably the standard human brain reaction, and Temple OS takes the heat. Figures, Temple OS is the problem not the lack of ID check in C (Then again, crucifying Mark Z like Bill G is fun.)
 
4:11 AM
C compilers could require C_ID_CHECK to run any command.
I mean how does GCC en.wikipedia.org/wiki/GNU_Compiler_Collection have a garbage collector and not an ID check function?
C_ID_CHECK is a threat to national security or profit?
LAW_C_ID_CHECK or C_ID_CHECK, which root level?
I mean hearings are fun, C is boring, but C works.
Lord YCombinator ie excellent at talking about Temple OS with a whiff or, well,...
Lord if YCombinator had to talk about Windows and Mac like Temple OS with the same cryptological (and backed by C references) hint vectors.
My prototype for Temple OS ID (I added ID, like "Iidentification, please"), my prototype operating system (OS) distribution, includes an ID check.
We could in 100 days require every EMT emitting electronic device to have an ID check by law, and I would approve, but that would mean profit issues.
LAW_C_ID_CHECK breaks many other functions, I am aware the base LAW function would need to be changed.
LAW function in many senses would be checking for ID.

First.
Temple OS ID adds LAW at the byte code level.
*Whiff of, well, solving every problem with legal-based OS Operating System requirements would break a lot of profit models. Somehow we got to making fun of Temple OS in tones, and electric cars with DUI checks, before C_ID_CHECK.
US law requiring ID checks for (required global variables? Same technology as a keyfog would enable proving who sent that sh.... I do not mind testifying, who exactly is fighting ID checks according to he Law?) general encounters = LAW_C_ID_CHECK?
US law requiring ID checks for general encounters = LAW_C_ID_CHECK?

Real ID cards coupled with real ID keyfob = "Operating Systems level change".

Real risk is profit models.
 
 
1 hour later…
6:12 AM
Real risk is influence (and under/influence) models.

All C as part of Temple OS ID spec API distro I just made over the weekend.
 

« first day (2696 days earlier)