3 ms·

Everybody has a project they kick around in the back of their head but will probably never get around to doing. My project is an O/S. It should be built from t

Everybody has a project they kick around in the back of their head but will probably never get around to doing. My project is an O/S. It should be built from the ground up to be networkable, self-updating, and handle biometrics and P2P trust. And of course heavy use of encryption. In addition, it should operate along two streams: everything should have an execute and a verify stream running simultaneously. The reason this is my dream project is that we've reached the point where several weaknesses of the existing architecture are coming together to create problems. They need to be solved at the lowest level possible in the stack. I agree with the author: the initial decentralized nature of the internet has been perverted by all of the major players. There is a brutal fight underway by big companies trying to build walled gardens. These companies do not have my best interests in mind.

walterbell 12y ago
> In addition, it should operate along two streams: everything should have an execute and a verify stream running simultaneously. What would a "verify stream" do ... input validation, regression testing, anomaly detection, ..? Would it be verifying code or data or endpoint identity?
- DanielBMarkham 12y ago
  I've been listening to the TDD guys for some while, and I think they may be on to something that's lot more important than just writing code. They describe TDD as "double entry bookkeeping". That is, you enter things in twice and then you always have a cross-check to make sure you prevent errors. The same theory is in action in most modern commercial airline cockpits: one person could fly the plane alone, but there's a purposeful redundency built into the system -- a cross check. Same goes for flight control hardware: one system is never enough. I'm sold. I want everything I own, from the metal on up, to consist of competing and cross-checking systems, ideally open source from different groups. So to answer your question, yes. All of it. It's got to be baked in everywhere. Sketching this out on the back of a napkin somewhere would be a hoot.

walterbell 12y ago

> In addition, it should operate along two streams: everything should have an execute and a verify stream running simultaneously. What would a "verify stream" do ... input validation, regression testing, anomaly detection, ..? Would it be verifying code or data or endpoint identity?

DanielBMarkham 12y ago
I've been listening to the TDD guys for some while, and I think they may be on to something that's lot more important than just writing code. They describe TDD as "double entry bookkeeping". That is, you enter things in twice and then you always have a cross-check to make sure you prevent errors. The same theory is in action in most modern commercial airline cockpits: one person could fly the plane alone, but there's a purposeful redundency built into the system -- a cross check. Same goes for flight control hardware: one system is never enough. I'm sold. I want everything I own, from the metal on up, to consist of competing and cross-checking systems, ideally open source from different groups. So to answer your question, yes. All of it. It's got to be baked in everywhere. Sketching this out on the back of a napkin somewhere would be a hoot.