recently a live-stream from six years ago popped up on %radio. early urbit fanatics were reading through the "new" urbit whitepaper .
this along with current breakthroughs like nock being used for zero-knowledge proofs inspired me to try and understand the lowest level of urbit code.
can this bird-brain handle it?
my intentions was to write down my thought process of learning nock while I stepped thru the docs to understand it. but as it turns out, a much better personal guide already exists.
I really enjoy the style and tone. it's setup perfect for my kind of learning!
so just go read ~timluc-miptev's nock guide.
your feathered friend,
bird
ps. I like the look so much I copied it here.
pps. one thought struck me while going through the guide.
nock doesn't really exist!. it's completely virtual. right now the only thing nock is is a specification. so nothing actually runs nock. it's up to whatever machine an urbit is on to execute the nock specification as purely as possible.
nock and therefore urbit is insolated from the world, floating above it in a virtual machine.
this helps to drive home the concept of kelvin versioning and how urbit is an opportunity within the middle layer of our digital world to freeze everything so completely we can continue to innovate on the machines below that it runs on, and expand up and outward with brand new ways for computers to interconnect between themselves and integrate into our lives.
it's a big dream, this urbit has.
|install %radio ~nodmyn-dosrux