git.iko.soy/urbit.org
on master help sign in
svg margin/width fixes across all pages
7579fbfé
content/understanding-urbit/people-history.md+1−1
compare with master
unifiedsplit
@@ -41,7 +41,7 @@ For those interested in contributing there are some simple instructions on [GitH
41
41
42We 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.
42We 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.
43
43
44−![](https://media.urbit.org/site/understanding-urbit/project-history/history-4.svg)
44+<img class="full w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/project-history/history-4.svg"/>
45
45
46At the beginning, Urbit was just a few people with the right combination of imagination and discipline to try to rebuild computing.
46At the beginning, Urbit was just a few people with the right combination of imagination and discipline to try to rebuild computing.
47
47
content/understanding-urbit/urbit-id.md+1−1
@@ -37,7 +37,7 @@ You can also call stars ‘infrastructure nodes’ and galaxies ‘governance no
37
37
38And 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.
38And 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.
39
39
40−![](https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-address-space-1.svg)
40+<img class="full w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-address-space-1.svg"/>
41
41
42At a high level, there are three important things to understand about the overall Urbit ID system design.
42At a high level, there are three important things to understand about the overall Urbit ID system design.
43
43
content/understanding-urbit/urbit-os.md+1−1
@@ -39,7 +39,7 @@ The entire Urbit OS stack, from programming language to applications, is upgrade
39
39
40Since 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.
40Since 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.
41
41
42−![](https://media.urbit.org/site/understanding-urbit/network-os/urbit-os-diagram-apart.svg)
42+<img class="full w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/network-os/urbit-os-diagram-apart.svg"/>
43
43
44On 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.
44On 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.
45
45
content/understanding-urbit/urbitos1-osn.md+3−3
@@ -20,7 +20,7 @@ In early 2020, we’ll release what we’re calling OS 1 — the first minimal b
20
20
21We’ve got a pretty clear picture of OS 1, 2 and 3 which we’ll explain in [the roadmap](/understanding-urbit/roadmap). Here, we’ll focus on the vision for Urbit as a user experience.
21We’ve got a pretty clear picture of OS 1, 2 and 3 which we’ll explain in [the roadmap](/understanding-urbit/roadmap). Here, we’ll focus on the vision for Urbit as a user experience.
22
22
23−![](https://media.urbit.org/site/understanding-urbit/project-history/uu-osn-1.svg)
23+<img class="full w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/project-history/uu-osn-1.svg"/>
24
24
25In the current world of apps and services, there’s no operating system in any meaningful sense. Our laptops and phones just let us switch between services. Our communities, co-workers and lives are spread between these services — and the work of combining them is left to the user. You have to remember all your passwords, who sent what message where, what files are on which platform, and so on.
25In the current world of apps and services, there’s no operating system in any meaningful sense. Our laptops and phones just let us switch between services. Our communities, co-workers and lives are spread between these services — and the work of combining them is left to the user. You have to remember all your passwords, who sent what message where, what files are on which platform, and so on.
26
26
@@ -42,7 +42,7 @@ Think of a module like a particular way of communicating. Usually, groups have a
42
42
43Creating a group and customizing the modules it shares is easy. Building a new module is pretty straightforward as well, no more difficult than building an iOS app — although you do have to learn about the Urbit stack.
43Creating a group and customizing the modules it shares is easy. Building a new module is pretty straightforward as well, no more difficult than building an iOS app — although you do have to learn about the Urbit stack.
44
44
45−![](https://media.urbit.org/site/understanding-urbit/uu-osn-3.svg)
45+<img class="full w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/uu-osn-3.svg"/>
46
46
47We think this basic metaphor can scale, over time, to be useful in many different contexts.
47We think this basic metaphor can scale, over time, to be useful in many different contexts.
48
48
@@ -54,7 +54,7 @@ A new tenant in a building could use an Urbit workspace to lock and unlock doors
54
54
55This model provides for unending possible combinations for ordinary users, without increasing complexity for developers. It’s clear to us what this can look like in the short term. What the zoomers will do with it is beyond our imagination.
55This model provides for unending possible combinations for ordinary users, without increasing complexity for developers. It’s clear to us what this can look like in the short term. What the zoomers will do with it is beyond our imagination.
56
56
57−![](https://media.urbit.org/site/understanding-urbit/uu-osn-4.svg)
57+<img class="full w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/uu-osn-4.svg"/>
58
58
59Centralized services are great at replacing broadcast media: distributing content from a producer to a bunch of followers.
59Centralized services are great at replacing broadcast media: distributing content from a producer to a bunch of followers.
60
60