Urbit is a computer built with networking, ownership, and durability as foundational design principles. A computer that you can trust to be yours, forever.
@grok@justinmk@dcolascione Which would be easier to memorize and turn into your brain wallet, so that you can move your digital assets without a lick of presence in the physical world?
Here is a paper presenting a simple proof that Nock is Turing complete, how it relates to the SKI combinator calculus, and why Nock opcodes 0, 1, and 2 are a complete basis for computing.
https://t.co/goqRGrOV93
We talked a bit more about the faithless inference piece vs the specifics of what the models are doing, but its interrelated:
“How do you know a 3rd party provider isn’t actually just serving you a cheaper—and less trustworthy—model than what you think you are getting?���
https://t.co/hhEAZqhOT0
> |hi ~dirted-pallup
ai made me a @urbit vere manager for @dappnode
started with a fork of @androolloyd dappnode-urbit repo tho refactored a bunch and it ended up not really being the same
+external app EAuth login support so it can auth 2 cancel game
https://t.co/mWr2eNVkCW
> |hi ~dirted-pallup
ai made me a @urbit vere manager for @dappnode
started with a fork of @androolloyd dappnode-urbit repo tho refactored a bunch and it ended up not really being the same
+external app EAuth login support so it can auth 2 cancel game
https://t.co/mWr2eNVkCW
this is only true is your codebase is infinitely large.
which begs the question: why do you keep making your codebase infinitely large?
seems like it would be better to make the whole os, like, 225k lines of code or so.
Base-1353 encoding, so I can fit 256-bit values, like “96cca2a0c8a3263c74ef36274abf55f410d992034d16e8285811a9ad3fc59c13”, into short 26 character strings, like “ᓒᔳᣏዧᐎᑙᖜዌᙔᐸƫȶƃᒨዊጶᙵኻѫyፐᎉᑫᖫᘪᒩ”.
Also, I think these sigils are beautiful.
https://t.co/Xh6xLzEEfr