git.iko.soy/urbit.org
on master help sign in
svg margin/width fixes across all pages
commit7579fbfae25066c3e3cf32ed3ac47726e87cb8b5 authoré <edouard@urcad.es> dateThu 19 Dec 2019, 02:11 (7 years ago) parent894a156
4 files changed+6−6
compare with master
unifiedsplit
content/understanding-urbit/people-history.md+1−1 content/understanding-urbit/urbit-id.md+1−1 content/understanding-urbit/urbit-os.md+1−1 content/understanding-urbit/urbitos1-osn.md+3−3
content/understanding-urbit/people-history.md+1−1
@@ -41,7 +41,7 @@ For those interested in contributing there are some simple instructions on [GitH
4141
4242We 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.
4343
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"/>
4545
4646At the beginning, Urbit was just a few people with the right combination of imagination and discipline to try to rebuild computing.
4747
content/understanding-urbit/urbit-id.md+1−1
@@ -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−![](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"/>
4141
4242At a high level, there are three important things to understand about the overall Urbit ID system design.
4343
content/understanding-urbit/urbit-os.md+1−1
@@ -39,7 +39,7 @@ 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−![](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"/>
4343
4444On 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
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
2020
2121We’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.
2222
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"/>
2424
2525In 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.
2626
@@ -42,7 +42,7 @@ Think of a module like a particular way of communicating. Usually, groups have a
4242
4343Creating 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.
4444
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"/>
4646
4747We think this basic metaphor can scale, over time, to be useful in many different contexts.
4848
@@ -54,7 +54,7 @@ A new tenant in a building could use an Urbit workspace to lock and unlock doors
5454
5555This 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.
5656
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"/>
5858
5959Centralized services are great at replacing broadcast media: distributing content from a producer to a bunch of followers.
6060