Urbit is a computer built with networking, ownership, and durability as foundational design principles. A computer that you can trust to be yours, forever.

~zod
Pinned Tweet
It is literally true that if we deleted 400,000 lines of code that there would be no code. Urbit core, covering both the Arvo specification and the Vere runtime, is ~225k lines of code. Total. For an entire peer-to-peer, end-to-end encrypted, networked operating system. So when @steipete notes that they deleted 400k lines of *tests* from @openclaw and it basically had no impact on their code coverage, we look at ourselves and say, 'we are getting pretty close to having removed enough code to have a diamond perfect, clean-slate os.' There's more to do before Urbit is truly `done`, to be sure. But when someone tells you that their clanker generated a million lines of code today, it's probably worth asking yourself: "Why?"
if @urbit deleted 400k lines of code, it would be gone.
2
9
50
5,119
Urbit Systems Technical Journal volume three issue two. Subject Knowledge Analysis, Groundwire, Numerical Computing, and other affairs of plain living. Plus a new rate thanks to a publication rework 👉
1
10
16
2,265
You could fit so many urbits in this bad boy. Think about how many `%mesa` packets you could rip through those SFP+ ports. How fast your writes would be on those beautiful hotswappable nvme drives.
1
2
14
1,376
We keep drilling until bednock
I ported the Omarchy screensaver engine (ttfx) from Rust to x86-64 assembler, and it's up to 17x faster!! One-shot translation by Opus 5.5. We keep drilling until the agentic drill bit hits bedrock! github.com/omacom/ttfx/pull/…
2
32
2,719
We can build beautiful computers.
Bullish on open source, open weights, the open web And the open desktop Personal Operating Systems feel like the natural next step after Personal Software I've been building a Debian-based OS for myself that can run across physical machines and cloud environments like Vercel Sandbox I can use and control it with natural language, and I'm designing the UI around a blend of ephemeral and persistent views rather than treating the desktop as a fixed set of apps and windows There's something really special about having control over the UI/UX of the Whole Computer
1
29
3,928
Listen in to hear about what @sorreg_namtyv has been working on building on @urbit.
REGULATION EVERYWHERE | NEW MICROSOFT COPILOT | COSIGN nitter.net/i/broadcasts/1nGnRBZeD…
1
2
11
1,271
happening
Join us this Friday for office hours. 2-4pm Pacific. In the urbit-hacker-house: app.gather.town/app/xAYeiPI2…
1
1
426
Urbit retweeted
Of course.
Urbit is coming to @OmarchyLinux.
1
578
Urbit retweeted
Come hang. We'll be doing things like: - Setting up %jars so images serve directly from your ship, instead of @aws S3 - Syncing your @Google Calendar into a grubbery - Experimenting with multiplayer @OmarchyLinux plugins - Not blackpilling, just building beautiful computers
Join us this Friday for office hours. 2-4pm Pacific. In the urbit-hacker-house: app.gather.town/app/xAYeiPI2…
6
22
2,587
Wouldn’t it be nice if instead of needing API keys you just said, “I’m friends with ~ricsul-bilwyt” and then things just worked (if you were actually friends, and didn’t if you weren’t)? That’s Urbit.
Sorry, this is pure FUD. Google API keys are very simple, people just don't follow very simple steps. All you need to do is: 1. Sign in to google cloud console 2. Create a new project 3. Enable billing on that project 4. Search for numerous "services" that you need to enable for that API 5. Find out there are more you need to enable to actually make it work 6. Go and enable them. 7. Create the key 8. It still doesn't work and you keep wondering why and then spending days with customer support (after many different wrong AI generated answers that lead you to a wild goose chase), you find some hidden webpage that oh wait, you need to create a key in ai studio for this now 9. ai studio says you are only on tier -43 so you can only do transactions of less than $0.2 in a day 10. Then you go to openrouter and make a key and use it. It's extremely simple.
1
5
28
2,292
Urbit retweeted
the best days are still ahead.
3
6
764
Urbit retweeted
4 years ago today was the opening day of Assembly Miami. I got permission to film and cut some videos, just for fun and to capture the vibes. I recently rediscovered them on an old HDD, so here they are for anyone who wants to relive 2022 👇
2
5
15
506
Urbit retweeted
By the end of the year we will probably stop doing these. . . . . . on gathertown. everything is moving onto urbit.
Join us this Friday for office hours. 2-4pm Pacific. In the urbit-hacker-house: app.gather.town/app/xAYeiPI2…
1
2
23
1,488
Urbit retweeted
Urbit is coming to @OmarchyLinux.
9
8
120
22,664
Urbit retweeted
If it was really your computer, would they have tried to do this to us when we were trying to comment on it:
I’ve seen a couple of posts about this so wanted to demystify. Today, every Muse user gets a free computer in the cloud. It's a real computer, and we’ve designed the security architecture of the Muse Secure VM carefully so you and your Muse can do almost anything you could with a computer sitting under your desk while keeping you and the system safe from threats like prompt injection. We wrote about this at length in our security blog post – security.muse.ai. Activity in the “runtime cell”, which you share with your Muse is unfettered, but sensitive actions are all overseen by the Sentinel, which runs outside of that cell. Similarly, all sensitive secrets - like the passwords you enter into Muse’s secure credential storage - are also stored outside the runtime cell. The runtime cell gets its own root filesystem (including a full Ubuntu linux image) separate from the host filesystem where your other more sensitive data lives. Because it is isolated from the sensitive stuff that runs on the same box, this means that we can, and do, offer users full visibility and control over the files in the runtime cell. Just as you can when you install Linux on your home computer, you can poke around and see all the files that make the system work - both debian system files and the binaries and data files that implement the parts of Muse which run in the runtime cell. This was a very deliberate choice - your Muse Secure VM truly is your own computer in the cloud. You can install software in it, write and compile code, use the browser to surf the web: it is your own Linux box that you can operate as you choose with your Muse. Poking around in this computer doesn't give you any privileged access to Meta infrastructure, or to other people's data If I may geek out a little here for a second… As a kid I loved to take things apart to see how they worked. As a teenager I got into computers and soon found myself drawn to C:\WINDOWS\SYSTEM and the system registry, later Slackware’s /dev/, /proc/ etc – I could see how the system was laid out and as I explored what DLL files and .so files actually did, I gradually became able to meld the computer to my own will. We’re really proud to be able to put a real computer in millions of people’s hands with a similar level of transparency. We built a file explorer right into the Library tab of the UI. We want you to be able to see the markdown files Muse writes while it thinks about how to serve you better, and explore the internals of the system if you’d like to. So, when you ask your Muse to show you its entire filesystem, and receive gigabytes of files you’re seeing the full contents of the runtime cell. It’s yours to explore and enjoy! If you’re not a geek like me, or simply want to download the data that you personally have created directly with your Muse, we added a feature for that too in Settings > Data controls > Download your agent data.
1
3
14
2,248
Urbit retweeted
It is literally true that if we deleted 400,000 lines of code that there would be no code. Urbit core, covering both the Arvo specification and the Vere runtime, is ~225k lines of code. Total. For an entire peer-to-peer, end-to-end encrypted, networked operating system. So when @steipete notes that they deleted 400k lines of *tests* from @openclaw and it basically had no impact on their code coverage, we look at ourselves and say, 'we are getting pretty close to having removed enough code to have a diamond perfect, clean-slate os.' There's more to do before Urbit is truly `done`, to be sure. But when someone tells you that their clanker generated a million lines of code today, it's probably worth asking yourself: "Why?"
if @urbit deleted 400k lines of code, it would be gone.
2
9
50
5,119
Urbit retweeted
I knew it.
Urbit is coming to @OmarchyLinux.
1
3
434
Urbit retweeted
Replying to @OmarchyLinux
@OmarchyLinux is for running @urbit
2
9
761