on master help sign in
update image tags in understanding-urbit
commit3ac73ae5f091dcfbefe21c38de1ef8344c332d38 authorGavin Atkinson <gvnatknsn@protonmail.com> dateMon 19 Jul 2021, 13:48 (5 years ago) parent06c0f40
4 files changed+31−35
content/understanding-urbit/interface.md+5−6 content/understanding-urbit/people-history.md+5−8 content/understanding-urbit/urbit-id.md+6−6 content/understanding-urbit/urbit-os.md+15−15
content/understanding-urbit/interface.md+5−6
@@ -20,8 +20,7 @@ Landscape is by no means the only possible interface for Urbit OS + Urbit ID, bu
2020
2121But we’ll get into that later. First, we’ll talk about why we built Landscape, where it is now, and where it’s going. Then we’ll cover a bit about other interface possibilities.
2222
23−
24−<img class="" src="https://media.urbit.org/site/understanding-urbit/project-history/uu-osn-1.svg">
23+![](https://media.urbit.org/site/understanding-urbit/project-history/uu-osn-1.svg)
2524
2625What problem is Landscape solving? Let’s start with the current situation when it comes to cloud services.
2726
@@ -39,7 +38,7 @@ In March 2020 we shipped the first public version of Landscape, OS 1, to the net
3938
4039OS 1 is a minimal, multipurpose interface for bringing a group together to chat, share links, write and engage in discussion. OS 1 is free of any ads, tracking, or surveillance (as is the norm for anything built on Urbit). OS 1 is a stripped-down social utility designed for high-trust, direct communication and collaboration. OS 1 is the place for small communities to feel at home.
4140
42−<img class="ba" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/uu-interface-3.png">
41+![](https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/uu-interface-3.png)
4342
4443We built OS 1 for ourselves. We were sick of using centralized, mainstream software. We didn’t want to be stuck switching between bloated, monolithic services in order to keep in touch and move our work forward. We were done relying on some third party to take care of our community—so we exited to Urbit, and it feels good.
4544
@@ -49,7 +48,7 @@ If you’re curious to get a complete overview of OS 1, check out [this post](ht
4948
5049Our target with OS 1 was to produce the [Nokia 3310](https://en.wikipedia.org/wiki/Nokia_3310) of cloud computers. Something bordering on simplistic, but still nice to use. We hit that target, but it’s just the first milestone. Let’s talk a bit about how Landscape grows and matures at a high level (for more specifics on the near-to-medium term, check out [the roadmap](https://urbit.org/understanding-urbit/roadmap/)).
5150
52−<img class="ba" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/uu-interface-4.png">
51+![](https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/uu-interface-4.png)
5352
5453Landscape has two basic building blocks: groups and modules. A group is exactly what it sounds like: one or more people. A module is sort of like an app without the data lock-in. A module is just a tool for getting something done, like ‘tasks’, ‘links’ or ‘votes’ that’s shared by a group.
5554
@@ -63,9 +62,9 @@ When we look forward to what we can do with Landscape in the future, it’s hard
6362
6463Landscape is for everything else. Landscape is for actual two-way communication.
6564
66−<img class="ba" src="https://media.urbit.org/site/understanding-urbit/your-last-computer/your-last-computer-waves%402x.png">
65+![](https://media.urbit.org/site/understanding-urbit/your-last-computer/your-last-computer-waves%402x.png")
6766
6867Our desire to build a single place to work together isn’t driven just by convenience
6968(although it is quite convenient). The way we see it, [real communities need to have real ownership over the spaces they inhabit](https://urbit.org/blog/urbit-is-for-communities/). When communities use industrial-grade, one-size-fits-all software they feel as sterile as the software they use. That world always felt a bit like living in a planned community. We’d rather live in the countryside.
7069
71−We think Landscape can evolve into something even *more* powerful, cleaner, and more satisfying to use. Landscape is neither a social network nor productivity software. Landscape isn’t centrally controlled or passively surveilled. Landscape is something entirely new. It’s software that’s tailored to the people who use it, by the people who use it.
70+We think Landscape can evolve into something even _more_ powerful, cleaner, and more satisfying to use. Landscape is neither a social network nor productivity software. Landscape isn’t centrally controlled or passively surveilled. Landscape is something entirely new. It’s software that’s tailored to the people who use it, by the people who use it.
content/understanding-urbit/people-history.md+5−8
@@ -15,7 +15,7 @@ Today, Urbit is built and maintained by two companies, a community of contributo
1515
1616Let’s talk first about these individual groups within the Urbit community, then about the history of the project and how it came to be.
1717
18−<img class="ba" src="https://media.urbit.org/site/understanding-urbit/project-history/project-status-landscape-earth@2x.png">
18+![](https://media.urbit.org/site/understanding-urbit/project-history/project-status-landscape-earth@2x.png)
1919
2020There are currently two independent companies that work on building Urbit full-time: [Tlon](https://tlon.io/) and [urbit.live](https://urbit.live/).
2121
@@ -31,12 +31,9 @@ The community of contributors and core developers has been steadily contributing
3131
3232When the Urbit ID address space went on-chain in early 2019 there were about 2,000 star holders and 70 galaxy holders – that number has since grown steadily. For the most part, the best way to connect with them is through Urbit itself.
3333
34−<img class="ba"
35−src="https://media.urbit.org/site/understanding-urbit/uu-people-history-2a.jpg"/>
34+![](https://media.urbit.org/site/understanding-urbit/uu-people-history-2a.jpg)
3635
37−<img class="ba"
38−src="https://media.urbit.org/site/understanding-urbit/uu-people-history-2c.jpg"
39−/>
36+![](https://media.urbit.org/site/understanding-urbit/uu-people-history-2c.jpg)
4037
4138Given how new and unusual Urbit is, it attracts a wide variety of interesting people — both technical and non-technical. The community is generally happy to talk to people about what Urbit is, what we’re up to, and where we’re going. The best way to get involved is to simply join the Urbit Community at `~bitbet-bolbel/urbit-community` — which our [setup instructions](/using/os/getting-started) can help you do.
4239
@@ -44,7 +41,7 @@ For those interested in contributing there are some simple instructions on [GitH
4441
4542We also run a bi-monthly course called ‘Hoon School’ to teach people about the system. Hoon School is designed for anyone with the most basic technical skills — you don’t have to be an expert programmer. If you’re interested, you should [apply](/community/hoonschool). We accept everyone we can and only close the class when it gets too big.
4643
47−<img class="full w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/project-history/history-4.svg"/>
44+![](https://media.urbit.org/site/understanding-urbit/project-history/history-4.svg)
4845
4946At the beginning, Urbit was just a few people with the right combination of imagination and discipline to try to rebuild computing.
5047
@@ -91,7 +88,7 @@ urbit.live gets going and starts selling Urbit IDs to the public.
9188
9289Tlon spends the year stabilizing Arvo and building OS 1.
9390
94−<img class="ba" src="https://media.urbit.org/site/understanding-urbit/uu-history-4.jpg"/>
91+![](https://media.urbit.org/site/understanding-urbit/uu-history-4.jpg)
9592
9693Building Urbit is about building a future where technology doesn’t control us. Instead, we look forward to a future where technology is simpler, more reliable and less invasive.
9794
content/understanding-urbit/urbit-id.md+6−6
@@ -9,13 +9,13 @@ hide_previous_title = "true"
99image = "https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-cards%402x.png"
1010+++
1111
12−Assuming Urbit OS is simple enough for an ordinary user to own and operate, how do they log in? How do people identify one another on this new network? When people want to get data, files and messages to one another, how do they do it? And how do we prevent spam?
12+Assuming Urbit OS is simple enough for an ordinary user to own and operate, how do they log in? How do people identify one another on this new network? When people want to get data, files and messages to one another, how do they do it? And how do we prevent spam?
1313
1414Urbit ID is the answer to all these questions. Urbit ID is a decentralized addressing and public key infrastructure designed for Urbit OS.
1515
1616Let’s talk first about what an Urbit ID is and what it does. Then we’ll cover our design goals and how the system works overall.
1717
18−<img class="ba" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-cards%402x.png">
18+![](https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-cards%402x.png)
1919
2020Your Urbit ID is a short, four-syllable name like `~ravmel-ropdyl` that you own with an eight-syllable master passkey like `~palfun-foslup-fallyn-balfus`. This name and key lets you log into Urbit OS, and it’s used to encrypt packets you send over the Urbit network. Soon it will also be a master key that allows holding and sending of Bitcoin and other cryptocurrencies. Your Urbit ID and passkey belong to you like any other cryptographic assets. No one can take them away from you (just make sure to store the key safely).
2121
@@ -27,7 +27,7 @@ If you’re curious to see exactly how this system works, the code is of course
2727
2828Since the Urbit ID registry is live and deployed you can even [look at the chain](https://github.com/urbit/azimuth#live-contracts).
2929
30−<img class="ba" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-paperwallet%402x.png">
30+![](https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-paperwallet%402x.png)
3131
3232Each Urbit ID is really just a number. From that number we generate a pronounceable name and a visually identifiable sigil. `~dalwel-fadrun` is `3,509,632,436`, for example.
3333
@@ -37,7 +37,7 @@ You can also call stars ‘infrastructure nodes’ and galaxies ‘governance no
3737
3838And that's it. It's a simple system. What's important is why it is the way it is. Let's take a look at that.
3939
40−<img class="full ba w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-address-space-1.svg"/>
40+![](https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-address-space-1.svg")
4141
4242At a high level, there are three important things to understand about the overall Urbit ID system design.
4343
@@ -53,7 +53,7 @@ The Urbit ID sponsorship tree is not intended to be a social system in any way.
5353
5454Your relationship with your sponsor should be sort of like your ISP or a utility provider: a passive, non-invasive relationship. If it isn’t to your liking, moving to a new sponsor is very easy.
5555
56−<img class="ba" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-sigils%402x.png">
56+![](https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-sigils%402x.png)
5757
5858Urbit IDs are property, and we think of the entire registry of Urbit IDs as a vast territory of digital land.
5959
@@ -61,7 +61,7 @@ The scarcity of Urbit ID address space gives it value and that in turn helps boo
6161
6262When we launched the Urbit ID system, in January of 2019, there were a couple thousand different star and galaxy holders acting as stewards of this digital land. Since then, that number has been steadily on the rise.
6363
64−<img class="ba" src="https://media.urbit.org/site/understanding-urbit/project-history/uu-id-5.jpg">
64+![](https://media.urbit.org/site/understanding-urbit/project-history/uu-id-5.jpg)
6565
6666Ultimately, we want your Urbit ID to feel like a civilizational key. If your Urbit ID were a piece of hardware, you could tap it to unlock a door, swipe it to buy a coffee, and plug it into any computer to log in. Your Urbit ID should be a unique, beautiful object that’s both an address and a wallet. It’s a key to a secret club and the ticket to your digital life.
6767
content/understanding-urbit/urbit-os.md+15−15
@@ -9,29 +9,29 @@ hide_previous_title = "true"
99image = "https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-5.jpg"
1010+++
1111
12−For the most part, we use our laptops simply as access points to MEGACORP services. Our phones are the same. These services are amazing and convenient. But for that convenience we’ve traded away control, ownership and privacy. The way we live our digital lives is completely out of our hands.
12+For the most part, we use our laptops simply as access points to MEGACORP services. Our phones are the same. These services are amazing and convenient. But for that convenience we’ve traded away control, ownership and privacy. The way we live our digital lives is completely out of our hands.
1313
14−<img class="ba" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-5.jpg">
14+![](https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-5.jpg)
1515
16−Today’s MEGACORP monopolies retain their control because of one central technical advantage: they make the server side usable.
16+Today’s MEGACORP monopolies retain their control because of one central technical advantage: they make the server side usable.
1717
18−Urbit OS is built to break these monopolies at this central point of control. Urbit OS makes the server side usable for individuals without the need for MEGACORP to run their software.
18+Urbit OS is built to break these monopolies at this central point of control. Urbit OS makes the server side usable for individuals without the need for MEGACORP to run their software.
1919
20−We’ve already been through this before. In 1974 a computer was a mainframe the size of a room and was shared by hundreds of people. By 1984 a computer was the size of a desk and everyone had their own PC. The PC was more flexible and more fun, so it won by a wide margin. Then, with the rise of the internet, the PC’s flexibility slowly became irrelevant.
20+We’ve already been through this before. In 1974 a computer was a mainframe the size of a room and was shared by hundreds of people. By 1984 a computer was the size of a desk and everyone had their own PC. The PC was more flexible and more fun, so it won by a wide margin. Then, with the rise of the internet, the PC’s flexibility slowly became irrelevant.
2121
2222Today, we’re more or less back to the timesharing model of the 1970s. Urbit OS is the PC to MEGACORP’s mainframe. It’s more flexible, more fun, and most of all, poised to capture the everyday creativity of the individual.
2323
24−Let’s talk about how we think we’re going to pull this off from a technical standpoint, and our vision for using Urbit.
24+Let’s talk about how we think we’re going to pull this off from a technical standpoint, and our vision for using Urbit.
2525
2626If you’d like to skip ahead to what Urbit will be like to use [go ahead](/understanding-urbit/interface). Or if you’re someone who just wants to head to the source, [it’s here](https://github.com/urbit/urbit#urbit). In that case you may also want to [read the docs](https://urbit.org/docs/) to get up and running.
2727
28−<img class="ba" src="https://media.urbit.org/site/understanding-urbit/technical-overview/technical-overview-kernel@2x.png">
28+![](https://media.urbit.org/site/understanding-urbit/technical-overview/technical-overview-kernel@2x.png)
2929
30−Urbit OS is a completely new, carefully architected software stack: a VM, programming language, and kernel designed to run software for an individual. Urbit OS is a program that runs on almost any cloud server, most laptops and many phones: anything with Unix and an internet connection.
30+Urbit OS is a completely new, carefully architected software stack: a VM, programming language, and kernel designed to run software for an individual. Urbit OS is a program that runs on almost any cloud server, most laptops and many phones: anything with Unix and an internet connection.
3131
3232The main thing to understand about our ‘overlay OS’, as we call it, is that the foundation is a single, simple function. This function is the Urbit OS virtual machine. We call it ‘Nock’. The entire Urbit OS system compiles down to Nock, and Nock is just 33 lines of code.
3333
34−Nock is similar in spirit to WASM or the JVM: it’s a uniform machine code for every Urbit [ship](https://urbit.org/docs/glossary/ship/). A frozen foundation makes for some nice features:
34+Nock is similar in spirit to WASM or the JVM: it’s a uniform machine code for every Urbit [ship](https://urbit.org/docs/glossary/ship/). A frozen foundation makes for some nice features:
3535
3636The state of your Urbit OS is a pure function of its event history. It’s auditable, inspectable, repeatable. You can actually trust it.
3737Writing decentralized apps becomes vastly simpler than in the old world, since every node computes exactly the same way.
@@ -39,20 +39,20 @@ The entire Urbit OS stack, from programming language to applications, is upgrade
3939
4040Since Nock is a protocol for computing itself, any two nodes on the Urbit network can easily share data, communicate and connect their software. 20th century systems could never do this without a MEGACORP acting as the intermediary.
4141
42−<img class="full ba w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/network-os/urbit-os-diagram-apart.svg"/>
42+![](https://media.urbit.org/site/understanding-urbit/network-os/urbit-os-diagram-apart.svg")
4343
44−On top of this tiny VM we built a self-hosting, purely functional programming language, a kernel written in that language and a set of kernel modules that serve all the needs of personal computing. Specifically: a filesystem, build system, application sandbox, secret storage, web server, terminal driver and a networking protocol.
44+On top of this tiny VM we built a self-hosting, purely functional programming language, a kernel written in that language and a set of kernel modules that serve all the needs of personal computing. Specifically: a filesystem, build system, application sandbox, secret storage, web server, terminal driver and a networking protocol.
4545
4646This sounds like a lot — but the whole stack is incredibly compact. The whole system clocks in at around 50K lines of code. We’ve seen individual developers understand the entire thing. Who is the last person you met that actually understands their entire computer? Urbit OS is like the 1968 Porsche 911 of operating systems: extremely simple, elegant, and built for the individual.
4747
48−<img class="ba" src="https://media.urbit.org/site/understanding-urbit/project-history/uu-os-4.jpg">
48+![](https://media.urbit.org/site/understanding-urbit/project-history/uu-os-4.jpg)
4949
50−But why did we build all this technology?
50+But why did we build all this technology?
5151
5252First and foremost, to deliver a better user experience. Urbit OS alone is just a new layer for personal computing in the cloud. But with this new layer we open up the possibility of building a completely unified interface for people to compute in the cloud. (If you’d like to skip to how we envision that interface, [go for it](/understanding-urbit/interface).)
5353
54−From a broader perspective, it’s clear that connected computing is important and that it’s here to stay. We just want it to be as calm, simple and reliable as possible, and we don’t think that can happen using existing technology.
54+From a broader perspective, it’s clear that connected computing is important and that it’s here to stay. We just want it to be as calm, simple and reliable as possible, and we don’t think that can happen using existing technology.
5555
56−All of Urbit is built to function as a single stack, and we think that building a useful product is the best way to mature the system as a whole. That said, each component of this system can be used on its own. Don’t like our client? That’s okay, you can build your own. Don’t want to use Urbit OS? No problem — you can use Urbit ID as an authentication system for some other OS, or for anything, really.
56+All of Urbit is built to function as a single stack, and we think that building a useful product is the best way to mature the system as a whole. That said, each component of this system can be used on its own. Don’t like our client? That’s okay, you can build your own. Don’t want to use Urbit OS? No problem — you can use Urbit ID as an authentication system for some other OS, or for anything, really.
5757
5858Speaking of Urbit ID, let’s talk about what that actually is.