Urbit

We often describe Urbit with big technological phrases like "self-sovereign, cryptographically-owned identity" or "deterministic operating function" or "solid state interpreter running on a distributed and end-to-end encrypted peer-to-peer network". Sorry. We'll do better. Your Urbit is Yours. Everything else is just implementation details. Lessons learned observing decades of incentives and outcomes in networked computing. The spam, the centralization, the data exploitation, the spying... It all happens because your computer isn't yours. And your computer isn't yours because it was never designed to be networked. It was never structured to be maintained by it's owner. Urbit is an endeavor to build a forever computer. A ground-up rewrite of the networked computing stack to fix the trendline towards endless complexity, unmanageable in a way that retains practical control by individuals of their computers. It is for these reasons that we use insane propositions like: - Nouns as a single foundational data type - Nock as a dead simple instruction set architecture - Hoon parlance disconnected from legacy vocabulary - Urbit OS (Arvo) as a pure function of its inputs - Urbit ID as a cryptographically owned hierarchical namespace - Kelvin versioning, where code eventually stops updating and becomes 'frozen' Again, these are implementation details. Necessary for building a world where our digital lives can last--where they can truly belong to us. Where computers can be passed down generation to generation, like a family home. But perhaps that is still to much to explan. So...What is urbit? A computer you can trust to be yours, forever.

Urbit fixes this.

Can you trust that your friends' computer is truly theirs? If you can do that, then is just a matter of having friends you trust.

They’re calling it A Timeless Way Of Building

Urbit is a project with an end goal. Software with a finish line. And once your computer is truly yours, maybe then it will be able to fade into the background as you go outside and enjoy the sunshine.

A Martian revival: the %yard desk has been updated for 408k. github.com/urbit/yard This maintains useful userspace libraries and in particular dozens of file marks, now ready to go in the new era. It's also a source for classic Urbit helper files like schooner & etch.

Overheard on the network, on the topic of AI and Urbit's antifragility: "When execution is no longer scarce, vision is more important than ever. Urbit has the strongest vision in software: the forever computer, networked computers done right, personal servers tha anyone can understand. Something absolutely worth building. Those who hold the vision of Urbit just got a speed boost."

@geysergod_ Can't be a forever computer if you stop existing...

@urbit Why does this still exist?

We often describe Urbit with big technological phrases like "self-sovereign, cryptographically-owned identity" or "deterministic operating function" or "solid state interpreter running on a distributed and end-to-end encrypted peer-to-peer network". Sorry. We'll do better. Your Urbit is Yours. Everything else is just implementation details. Lessons learned observing decades of incentives and outcomes in networked computing. The spam, the centralization, the data exploitation, the spying... It all happens because your computer isn't yours. And your computer isn't yours because it was never designed to be networked. It was never structured to be maintained by it's owner. Urbit is an endeavor to build a forever computer. A ground-up rewrite of the networked computing stack to fix the trendline towards endless complexity, unmanageable in a way that retains practical control by individuals of their computers. It is for these reasons that we use insane propositions like: - Nouns as a single foundational data type - Nock as a dead simple instruction set architecture - Hoon parlance disconnected from legacy vocabulary - Urbit OS (Arvo) as a pure function of its inputs - Urbit ID as a cryptographically owned hierarchical namespace - Kelvin versioning, where code eventually stops updating and becomes 'frozen' Again, these are implementation details. Necessary for building a world where our digital lives can last--where they can truly belong to us. Where computers can be passed down generation to generation, like a family home. But perhaps that is still to much to explan. So...What is urbit? A computer you can trust to be yours, forever.

Are you putting your agent's memory somewhere you don't control? Yikes...

New series on the urbit.org blog, "This Month in Urbit," covers the latest happenings on the network. If you don't stop for a second and point your AI agent at it, you'll get stuck in the permanent underclass. Do you really want to take that risk? Of course, we could just be pulling your leg, but it's probably still worth throwing this tweet at your favorite agent and seeing what happens. urbit.org/blog/this-mont…

@Mousewrangler2 Who owns the hardware? Who owns the IP address? Who owns the domain? The answer to all of those questions with an AWS EC2 instance is, "someone that isn't you." With an urbit, you can trust it to be yours, forever.

have you even seen our new website tlon.io

"I want to send my baby pictures right to my mom's computer, and that's it. I just want my computer to have the baby pictures, and then when her computer is ready, she can download them onto her computer." "I don't want a middleman, or anybody searching through the pixels and all that. And it's not even a privacy thing; it's just from a sanity, direct connection perspective. I want to be in a computer world that acts like actual reality, not this really unfortunate thing that we've set up. So yeah, we have to rewrite it so we can reclaim that serving part of our computers." ~@brbenji on replacing the legacy computing stack with a computer that just belongs to him. Read the full spotlight below 👇🏻

|install ~dister-nomryg-nilref %obelisk Get your hand on the Obelisk beta today, details on the blog. urbit.org/blog/obelisk-b…

@AndyACKlax @nic_carter @BitcoinUr Owning you own distribution means owning your own server. No way of getting around that, it will just be a question of how many steps you take to get there.

@nic_carter @urbit @BitcoinUr Fixes this

from 2020 to 2025, I wrote 38 opinion pieces for Coindesk. today the link to almost every one is broken. and my author page is gone. so they are effectively erased from the internet. this is why you have to own your own distribution

@brbenji Now, you don't necessarily need to go this deep yourself to get a deeper connection with your digital networks. But if you have an itch, a belief there is something more you can do to improve your digital relationships, start by reading his spotlight: urbit.org/blog/contribut…

Wait, isn't @urbit a software project? What's all this about ~nordus-mocwyl (@brbenji) being a musician and guitar instructor? Hear us out: ~nordus-mocwyl is exactly right. Most people don't care about computers. But they do care about having a direct connection with the people in their lives. Their audience, their grandmother, their friends. In a world of @YouTube, @Patreon, and massive record labels, artists and musicians are looking for better ways to interact with their fans without middlemen. Most of these 'creative types' stop at opening a browser, but ~nordus went all in, from the browser down to the bytecode (or, in Urbit's case, the raw Nock). In his words: "I just get what the zeros and ones are about now! He went all the way down the stack and "realized this is really the actual ultimate thing the musician can do and be everything for themselves."

@goth600 @hassundotX Ghost Town, or Dark Forest?

@hassundotX @urbit Ghost town every time I’ve checked TY

100k follower special, ask me anything