git.iko.soy/urbit.org
on master help sign in
Merge pull request #329 from urbit/update/understanding-urbit-content

initial content replacements, structural edits to follow soon

commitc3cf2bf24952093117a50801e606e0c43831fbba authormatildepark <matilde@tlon.io> dateThu 19 Dec 2019, 15:55 (7 years ago) parent52f0442a3be62a
16 files changed+529−374
compare with master
unifiedsplit
content/understanding-urbit/simple-durable-yours.md → content/blog/simple-durable-yours.md+2−5 content/understanding-urbit/your-last-computer.md → content/blog/your-last-computer.md+2−5 content/understanding-urbit/interface.md+63 content/understanding-urbit/network-and-os.md−40 content/understanding-urbit/people-history.md+104 content/understanding-urbit/project-history.md−79 content/understanding-urbit/roadmap.md+80 content/understanding-urbit/technical-overview.md−47 content/understanding-urbit/urbit-id.md+30−37 content/understanding-urbit/urbit-os.md+58 content/using/develop.md+1−1 sass/_main.scss+4−3 templates/index.html+78−78 templates/partials/pagination.html+1−1 templates/understanding-urbit/list.html+71−77 templates/understanding-urbit/post.html+35−1
content/understanding-urbit/simple-durable-yours.md → content/blog/simple-durable-yours.mdrenamed+2−5
@@ -1,11 +1,8 @@
11+++
22title = "Simple, Durable, Yours"
3−description = "The core ideas that Urbit is built around"
4−weight = 1
3+date = 2019-10-17
4+description = "We built Urbit from scratch to be a system that’s simple, durable, and yours. Everything that computing today is not — but should be."
55[extra]
6−flatten_pagination = "true"
7−hide_next_title = "true"
8−hide_previous_title = "true"
96+++
107
118We live in a world dense with digital services. We see the world through them, we depend on them completely, and they’re not going away. They’re only becoming more ubiquitous.
content/understanding-urbit/your-last-computer.md → content/blog/your-last-computer.mdrenamed+2−5
@@ -1,11 +1,8 @@
11+++
22title = "Your Last Computer"
3−description = "What Urbit should feel like to an everyday user"
4−weight = 2
3+date = 2019-10-17
4+description = "Your Urbit is a simpler computer, a quieter computer, a more private computer. We want it to feel predictable, safe, and reliable — things only a complete, sealed system can do. This, we hope, can get us a world where technology keeps us connected, but doesn’t dominate our lives."
55[extra]
6−flatten_pagination = "true"
7−hide_next_title = "true"
8−hide_previous_title = "true"
96image = "https://media.urbit.org/site/understanding-urbit/your-last-computer/your-last-computer-waves%402x.png"
107+++
118
content/understanding-urbit/interface.mdnew file+63
@@ -0,0 +1,63 @@
1++++
2+title = "Interface"
3+description = "What Urbit feels like to an everyday user"
4+weight = 3
5+[extra]
6+flatten_pagination = "true"
7+hide_next_title = "true"
8+hide_previous_title = "true"
9++++
10+
11+We started at the bottom of the stack, years ago, with the VM. We’re just now getting to the top: the interface. Urbit ID and Urbit OS are great tools — but technology on its own isn’t enough. As far as we’re concerned, if people don’t actually use this thing, it doesn’t matter.
12+
13+Urbit, VM to UI, is meant to feel like the a desktop OS for a networked world: a single, unified system where you can interact with, update and archive all of your personal data; communicate with your friends and family; and collaborate with the people you work with.
14+
15+One way to imagine Urbit is as the Western answer to WeChat: a seamless, multi-purpose, vastly extensible social network, but without the surveillance. As a platform anyone can extend, we see Urbit as the ultimate productivity tool: no more frankenstack of apps and services needed for companies and collaborators, because everything lives in one interface. With the power to build whatever you want on top of Urbit, you can bring everything together in one place.
16+
17+In early 2020, we’ll release what we’re calling OS 1 — the first minimal but complete user experience for Urbit. OS 1 brings together the whole Urbit stack into a single interface. OS 1 is simple in the extreme. It’s a calm, ad-free, privacy-respecting environment to homestead new digital communities.
18+
19+We’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.
20+
21+<img class="full w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/project-history/uu-osn-1.svg"/>
22+
23+In 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.
24+
25+The most severely lacking thing about our digital lives today is that they lack a sense of place or a sense of home.
26+
27+It’s annoying and confusing to switch between interfaces, you can’t extend or build on top, and privacy and security are out of your hands. This fragmented, siloed, closely surveilled experience is simply a byproduct of having other people run and control your software. The result, for the ordinary user, is restrictive and boring. The possibility for everyday creativity with the tools we’re stuck with is close to zero. Wasn’t the computer supposed to be a bicycle for the mind?
28+
29+Operating systems for the PC took the desk of the 1970s and made it digital. Paper, drawers and envelopes became ‘files’ and ‘folders’. It’s a great abstraction, but it’s ancient. We live in a multiplayer, connected world; we need an operating system that knows that.
30+
31+The ‘desk’ of today is cluttered with apps and services, data structures and interfaces. Refactoring this, unifying it, is the most important problem that a platform like Urbit can solve. We want Urbit, as a user experience, to be a single system for bringing together a group of people to do many things together.
32+
33+<img class="ba" src="https://media.urbit.org/site/understanding-urbit/your-last-computer/your-last-computer-waves%402x.png">
34+
35+What exactly does this look like? In the long run, we’re not 100% sure. There’s a lot to be invented — but we have a first pass that we think is quite good. At least, good enough that we like using it quite a lot.
36+
37+In Urbit, there are two building blocks: groups and modules. A group is exactly what it sounds like: 1 or more people. A module is sort of like an app without the data lock-in. It’s just a tool for getting something done, like ‘chat’, ‘publish’, or ‘links’ that’s shared by a group. Any group on Urbit can combine modules, or build their own.
38+
39+Think of a module like a particular way of communicating. Usually, groups have a few different ways they want to communicate. Urbit makes this simple and straightforward. With one group, you may decide to chat and share photos. Another might share annotated research, watch the markets, and manage payments on a blockchain.
40+
41+Creating 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.
42+
43+<img class="full w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/uu-osn-3.svg"/>
44+
45+We think this basic metaphor can scale, over time, to be useful in many different contexts.
46+
47+For example, parents might give their young children an Urbit that’s locked, at first, to only two groups: family and friends from school. It might also be limited to one module: chat.
48+
49+A broader group of siblings, parents and grandparents might create a group with a few more modules to share photos, chat and coordinate events.
50+
51+A new tenant in a building could use an Urbit workspace to lock and unlock doors, pay their utilities and rent, and communicate with the landlord. The building owner could use an urbit workspace to keep up with all her tenants, accept rent payments, check on critical building systems and communicate with subcontractors.
52+
53+This 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.
54+
55+<img class="full w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/uu-osn-4.svg"/>
56+
57+Centralized services are great at replacing broadcast media: distributing content from a producer to a bunch of followers.
58+
59+Urbit is for everything else. That is, Urbit is for actual two-way communication: keeping a group of friends connected, staying in touch with your family, or working with a group of collaborators.
60+
61+We designed Urbit to become the best tool for communicating with friends and family, or collaborating with peers. It’s a social network, but much calmer and more purposeful. It’s a productivity tool, but much more secure and powerful.
62+
63+How do we get to this future? By staying focussed, writing code, and iterating through design. We have a rough outline of this process — let’s walk through it.
content/understanding-urbit/network-and-os.mddeleted−40
@@ -1,40 +0,0 @@
1−+++
2−title = "Urbit OS + Network"
3−description = "The Urbit OS + Network + how they work together"
4−weight = 5
5−[extra]
6−flatten_pagination = "true"
7−hide_next_title = "true"
8−hide_previous_title = "true"
9−image = "https://media.urbit.org/site/understanding-urbit/network-os/urbit-os-phones@2x.png"
10−+++
11−
12−
13−
14−Our phones are cluttered with apps, ads, and notifications. Our laptops are basically just web browsers that connect us to services controlled by MEGACORP. Who knows where your messages, images, contacts, and connections live, let alone how long they’ll last or who is looking at them?
15−
16−<img class="mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/network-os/urbit-os-phones%402x.png">
17−
18−The digital world feels like a theme park built to maximize ENGAGEMENT — but we think it’s BORING. What happened to the vision of a computer as a tool that would expand and enrich our lives?
19−
20−While the world has drifted into a fever dream, we built Urbit.
21−
22−<img class="mv5 ba w-100" src="https://media.urbit.org/site/understanding-urbit/network-os/urbit-os-diagram.svg">
23−
24−Your Urbit ID gets you a name, an address, and a crypto wallet — but what about when you want to connect with other people? That’s where Urbit OS comes in.
25−
26−Urbit OS is everything that you need to build and run your own social software and compute with whomever you like. Create a pseudonymous chat group, edit a document together, then split a bar tab and later turn it into a syndicate and start investing. Eventually, maybe you’ll decide to become a microstate that funds everyone in Bitcoin — the possibilities are wide open.
27−
28−Since we’ve got a decentralized identity system to build on and everyone runs their own OS, your social software is actually owned and operated by the collective of Urbit ID owners. You can (and should) do whatever you want.
29−
30−<img class="mv5 ba w-100" src="https://media.urbit.org/site/understanding-urbit/network-os/urbit-os-diagram-apart.svg">
31−
32−We built Urbit OS from scratch. It’s a completely new computing stack. Without getting into the technical details (you can find those [here](@/understanding-urbit/technical-overview.md)), Urbit OS is built to do three things: be a compact and complete system (simple); run forever with no maintenance (durable); and be extensible by anyone (yours).
33−
34−Urbit OS is a completely unified system with no external dependencies. In a single codebase, two orders of magnitude smaller than Linux, you have an entire programming language and operating system. We realize how crazy this is — but it means that a single person can actually understand the entire system. Who is the last person you met that actually understands their entire computer? Urbit OS is like the [1968 Porsche 911](https://cdn.bringatrailer.com/wp-content/uploads/2007/05/1968_Porsche_911_SR_Factor_Race_Car_Engine_1.jpg) of operating systems.
35−
36−At the very bottom of the stack, Urbit OS is just a single, fixed function that we never change. Everything on top is upgradeable over the network. This means your Urbit OS can run forever without you ever having to do any maintenance. Put it on a USB stick, throw it in a drawer for ten years, and forget about it. When you plug it in again, it’ll upgrade itself automatically.
37−
38−Since Urbit OS is completely sealed, it’s all run-from-source. All the code to run the system is yours to modify, tinker with, and extend. Build your own apps, modules, and user experience. Or customize Urbit OS to control your tractor. Even better: collaborate with others on the network to build the experience you’re looking for. It’s entirely up to you.
39−
40−We build Urbit OS so we can finally have a dependable system that we can commit to and keep far into the future. The modern web already looks dated to us.
content/understanding-urbit/people-history.mdnew file+104
@@ -0,0 +1,104 @@
1++++
2+title = "People + History"
3+description = "Where we've been and were we are now"
4+weight = 5
5+[extra]
6+flatten_pagination = "true"
7+hide_next_title = "true"
8+hide_previous_title = "true"
9+image = "https://media.urbit.org/site/understanding-urbit/project-history/project-status-landscape-earth%402x.png"
10++++
11+
12+So who builds this thing? Where does it come from? What’s the history?
13+
14+Today, Urbit is built and maintained by two companies, a community of contributors and core developers, infrastructure (star) operators, and governance (galaxy) node owners.
15+
16+Let’s talk first about these individual groups within the Urbit community, then about the history of the project and how it came to be.
17+
18+<img class="ba" src="https://media.urbit.org/site/understanding-urbit/project-history/project-status-landscape-earth@2x.png">
19+
20+There are currently two independent companies that work on building Urbit full-time: [Tlon](https://tlon.io/) and [urbit.live](https://urbit.live/).
21+
22+Tlon has been around since 2013 or so, and is primarily focussed on the development of Urbit OS and its user experience. Urbit.live was started in 2018 to make the onramp into Urbit as easy as possible. Both companies contribute regularly to the code base.
23+
24+Tlon was originally granted about half of the Urbit ID address space, and has used that to fund its operations so far. Over time, Tlon plans to offer hosting and services to make using Urbit as easy as possible.
25+
26+Tlon is also working to set up an urbit.org foundation. This is still in process, and is expected to happen in 2020.
27+
28+Urbit.live started selling Urbit IDs very early once that became possible, and also plans to offer services within the Urbit ecosystem.
29+
30+The community of contributors and core developers has been steadily contributing to the code base since before Tlon existed, and they’re still going strong. They can primarily be found on Urbit itself, in `~dopzod/urbit-help`, the [urbit-dev mailing list](https://groups.google.com/a/urbit.org/forum/#!forum/dev) and on [GitHub](https://github.com/urbit).
31+
32+When 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.
33+
34+<img class="ba"
35+src="https://media.urbit.org/site/understanding-urbit/uu-people-history-2a.jpg"/>
36+
37+<img class="ba"
38+src="https://media.urbit.org/site/understanding-urbit/uu-people-history-2c.jpg"
39+/>
40+
41+Given 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 `~dopzod/urbit-help` — which our [setup instructions](/using/operations/using-your-ship/) can help you do.
42+
43+For those interested in contributing there are some simple instructions on [GitHub](https://github.com/urbit/urbit/blob/master/CONTRIBUTING.md#contributing-to-urbit), but we also run a [grants program](https://grants.urbit.org/) where we reward contributors with Urbit ID address space. Grants aren’t solely for pre-determined projects, either. If you have something you’d like to propose, we’d love to hear from you.
44+
45+We 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.
46+
47+<img class="full w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/project-history/history-4.svg"/>
48+
49+At the beginning, Urbit was just a few people with the right combination of imagination and discipline to try to rebuild computing.
50+
51+**2002**
52+
53+Urbit starts as an open-ended personal project. An “independent study PhD” to reinvent computing for a network-centric world.
54+
55+**2008**
56+
57+Nock, the foundation of Urbit, works. Coming in at 32 lines of code, that’s 1 line of code every two months.
58+
59+**2012**
60+
61+Hoon, Urbit’s programming language, compiles itself to Nock. Writing Hoon is much easier than writing Nock.
62+
63+**2013**
64+
65+Arvo, Urbit’s OS kernel, boots and the first live Urbit network is started with a command-line chat.
66+
67+**2014**
68+
69+Tlon is founded to help support Urbit development (and is < 8 people for the next four years).
70+
71+**2015**
72+
73+Urbit has its first web interface and serves its own website.
74+
75+**2016**
76+
77+The first sale of Urbit address space sells out in four hours.
78+
79+**2017**
80+
81+Our test network runs for ten months without a reboot.
82+
83+Our private sale, shared only with our mailing list, sells out in six hours — limit two per person.
84+
85+**2018**
86+
87+Tlon sells about 8% of its stake in the network to accelerate Urbit development.
88+urbit.live gets going and starts selling Urbit IDs to the public.
89+
90+**2019**
91+
92+Tlon spends the year stabilizing Arvo and building OS 1.
93+
94+<img class="ba" src="https://media.urbit.org/site/understanding-urbit/uu-history-4.jpg"/>
95+
96+Building 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.
97+
98+Keep in touch while we make build this vision into reality by [joining our mailing list](https://urbit.us11.list-manage.com/subscribe/post?u=972a03db9e0c6c25bb58de8c8&id=be143888d2) or following us on [Twitter](https://twitter.com/urbit) or [GitHub](https://github.com/urbit).
99+
100+If you’re somewhat technical and you’d like to help and contribute, [install Urbit](/using/install) and consider [applying for a grant](https://grants.urbit.org/s).
101+
102+If you’re interested in homesteading a community when OS 1 comes out, [apply here](/community/community-grants).
103+
104+Or if you’re curious to try Hoon School, [let us know](/community/hoonschool).
content/understanding-urbit/project-history.mddeleted−79
@@ -1,79 +0,0 @@
1−+++
2−title = "Project Status + History"
3−description = "Where we've been and were we are now"
4−weight = 7
5−[extra]
6−flatten_pagination = "true"
7−hide_next_title = "true"
8−hide_previous_title = "true"
9−image = "https://media.urbit.org/site/understanding-urbit/project-history/project-status-landscape-earth%402x.png"
10−+++
11−
12−Can you move to Urbit today and never look back? Not quite yet. Urbit is still young.
13−
14−
15−<img class="mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/project-history/project-status-landscape-earth%402x.png">
16−
17−Currently, Urbit ID is live and deployed. That means you can own a piece of Urbit — if you can find one. There are thousands of people that can potentially invite you, and we give away invites from time to time. Your Urbit ID gets you a name, a sigil, and access to Urbit OS.
18−
19−<img class="mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/project-history/project-status-bridge%402x.png">
20−
21−You can interact with your Urbit ID and invite friends using [Bridge](https://bridge.urbit.org), the Urbit authentication system. You can also use Bridge to boot the current alpha of Urbit OS. Soon you’ll be able to use Bridge for payments and to explore the Urbit network.
22−
23−<img class="mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/project-history/project-status-landscape%402x.png">
24−
25−Urbit OS is a solid alpha. We use it every day to coordinate and chat about the future of Urbit. You’re [welcome to join](@/using/install.md). Our standards are high, so we aren’t asking everyone to use Urbit OS yet. If you’re someone who wants to customize their own software and experiment with a new system, [check it out](@/using/install.md). Otherwise, [join the mailing list](https://urbit.us11.list-manage.com/subscribe/post?u=972a03db9e0c6c25bb58de8c8&amp;id=be143888d2). We have exciting things planned for 2020.
26−
27−Urbit OS isn’t just an interface — it’s a complete system. You should also check out the [GitHub repository](https://github.com/urbit/urbit), our [open grants program](https://grants.urbit.org) and the [documentation](@/docs/_index.md). Building a system from scratch is a huge and enormously fun undertaking. There’s a lot going on, and we do all our development in public. Systems programmers, functional programming nerds, anyone who wants to tinker with their software will probably love playing with Urbit.
28−
29−<img class="mv5 w-100" src="https:///media.urbit.org/site/understanding-urbit/project-history/history-4.svg">
30−
31−At the beginning, Urbit was just a few people with the right combination of imagination and discipline to try to rebuild computing. Now it's a community of thousands of address space holders, dozens of open source developers, at least two independent companies ([Tlon](https://tlon.io) — which works mostly on kernel development and interface design, and [urbit.live](https://urbit.live) — which is building services on the platform), and who knows how many fans.
32−
33−<br /><br />
34−
35−## History
36−
37−<img class="mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/project-history/project-history-05.svg">
38−
39−## Roadmap
40−
41−<img class="mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/project-history/project-history-06.svg">
42−
43−## Future updates
44−
45−Urbit is young, but developing quickly. If you've just finished our Understanding Urbit series and want to stay connected with the project, we recommend starting with our mailing list.
46−
47−Enter your email below to get regular updates on the project.
48−
49−<iframe name="nothing" style="display:none;"></iframe>
50−<form
51−action="https://urbit.us11.list-manage.com/subscribe/post?u=972a03db9e0c6c25bb58de8c8&amp;amp;id=be143888d2"
52−method="post"
53−id="mc-embedded-subscribe-form"
54−name="mc-embedded-subscribe-form"
55−class="validate form"
56−target="_blank"
57−novalidate>
58−<div class="input-group" id="mc_embed_signup_scroll">
59− <div class="mc-field-group w-100 relative">
60− <input
61− class="bg-white black b--black ba pa3 w-100 mb2 br0 wk-appearance-none"
62− type="email"
63− name="EMAIL"
64− id="mce-EMAIL"
65− placeholder="your@email.com"/>
66− <button
67− id="mc-embedded-subscribe"
68− class="dib bn absolute bg-transparent"
69− style="font-family: 'Inter UI', san-serif; right: 3px; top: 15px; -webkit-appearance: none;"
70− type="submit"
71− name="subscribe"
72− onclick="_paq.push(['trackEvent', 'Mailing List', 'Subscribe'])">
73− <span class="fr pr1">-></span>
74− </button>
75− </div>
76−</div>
77−
78−You can also follow us on [Twitter](https://twitter.com/urbit) or [GitHub](https://github.com/urbit).
79−</form>
content/understanding-urbit/roadmap.mdnew file+80
@@ -0,0 +1,80 @@
1++++
2+title = "Roadmap: OS 1 -> OS N"
3+description = "The core ideas that Urbit is built around"
4+weight = 4
5+[extra]
6+flatten_pagination = "true"
7+hide_next_title = "true"
8+hide_previous_title = "true"
9++++
10+
11+Today, we call Urbit an ‘OS 0’. It’s an evolving open source project with a live network. In 2020, we’re planning to ship OS 1 — the first minimal but complete release of Urbit.
12+
13+As we discussed in the [last post](/understanding-urbit/interface), we see Urbit’s primary advantage as bringing together groups to share a set of modules for communication and collaboration. As Urbit matures, the set of available modules grows and expands, and the system both stabilizes and becomes more secure.
14+
15+Let’s walk through the sequence of milestones we have planned for 2020 and 2021.
16+
17+
18+![](https://media.urbit.org/site/understanding-urbit/project-history/project-status-landscape%402x.png)
19+
20+OS 0 — 2019
21+
22+Today, Urbit OS is an evolving prototype. Brave explorers, open-minded systems software nerds and those who want the future to arrive as fast as possible should [install Urbit](/using/install), [check it out](https://urbit.org/using/operations/), and potentially [enroll in Hoon School](/community/hoonschool).
23+
24+Urbit has evolved a lot during OS 0. We deployed the Urbit ID system to Ethereum and made huge strides toward the stability of Urbit OS (detailed [here](/blog/stable-arvo)). OS 0 has been all about refining our interface goals and making sure our system works as well as possible.
25+
26+Urbit is a community project, and the community hangs out on OS 0 to communicate and coordinate about developing the system. Come join us if you’d like to help, or just want to follow along as the system progresses.
27+
28+
29+
30+![](https://media.urbit.org/site/understanding-urbit/uu-roadmap-2.png)
31+
32+OS 1 — Q1 2020
33+
34+OS 1 is the first minimal but complete release of Urbit. We think of it as the [Nokia 3310](https://en.wikipedia.org/wiki/Nokia_3310) of cloud computers.
35+
36+OS 1 is a simple system to publish notes, chat and share links with groups of friends all in one place. OS 1 is stripped down, but open for anyone to extend and build on top of. It’s easy to onboard a group of friends into OS 1 via email and there will be hosting available to select groups.
37+
38+OS 1 is aimed first and foremost at communities looking to homestead a new platform they can truly make their own. We’ve been using Urbit ourselves over the years, and OS 1 is what we’ve been looking forward to using for our own daily communication and collaboration.
39+
40+While we’re excited about what OS 1 is, there are also plenty of gaps. For example, OS 1 doesn’t have an exceptional notification system, it still lives in a browser, and it lacks great tooling for distributing new modules. While we aren’t inventing any new cryptography, Urbit also hasn’t been audited, so we aren’t calling it secure just yet.
41+
42+If OS 0 is for explorers, OS 1 is for tinkerers. More like car camping than backpacking.
43+
44+Tlon is also planning to provide free hosting to a limited number of groups who want to homestead the system. (Although you can always host Urbit yourself, of course.) If you’re interested in trying OS 1 with your group of friends, [let us know](/community/community-grants).
45+
46+OS 2 is where Urbit gets easier for a broader audience to try out.
47+
48+
49+
50+![](https://media.urbit.org/site/understanding-urbit/uu-roadmap-3.png)
51+
52+OS 2 — Q2 2020
53+
54+OS 2 is an approachable, expanded and easier to use OS 1. We think of OS 2 as the [iOS 1](https://en.wikipedia.org/wiki/IPhone_OS_1) of cloud computers — no matter how silly that sounds.
55+
56+Like OS 1, OS 2 let’s a group of people chat, publish blogs and short messages, and share links. The main difference is that OS 2 is a standalone app (rather than the browser tab of OS 1) and supports Urbiit-to-Urbit payments in BTC and ETH. OS 2 is the calm, private computing environment we’ve been waiting for.
57+
58+OS 2 is for those eager to leave behind MEGACORP platforms and build new, intentionally architected communities. If OS 1 is car camping, OS 2 is a geodesic dome on the playa. Not exactly a permanent home, but a good start.
59+
60+While OS 2 is a big improvement, it’s still not audited to be secure. Turning that corner happens with OS 3.
61+
62+
63+
64+![](https://media.urbit.org/site/understanding-urbit/uu-roadmap-4.png)
65+
66+OS 3 — 2021
67+
68+Over the course of 2020 Urbit OS will be audited to ensure it’s completely secure. Real security, along with big improvements to our hosting infrastructure, will make OS 3 the first Urbit OS for serious work and very broad consumption.
69+
70+OS 3 makes it possible to customize a permanent, secure space for your friends, company or collaborators. With OS 3, Urbit is no longer just experimental; it’s ready for real work.
71+
72+OS 3 means you can use Urbit in earnest for everyday work. Payments, contracts, managing your entire crypto portfolio, and connecting to critical IoT devices are all possible. The range of features you can create with a truly secure personal server are really exciting to imagine.
73+
74+OS 3 means you can safely commit personal data to your Urbit with absolute peace of mind. Modules for location tracking, biometric and health data can be used without worrying about leaking bits.
75+
76+OS 3 is ready for a small law firm, or an extended family, or the crypto syndicate you’ve been thinking of starting. Or, why not, go ahead and use OS 3 to launch that digital country you’ve been meaning to start.
77+
78+Where will Urbit be in 2022 or 2023? We can’t be sure exactly. We do have our eyes set on 2030 — when Urbit should be the primary platform for people to communicate and collaborate. We think our next steps are clear and we’re on the right path.
79+
80+By this point you might be wondering, who built this thing? Where did it come from? That’s next.
content/understanding-urbit/technical-overview.mddeleted−47
@@ -1,47 +0,0 @@
1−+++
2−title = "Technical Overview"
3−description = "A quick tour of the technology"
4−weight = 6
5−[extra]
6−flatten_pagination = "true"
7−hide_next_title = "true"
8−hide_previous_title = "true"
9−+++
10−
11−
12−
13−Owning a computer, especially a server, can feel like a job. Urbit, on the other hand, is engineered to be maintenance-free. We figure that if people are actually going to use a new computing platform, it can’t feel like work. At all.
14−
15−<img class="ba mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/technical-overview/technical-overview-server.svg">
16−
17−So we built our whole stack, starting with the VM, to be as simple and compact as possible. Let’s take a look at what the system looks like from a technical perspective and get a feel for how it’s built.
18−
19−<img class="ba mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/technical-overview/technical-overview-duo.svg">
20−
21−Under the hood, Urbit is two parts: an ID system and an OS. The ID system is live and deployed to Ethereum. The OS is a program that runs on top of any Unix machine with an internet connection.
22−
23−Urbit ID is incredibly simple. An Urbit ID is just a pair of an ID and a public key. Some IDs have the ability to issue a finite number of other IDs. Galaxies, the top-tier of Urbit IDs, have the ability to upgrade the Urbit ID contracts by a majority vote. Each Urbit ID also has a cascade of keys that can perform specific actions that make securing your Urbit ID simple and straightforward. For example, the key for booting Urbit OS is separate from the key for issuing children — keep that one in a safe.
24−
25−All of this is implemented as a [suite of Solidity contracts](https://github.com/urbit/azimuth) that are [deployed to Ethereum](https://etherscan.io/address/azimuth.eth) that we call ‘Azimuth’. We’re not wedded to using Ethereum forever — but it works well for now. Someday we’d like to host Azimuth on Urbit itself.
26−
27−As a compliment to Urbit ID, we implemented the [Urbit HD wallet](https://github.com/urbit/urbit-wallet-generator) which lets most people own their Urbit IDs using a simple passkey that’s easy to remember. This means you own your Urbit ID and can log in to Urbit OS with something like ID `~ravmel-ropdyl`, passkey `~poldec-tonteg-palfun-foslup`.
28−
29−Until Urbit OS is completely secure (in the next year or so, we hope), you can interact with Urbit ID through a standalone, browser-based interface called [Bridge](https://bridge.urbit.org). Bridge lets you securely manage your keys, transfer your Urbit ID, log in to Urbit OS, and so on.
30−
31−<img class="ba mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/technical-overview/technical-overview-kernel@2x.png">
32−
33−In the simplest terms, Urbit OS is three things: a file, a key, and a program. The file is a log of everything that has ever happened to your Urbit. The key is derived from the same key you own your Urbit ID with.
34−
35−The program is mostly Arvo — our name for the Urbit OS kernel. Arvo is implemented in Hoon, a functional language that compiles down to Nock, our tiny set of opcodes.
36−
37−Arvo’s behavior is completely defined by a transition function that goes from `[event, current-state]` to `[effects, next-state]`. An event might be a keypress, an HTTP request, or a UDP message from another Arvo. An effect might be a command to the Unix terminal, an HTTP response, a UDP message to another Arvo or a move to one of Arvo’s kernel modules, or *vanes*.
38−
39−We currently have vanes for networking (`%ames`), timers (`%behn`), a filesystem (`%clay`), a terminal driver (`%dill`), an http server (`%eyre`), a functional build system (`%ford`), an application server (`%gall`) and a module for managing private keys (`%jael`).
40−
41−The operating system has a runtime called Vere that performs I/O for your OS. Think about it as the way your Urbit can interact with the outside world. It also handles your event log and runs Nock, our machine language.
42−
43−Nock is like a pico-Lisp with no symbols. It's a homoiconic purely functional machine code with 12 opcodes and one universal datatype, the noun: an acyclic binary tree that is either a number (which can also represent an arbitrarily large bytestream) or a cell, which is a pair of nouns.
44−
45−Hoon, the language in which the operating system is implemented, is a purely functional, statically typed, strictly evaluated programming language that compiles to Nock. It’s a little quirky, but at its core it’s a macro extension of Nock.
46−
47−Perhaps most interesting: our whole stack (except for Nock and Vere) is designed to be updated over the air. This is what makes it possible for Urbit to be a computer for life — it can grow with you.
content/understanding-urbit/urbit-id.md+30−37
@@ -1,7 +1,7 @@
11+++
22title = "Urbit ID"
33description = "An overview of the Urbit ID system"
4−weight = 4
4+weight = 2
55[extra]
66flatten_pagination = "true"
77hide_next_title = "true"
@@ -9,67 +9,60 @@ hide_previous_title = "true"
99image = "https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-cards%402x.png"
1010+++
1111
12−Every time you post a comment, like something, send a message, or use any app or service, you need an account. (And, behind the scenes, a network address.) Neither of these things belongs to you. The way things are going, they never will. No matter what you’re up to with your phone or laptop, you’re dependent on MEGACORP.
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
14−<img class="ba mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-megacorp.svg">
14+Urbit ID is the answer to all these questions. Urbit ID is a decentralized addressing and public key infrastructure designed for Urbit OS.
1515
16−We don’t like being owned by someone else. We think your identity and wallet should feel like a unique and precious object that you can always carry with you. So we built Urbit ID.
16+Let’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 mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-cards%402x.png">
18+<img class="ba" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-cards%402x.png">
1919
20−Urbit ID is meant 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. It’s 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.
20+Your 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
22−Your Urbit ID isn’t a physical object (yet). Instead, it’s even simpler. Your Urbit ID is a name and passkey that’s easy to memorize.
22+The Urbit ID registry is live and deployed to the Ethereum blockchain. Urbit ID isn’t specifically wedded to Ethereum – someday we’d like it to be hosted by Urbit OS itself. Also, Urbit ID is the only component of the stack using Ethereum – your Urbit OS node is hosted wherever you choose. The primary function of the Urbit ID registry is to keep track of who owns what, to specify which keys are associated with which names, and to enforce the rules of address distribution. We’ll get into the details a bit more below.
2323
24−If you wake up in the desert, unsure how you got there, you’ll be fine so long as you remember your Urbit ID and passkey. With it, you still own your digital identity and your digital assets. If you remember your friend’s Urbit ID you can always connect and send them money or messages.
24+First, let’s talk about Urbit ID’s implementation and design goals, then about where we envision it going in the future.
2525
26−Urbit ID is a simple, decentralized system for people to own their digital addresses and crypto wallets. Urbit ID is a system owned by its users, designed to last far into the future, that’s live and usable today.
26+If you’re curious to see exactly how this system works, the code is of course [open source](https://github.com/urbit/urbit). Including the source for our [phonemic naming system](https://github.com/urbit/urbit-ob/blob/master/src/internal/co.js) and the [visual representations](https://github.com/urbit/sigil-js). There’s even a [Figma plugin](https://github.com/urbit/sigil-figma-plugin) for using them. There’s also an interface for interacting with Urbit ID whose source is [open too](https://github.com/urbit/bridge).
2727
28−Urbit ID is a completely separate system from Urbit OS. It’s finished and deployed to Ethereum already. We designed Urbit ID to log in to Urbit OS, but it can be used for anything.
28+Since the Urbit ID registry is live and deployed you can even [look at the chain](https://github.com/urbit/azimuth#live-contracts).
2929
30−For those curious to understand Urbit ID a bit better, we’ll cover the basics of how Urbit ID works.
30+<img class="ba" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-paperwallet%402x.png">
3131
32−<img class="ba mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-paperwallet%402x.png">
32+Each 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
34+Urbit IDs are distributed by a sponsorship tree. At the top of the tree are 2<sup>8</sup> (256) galaxies. Each galaxy issues 2<sup>8</sup> stars, making a total of 2<sup>16</sup> (65K). Stars then each can issue 2<sup>16</sup> planets, making for 2<sup>32</sup> (~4B). As you might expect, each planet issues 2<sup>32</sup> moons.
3435
35−Your Urbit ID is a short, memorable address that anyone can use to connect with you that *doesn’t* depend on any company. It’s an address you own completely and can keep forever.
36+You can also call stars ‘infrastructure nodes’ and galaxies ‘governance nodes’, since those are more descriptive names for their roles. Stars help route packets, kind of like an ISP. And galaxies are a bit like DNS root servers or ICANN members. The difference, of course, is that Urbit IDs are owned cryptographically by many different people and accrue reputation independently.
3637
37−For most people, an Urbit ID looks something like `~tinbel-picpel`. You own it with a simple, memorable key twice its length, like `~winter-paches-palfun-foslup`. Urbit IDs are designed not to have any personally identifying information attached to them at all, sort of like a phone number. Each name and password is automatically generated — so we don’t accidentally leak data when we meet a stranger in the digital world.
38+And 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.
3839
39−Your Urbit ID and passkey are all you need to log into Urbit OS and send and receive crypto payments. Together, they’re a simple keypair that are easily memorizable. We think it’s the perfect form factor for ordinary people to take control of their digital lives.
40+<img class="full ba w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-address-space-1.svg"/>
4041
41−<img class="b—black ba mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-address-space-2.svg">
42−
43−We want everyone to own their own identity and wallet. One way to do this would be to build a MEGACORP or a Centralized Naming Authority of Urbit. But we prefer decentralized, collectively owned systems. So that’s what we built. Let’s look briefly at the basic mechanics of Urbit ID.
44−
45−Each Urbit ID is just a number. From that number we generate a pronounceable name and visually identifiable sigil. `~dalwel-fadrun` is `3,509,632,436`, for example.
46−
47−Urbit IDs are distributed by a sponsorship tree. At the top of the tree are `2^8` (`256`) galaxies. Each galaxy issues `2^8` stars, making a total of `2^16` (`65K`). Stars then each can issue `2^16` planets, making for `2^32` (`~4B`). As you might expect, each planet issues `2^32` moons.
48−
49−Every Urbit ID needs a sponsor. Stars and planets can always move to a new one. The galaxies act as a senate to upgrade the system by majority vote.
42+At a high level, there are three important things to understand about the overall Urbit ID system design.
5043
51−And 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.
44+First, scarcity: there are only 2<sup>32</sup> (~4B) Urbit IDs, so they cost something. Since they cost something, people are less likely to use them to spam or abuse the network. When you meet a stranger with an Urbit ID, you know they have some skin in the game (even without leaking personal data in either direction). That said, each Urbit ID is purely pseudonymous, so `~dalwel-fadrun` for example, is proof of some stake in the network, but not much more.
5245
53−<img class="b—black ba mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-address-space-1.svg">
46+Second, decentralization: Urbit IDs are distributed by a sponsorship tree. Each sponsor issues a fixed number of addresses. Since there are lots of sponsors, there are lots of ways to get an Urbit ID — not just one central authority. Once you get one, it’s yours forever.
5447
55−At a high level, there are three important things to understand about the overall Urbit ID system design.
48+One point that’s useful to understand about sponsors is that while Urbit IDs always need a sponsor, or parent node on the network (primarily for peer discovery), it’s always possible to change sponsors and sponsors can always reject children. This means bad actors can be banned and abusive sponsors can be ignored. We think this strikes a nice balance between accountability and freedom.
5649
57−First, there are only so many Urbit IDs, so they cost something. Since they cost something, people are less likely to use them to spam or abuse the network. And, when you meet a stranger with an Urbit ID, you know they have some skin in the game without them leaking any personal data in either direction. Each Urbit ID is purely pseudonymous. `~dalwel-fadrun`, for example, is only proof of some stake in the network.
50+Third, governance: galaxies (the top of the sponsorship tree) form a senate that can upgrade the logic of the Urbit ID system by majority vote. We think Urbit ID will last for quite a long time, but if it ever needs to be updated, the galaxies can vote to approve, reject, or propose changes to the contracts. Code may be law, but ultimately we acknowledge that human judgment can’t be factored out.
5851
59−Second, Urbit IDs are distributed by a sponsorship tree. Each sponsor issues a fixed number of addresses. Since there are lots of sponsors, there are lots of ways to get an Urbit ID — not just one central authority.
52+The Urbit ID sponsorship tree is not intended to be a social system in any way. Interactions between people and communities on the Urbit network are peer-to-peer, entirely organic and completely uncontrolled by the address hierarchy. Urbit ID is simply an authentication substrate upon which reputation and communication systems can be built. (We’ve even considered renaming stars and galaxies ‘infrastructure’ and ‘governance’ nodes, respectively).
6053
61−Urbit IDs need a sponsor even after they’re issued, but you can always change sponsors and sponsors can always reject children. This means bad actors can be banned and abusive sponsors can be ignored. We think this strikes a nice balance between accountability and freedom.
54+Your 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.
6255
63−Finally, galaxies (the top of the sponsorship tree) form a senate that can upgrade the logic of the Urbit ID system by majority vote. We think Urbit ID should last for quite a long time, but if it ever needs to be changed, the galaxies can facilitate upgrades. Code may be law, but ultimately we acknowledge that human judgment can’t be factored out.
56+<img class="ba" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-sigils%402x.png">
6457
65−(For a bit more on how all this works, see the [FAQ](@/faq.md).)
58+Urbit IDs are property, and we think of the entire registry of Urbit IDs as a vast territory of digital land.
6659
67−Urbit ID isn’t just a design. It’s [live and deployed](https://azimuth.network) to the Ethereum blockchain.
60+The scarcity of Urbit ID address space gives it value and that in turn helps bootstrap decentralization even while the project is young. Broad distribution is important – If Urbit is going to last a long time and succeed as neutral infrastructure, it has to be owned and controlled by a wide variety of people.
6861
69−<img class="b—black ba mv5 w-100" src="https://media.urbit.org/site/understanding-urbit/urbit-id/urbit-id-sigils%402x.png">
62+When 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.
7063
71−Urbit IDs are digital property, and we think of the entire address space of Urbit IDs as a vast territory of digital land.
64+<img class="ba" src="https://media.urbit.org/site/understanding-urbit/project-history/uu-id-5.jpg">
7265
73−The scarcity tree of Urbit ID address space drives decentralization even while the project is young, which is great. If Urbit ID is going to last a long time and succeed as neutral infrastructure, it has to be owned and controlled by a wide variety of people.
66+Ultimately, 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.
7467
75−When we launched the Urbit ID system, in January of 2019, there were a few thousand different star and galaxy holders – stewards of this digital land. Since then, that number is on the rise.
68+Moving on, let’s talk about what we want this whole stack to feel like as a user experience.
content/understanding-urbit/urbit-os.mdnew file+58
@@ -0,0 +1,58 @@
1++++
2+title = "Urbit OS"
3+description = "What Urbit should feel like to an everyday user"
4+weight = 1
5+[extra]
6+flatten_pagination = "true"
7+hide_next_title = "true"
8+hide_previous_title = "true"
9+image = "https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-5.jpg"
10++++
11+
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.
13+
14+<img class="ba" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-5.jpg">
15+
16+Today’s MEGACORP monopolies retain their control because of one central technical advantage: they make the server side usable.
17+
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.
19+
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.
21+
22+Today, 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.
23+
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.
25+
26+If 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.
27+
28+<img class="ba" src="https://media.urbit.org/site/understanding-urbit/technical-overview/technical-overview-kernel@2x.png">
29+
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.
31+
32+The 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.
33+
34+Nock is similar in spirit to WASM or the JVM: it’s a uniform machine code for every Urbit ship. A frozen foundation makes for some nice features:
35+
36+The state of your Urbit OS is a pure function of its event history. It’s auditable, inspectable, repeatable. You can actually trust it.
37+Writing decentralized apps becomes vasty simpler than in the old world, since every node computes exactly the same way.
38+The entire Urbit OS stack, from programming language to applications, is upgradeable over the network. For ordinary users, this makes for almost no system administration.
39+
40+Since 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+
42+<img class="full ba w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/network-os/urbit-os-diagram-apart.svg"/>
43+
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.
45+
46+This 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.
47+
48+<img class="ba" src="https://media.urbit.org/site/understanding-urbit/project-history/uu-os-4.jpg">
49+
50+But why did we build all this technology?
51+
52+First 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).)
53+
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 can happen using existing technology.
55+
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.
57+
58+Speaking of Urbit ID, let’s talk about what that actually is.
content/using/develop.md+1−1
@@ -12,7 +12,7 @@ This guide will start by getting you set up to run an Urbit ship, and then tell
1212
1313### Setting up your environment
1414
15−We assume you’ve gotten a basic introduction to Urbit. If you haven’t, read the [Understanding Urbit](@/understanding-urbit/_index.md) series, or just jump ahead to the [Technical Overview](@/understanding-urbit/technical-overview.md).
15+We assume you’ve gotten a basic introduction to Urbit. If you haven’t, read the [Understanding Urbit](@/understanding-urbit/_index.md) series.
1616
1717Once you’re ready, you can get started on the network right away and take some first steps, without acquiring an identity, by [creating a comet](@/using/operations/creating-a-comet.md).
1818
sass/_main.scss+4−3
@@ -102,6 +102,10 @@ a {
102102 text-decoration: none;
103103}
104104
105+b, strong {
106+ @extend .fw6;
107+}
108+
105109article {
106110 // default
107111 // links on body text
@@ -112,9 +116,6 @@ article {
112116 border-bottom: 0;
113117 }
114118 }
115− b, strong {
116− @extend .fw6;
117− }
118119 // post directories
119120 li {
120121 margin: 0rem 1rem 1rem 1rem;
templates/index.html+78−78
@@ -10,13 +10,13 @@
1010
1111{% block bodyclasses %}class="index"{% endblock bodyclasses %}
1212
13−{% block title %}
14− <meta name="og:title" content="{{ config.title }} - Your last computer">
15− <title>{{ config.title }} - Your last computer</title>
13+{% block title %}
14+ <meta name="og:title" content="{{ config.title }} - Your personal server">
15+ <title>{{ config.title }} - Your personal server</title>
1616{% endblock title %}
17−{% block description %}
18− <meta name="og:description" content="Urbit is your last computer. It's is a simple, durable computer that you own 100% and forever.">
19− <meta name="description" content="Urbit is your last computer. It's is a simple, durable computer that you own 100% and forever.">
17+{% block description %}
18+ <meta name="og:description" content="Urbit is a simple, durable system for running a personal server that you own 100% and forever.">
19+ <meta name="description" content="Urbit is a simple, durable system for running a personal server that you own 100% and forever.">
2020{% endblock description %}
2121{% block content %}
2222
@@ -30,9 +30,9 @@
3030 poster="https://media.urbit.org/site/sea30-poster.jpg">
3131 </video>
3232
33− <div class="grid12" style="height: 100%; width:100%;">
34− <div class="full c2-7-md c3-7-lg flex items-center align-center z10 white">
35− Urbit is your last computer.
33+ <div class="grid12 w-100 h-100">
34+ <div class="full c3-10-md c3-10-lg flex items-center align-center z10 white">
35+ Urbit is a clean-slate OS and network for the 21st century.
3636 </div>
3737 </div>
3838 <!-- VIMEO VERSION KEPT AS SHIM -->
@@ -43,29 +43,21 @@
4343
4444<!-- <nav class="full-bleed full grid12"> -->
4545
46−<section class="full c2-7-md c3-7-lg mt6">
47− <p class="lh-copy mt1 mb4">
48− Urbit is a simple, durable computer that you own 100% and forever.
46+<section class="full lh-copy c2-7-md c3-7-lg mt4">
47+ <p class="mb4">
48+ Urbit is two new pieces of technology:<br/>
49+ Urbit OS + Urbit ID.
4950 </p>
51+ <p><strong>Urbit OS</strong> is a clean slate reimaginging of the operating system as an 'overlay OS'. It runs on any Unix machine with an internet connection. Urbit OS is a compact system for an individual to run their own permanent personal server.</p>
52+ <p><strong>Urbit ID</strong> is a decentralized digital identity system. Your
53+ Urbit ID is a username, network address and crypto wallet designed for Urbit OS.</p>
54+ <p>Urbit OS + Urbit ID are designed to work together as a single system. Both are completely <a href="https://github.com/urbit/urbit">open source</a> for anyone to build on top of, play with and experiment with.</p>
55+ <p>Urbit is <i>not quite</i> ready for everyday users. But if you're curious, keep going ↓</p>
5056</section>
5157
52−<section class="full c2-7-md c3-7-lg mt6">
53− <ul class="list">
54− <li class="">
55− <a class="bb b--black" href="/understanding-urbit/">Introduction</a>
56− </li>
57− <li class="mt3">
58− <a class="blue2 bb b--blue" href="/docs">Docs</a>
59− </li>
60− <li class="mt3">
61− <a class="green2 bb b--green" href="/using/install">Install</a>
62− </li>
63− </ul>
64−</section>
65−
66−<section class="full c2-7-md c3-7-lg mt6">
58+<section class="full c2-7-md c3-7-lg mt5">
6759 <h1 class="mb3">Understanding Urbit</h1>
68− <p class="lh-copy mt1">This sequence of posts will give you a high-level overview of Urbit. They take about 12 minutes to read.</p>
60+ <p class="lh-copy mt1">This sequence of posts will give you a high-level overview of Urbit. They take about 20 minutes to read.</p>
6961 <ul class="list">
7062 <li class="mt3">
7163 <a class="b--black bb" href="/understanding-urbit/">Introduction</a>
@@ -83,13 +75,29 @@
8375 </ul>
8476</section>
8577
86−<section class="full c7-12-md c7-11-lg mt6">
87− <h1 class="mb3">Learn More</h1>
88− <p class="lh-copy mt1">We share ongoing project developments, discuss technical considerations, and update our public roadmap as often as possible. You can follow along here.</p>
78+<section class="full c2-7-md c7-11-lg mt5">
79+ <h1 class="mb3">Developer Resources</h1>
80+ <p class="lh-copy mt1">If you're someone who likes playing with experimental software, you should dive right in. Booting an Urbit takes only a few minutes.</p>
8981 <ul class="list">
9082 <li class="mt3">
91− <a class="b--black bb" href="/blog/2019-10-3-roadmap/">Roadmap</a>
83+ <a class="b--black bb" href="/using/install/">Install + Setup</a>
84+ </li>
85+ <li class="mt3">
86+ <a class="b--black bb" href="/docs/">Documentation</a>
87+ </li>
88+ <li class="mt3">
89+ <a class="b--black bb" href="/community/hoonschool">Hoon School</a>
9290 </li>
91+ <li class="mt3">
92+ <a class="b--black bb" href="https://grants.urbit.org">Developer Grants</a>
93+ </li>
94+ </ul>
95+</section>
96+
97+<section class="full c7-12-md c3-7-lg mt5">
98+ <h1 class="mb3">Learn More</h1>
99+ <p class="lh-copy mt1">We share ongoing project developments, discuss technical considerations, and update our public roadmap as often as possible.</p>
100+ <ul class="list">
93101 <li class="mt3">
94102 <a class="b--black bb" href="/blog">Blog</a>
95103 </li>
@@ -105,20 +113,50 @@
105113 </ul>
106114</section>
107115
108−<section class="full c2-7-md c3-7-lg mv6">
109− <h1 class="mb3">Follow Us</h1>
110− <p class="lh-copy mt1 mb4">Urbit is actively being built, explored, and experimented with.
111− To follow our progress you can:
112− </p>
116+<section class="full c2-7-md c7-11-lg mv5">
117+ <h1 class="mb3">Stay Up to Date</h1>
118+ <p class="lh-copy mt1 mb3">
119+ We send regular updates about our project. Enter your email to get them.
120+ </p>
121+ <iframe name="nothing" style="display:none;"></iframe>
122+ <form
123+ action="https://urbit.us11.list-manage.com/subscribe/post?u=972a03db9e0c6c25bb58de8c8&amp;amp;id=be143888d2"
124+ method="post"
125+ id="mc-embedded-subscribe-form"
126+ name="mc-embedded-subscribe-form"
127+ class="validate form"
128+ target="_blank"
129+ novalidate>
130+ <div class="input-group" id="mc_embed_signup_scroll">
131+ <div class="mc-field-group w-100 relative">
132+ <input
133+ class="bg-white black b--black ba pa3 w-100 mb2 br0 wk-appearance-none"
134+ type="email"
135+ name="EMAIL"
136+ id="mce-EMAIL"
137+ placeholder="your@email.com"/>
138+ <button
139+ id="mc-embedded-subscribe"
140+ class="dib bn absolute bg-transparent"
141+ style="font-family: 'Inter UI', san-serif; right: 3px; top: 15px; -webkit-appearance: none;"
142+ type="submit"
143+ name="subscribe"
144+ onclick="_paq.push(['trackEvent', 'Mailing List', 'Subscribe'])">
145+ <span class="fr pr1">-></span>
146+ </button>
147+ </div>
148+ </div>
149+ </form>
150+ <p>You can also:</p>
113151 <ul class="list">
114− <li class="mt2">
152+ <li class="mt3">
115153 Follow us on <a class="b--black bb" href="https://twitter.com/urbit">Twitter</a>
116154 </li>
117− <li class="mt2">
155+ <li class="mt3">
118156 Explore the code on
119157 <a class="b--black bb" href="https://github.com/urbit/urbit">GitHub</a>
120158 </li>
121− <li class="mt2">
159+ <li class="mt3">
122160 Ask questions in our <a class="b--black bb" href="https://discord.gg/Mae2bk7">Discord</a>
123161 </li>
124162 </ul>
@@ -127,44 +165,6 @@
127165 </p>
128166</section>
129167
130−<section
131− class="full c7-12-md c7-11-lg mb6 mt6-xl mt6-l mt6-m"
132− id="newsletter-subscribe-top">
133− <h1 class="mb3">Stay Up to Date</h1>
134− <p class="lh-copy mt1 mb3">
135− We send regular updates about our project. Enter your email to get them.
136− </p>
137− <iframe name="nothing" style="display:none;"></iframe>
138− <form
139− action="https://urbit.us11.list-manage.com/subscribe/post?u=972a03db9e0c6c25bb58de8c8&amp;amp;id=be143888d2"
140− method="post"
141− id="mc-embedded-subscribe-form"
142− name="mc-embedded-subscribe-form"
143− class="validate form"
144− target="_blank"
145− novalidate>
146− <div class="input-group" id="mc_embed_signup_scroll">
147− <div class="mc-field-group w-100 relative">
148− <input
149− class="bg-white black b--black ba pa3 w-100 mb2 br0 wk-appearance-none"
150− type="email"
151− name="EMAIL"
152− id="mce-EMAIL"
153− placeholder="your@email.com"/>
154− <button
155− id="mc-embedded-subscribe"
156− class="dib bn absolute bg-transparent"
157− style="font-family: 'Inter UI', san-serif; right: 3px; top: 15px; -webkit-appearance: none;"
158− type="submit"
159− name="subscribe"
160− onclick="_paq.push(['trackEvent', 'Mailing List', 'Subscribe'])">
161− <span class="fr pr1">-></span>
162− </button>
163− </div>
164− </div>
165− </form>
166−</section>
167−
168168 <!-- </nav> -->
169169<!-- </article> -->
170170{% include "partials/footer.html" %}
templates/partials/pagination.html+1−1
@@ -29,7 +29,7 @@
2929 </a>
3030 {% endif %}
3131
32− {% if page.relative_path == "understanding-urbit/simple-durable-yours.md" %}
32+ {% if page.relative_path == "understanding-urbit/urbit-os.md" %}
3333 <a class="bb-0" href="/understanding-urbit/">
3434 <nav class="next absolute left-1 t-left mb4">
3535 <p {% if page.extra.flatten_pagination %}
templates/understanding-urbit/list.html+71−77
@@ -32,91 +32,85 @@
3232
3333</nav>
3434<!-- content -->
35−<h1 id="introduction" class="mb4 full mt4 c4-10-lg">Introduction</h1>
36−<section class="full-bleed full grid12">
37− <img class="full c4-10-lg mb4" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-0.jpg"/>
38− <p class="full c4-10-lg mt0 mb4 mb4-xl lh-copy">
39− Imagine that you can login from anywhere with one name and password.
40− </p>
41− <p class="full c4-10-lg mt0 mb4 mb4-xl lh-copy">
42− And when you do, your entire OS appears.
43− </p>
44− <p class="full c4-10-lg mt0 mb4 mb4-xl lh-copy">
45− Inside is your whole digital life. All of your communities, conversations, and connections. All of your biometric data and devices. Your entire personal archive in one place that’s secure, private, and designed to last forever.
46− </p>
47− <p class="full c4-10-lg mt0 mb4 mb4-xl lh-copy">
48− You own and control this OS completely. It’s yours. No one else can look at it without your permission, it can never show you ads.
49− </p>
50− <p class="full c4-10-lg mt0 mb4 mb4-xl lh-copy">
51− This is what Urbit is. Your Urbit is a simple, durable computer that belongs to you 100% and forever.
52− </p>
53− <p class="full c4-10-lg mt0 mb4 mb4-xl lh-copy">
54− Urbit is not vaporware. It's real and it works. Two separate companies and a community of contributors are working together to build the Urbit future.
55− </p>
56− <p class="full c4-10-lg mt0 mb4 mb4-xl lh-copy">
57− But Urbit isn't ready for everyone yet. Today, it's a version <code>0</code>. Brave explorers should find a way in. In 2020, we plan to open Urbit for more people.
58− </p>
59− <p class="full c4-10-lg mt0 mb8 mb7-xl lh-copy">
60− Let’s walk through what Urbit is, what it’s for and where we’re going step by step.
61− </p>
35+<section class="full c4-10-lg">
36+ <h1 id="introduction" class="mb4 full mt4 ">Introduction</h1>
37+ <p class="full mt0 mb4 mb4-xl lh-copy">We think the internet can’t be saved. The way things are going, MEGACORP will always control our apps and services because we can no longer run them ourselves.</p>
38+ <p class="full mt0 mb4 mb4-xl lh-copy">The only way out of this mess is with a completely new platform that’s owned and controlled by its users.</p>
39+ <img class="full ba mb4" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-0.jpg"/>
40+ <p class="full mt0 mb4 mb4-xl lh-copy">Urbit is a new OS and peer-to-peer network that’s simple by design, built to last forever, and 100% owned by its users. Under the hood, Urbit is a clean-slate software stack compact enough that an individual developer can understand and control it completely.</p>
41+ <p class="full mt0 mb4 mb4-xl lh-copy">We built this new stack to give people a single integrated tool for communicating and building communities – a tool they can trust, control, and extend to their liking. We want to do away with the terrible user experience of the current ‘frankenstack’ of apps and services that we all use today. </p>
42+ <p class="full mt0 mb4 mb4-xl lh-copy">Urbit is designed to become an effective, customizable productivity tool for collaborators, and a calm noninvasive communication tool for friends and families.</p>
43+ <p class="full mt0 mb4 mb4-xl lh-copy">This probably sounds crazy, so let’s get concrete and talk about (1) Urbit as a piece of technology and (2) Urbit as a user experience.</p>
44+ <p class="full mt0 mb4 mb4-xl lh-copy b">1 - Technology</p>
45+ <p class="full mt0 mb4 mb4-xl lh-copy">Technically, Urbit is two components: Urbit OS and Urbit ID.</p>
46+ <p class="full mt0 mb4 mb4-xl lh-copy">Both are completely <a class="bb" href="https://github.com/urbit/urbit">open</a> <a class="bb" href="https://github.com/urbit/azimiuth">source</a> and MIT licensed.</p>
47+ <img class="full w-100 mb4" src="https://media.urbit.org/site/understanding-urbit/uu-intro-2.svg"/>
48+ <p class="full mt0 mb4 mb4-xl lh-copy">Urbit OS is a new, carefully architected software stack: a VM, programming language and kernel designed to run software for an individual. </p>
49+ <p class="full mt0 mb4 mb4-xl lh-copy">Urbit OS is a program that runs on almost any cloud server, most laptops and many phones: anything with Unix and an internet connection. Urbit OS is completely sealed from the system it runs on, sort of like WASM or the JVM. We sometimes call it an ‘overlay OS’.</p>
50+ <p class="full mt0 mb4 mb4-xl lh-copy">In an Urbit world, each person has their own Urbit OS node, or ‘urbit’. Your urbit is secure and private to you and entirely under your control. When you want to connect with others, you connect to their urbit directly — rather than going through a centralized service. </p>
51+ <p class="full mt0 mb4 mb4-xl lh-copy">If you’re curious to dive even deeper into Urbit OS, feel free to <a class="bb" href="/understanding-urbit/urbit-os">skip ahead</a>.</p>
52+ <img class="full w-100 mb4" src="https://media.urbit.org/site/understanding-urbit/uu-intro-3.svg"/>
53+ <p class="full mt0 mb4 mb4-xl lh-copy">Urbit ID is an identity and authentication system specifically designed to work with Urbit OS. When you boot or log in to Urbit OS, you use your Urbit ID. </p>
54+ <p class="full mt0 mb4 mb4-xl lh-copy">Your Urbit ID is a short, memorable name (like <code>~ravmel-ropdyl</code>) that’s a username, network address and crypto wallet all in one. It’s registered on a blockchain, you own it with a key and no one can take it away from you. Urbit IDs are cryptographic property. </p>
55+ <p class="full mt0 mb4 mb4-xl lh-copy">Urbit IDs aren’t money, but they are scarce, so each one costs something. This means that when you meet a stranger on the Urbit network, they have some skin in the game and are less likely to be a bot or a spammer.</p>
56+ <p class="full mt0 mb4 mb4-xl lh-copy">The Urbit ID system is live and deployed, and we don’t plan to change it all that much. It works well. If you’re curious to dive further into the details, jump ahead to <a class="bb" href="/understanding-urbit/urbit-id">this post.</a></p>
57+ <p class="full mt0 mb4 mb4-xl lh-copy b">2 - User experience</p>
58+ <p class="full mt0 mb4 mb4-xl lh-copy">We want Urbit to be a single, simple interface for your whole digital life.</p>
59+ <img class="full ba mb4" src="https://media.urbit.org/site/understanding-urbit/uu-intro-4.png"/>
60+ <p class="full mt0 mb4 mb4-xl lh-copy">Over the years, Urbit has been built in public as an open source project. Anyone can <a class="bb" href="/using/install/">join the network</a> and check out what we’re up to. It’s a bit like signing on to IRC in the early 90s. </p>
61+ <p class="full mt0 mb4 mb4-xl lh-copy">In early 2020, we’ll release Urbit OS 1: a minimal interface for group communication, and our first complete interface. OS 1 is a tool to chat, share notes and links, and stay connected. </p>
62+ <p class="full mt0 mb4 mb4-xl lh-copy">OS 1 is the first step toward a truly complete OS for a networked world. </p>
63+ <p class="full mt0 mb4 mb4-xl lh-copy">Over time, Urbit will grow into a system that can bring together all our different modes of communicating: chat, payments, documents, images, biometric data. We want individuals and their communities to be able to both control their software in fact, through the source code, and in action, through a simple interface.</p>
64+ <p class="full mt0 mb4 mb4-xl lh-copy">We want to leave behind a world of apps and services for one where we can bring everything together in one place. And, in doing so, ordinary users can create customized digital environments for their friends and communities.</p>
65+ <img class="full ba mb4" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-6.jpg"/>
66+ <p class="full mt0 mb4 mb4-xl lh-copy">To see how we’re going to get there, let’s walk through these two pieces of new technology individually, Urbit OS and Urbit ID. We’ll then talk about our vision for the future and how we’ll get there.</p>
67+ <p class="full mt0 mb4 mb4-xl lh-copy">For technical people, it’s important to note that Urbit as a stack is in no way required to be used together. Don’t like our client? Feel free to build your own. Just like the Urbit ID system? No problem — use it!
68+ <p class="full mt0 mb4 mb4-xl lh-copy">Ultimately, we think that new technology is most likely to get adopted if it can provide a much, much better user experience. So that’s what we’re focussing on creating.</p>
6269</section>
63−<section class="full-bleed full grid12 mt7">
64− <p class="full c4-7-lg mt0 mb4 mb2-xl lh-copy">
65− This is a drawing of an Urbit&nbsp;—&nbsp; a new kind of computer. <br /><br />
66− Your Urbit isn’t a physical device: it lives in the cloud or your laptop.
67− </p>
68− <img class="full c7-10-lg row-1 mt0 mb2 mb4-xl w-100 ba" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-1.svg" alt="A drawing of an Urbit ship." />
69−</section>
70−<section class="full-bleed full grid12">
71− <p class="full c4-7-lg mt0 mb4 mb2-xl lh-copy">
72− Your Urbit is a tool for you to run your own social software to connect and communicate with your friends and family. <br /><br />
73− Urbit is the opposite of MEGACORP social media.
74− </p>
75− <img class="full c7-10-lg row-1 mt0 mb2 mb4-xl w-100 ba" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-2.svg" alt="An Urbit ship receiving data." />
76−</section>
77−<section class="full-bleed full grid12">
78− <p class="full c4-7-lg mt0 mb4 mb2-xl lh-copy">
79− Your Urbit is a permanent, private archive.<br /><br />
80− Your Urbit can store all your data and digital assets safely, privately, forever.
81− </p>
82− <img class="full c7-10-lg row-1 mt0 mb2 mb4-xl w-100 ba" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-3.svg" alt="An Urbit ship with its previous versions in a lifetime archive" />
83−</section>
84−<section class="full-bleed full grid12">
85− <p class="full c4-7-lg mt0 mb6 mb2-xl lh-copy">
86− You own your Urbit like you own Bitcoin.<br /><br />
87− Each Urbit is a piece of a new network that’s owned and controlled by its users.
88− </p>
89− <img class="full c7-10-lg row-1 mt0 mb2 mb7-xl w-100 ba" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-4.svg" alt="An Urbit ship communicating with other ships" />
90−</section>
91−<section id="megacorp" class="full full-bleed grid12 bg-black">
92− <img class="full c4-10-lg mt7" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-5.jpg"/>
93− <p class="full c4-10-lg white lh-copy mt2 mt4-xl mb7">
94− Today, technology controls us. Every MEGACORP has the same incentive: To keep us hooked on their platform.
95− </p>
96−</section>
97−<section class="full full-bleed grid12 bg-yellow">
98− <img class="full c4-10-lg mt7" src="https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/intro/intro-6.jpg"/>
99− <p class="full c4-10-lg lh-copy mt2 mt4-xl">
100− We built Urbit so people can control their technology, shape their digital lives and freely build their digital communities.
101− </p>
102− <p class="full c4-10-lg lh-copy mt2">
103− We want to replace the Internet with a foundation for computing that we can all rely on far into the future.
104− </p>
105− <p class="full c4-10-lg lh-copy mt2">
106− Urbit is a large, ambitious project. But at the core it’s simple, durable and yours.
107− </p>
108−</section>
109−<p class="c1-10 c4-10-lg mt6 mb4 lh-copy">
110− Nothing quite like this has ever been done before.
111−</p>
70+
11271<footer class="relative mt4 c4-10-lg full">
11372 {% set posts = get_section(path="understanding-urbit/_index.md") %}
11473 {% for directorypage in posts.pages | slice (end=1) %}
115− <a class="bb-0" href="{{directorypage.permalink}}">
74+ <a href="{{directorypage.permalink}}">
11675 <nav class="previous absolute right-2 t-right">
11776 <p data-flat="true" class="mt5 mb6">{{directorypage.title}}</p>
11877 </nav>
11978 </a>
12079 {% endfor %}
12180</footer>
81+
82+<section class="c4-10-lg mv6">
83+ <iframe name="nothing" style="display:none;"></iframe>
84+ <p class="mt5">If you’d like to follow our progress, we send monthly updates via email:</p>
85+ <form
86+ action="https://urbit.us11.list-manage.com/subscribe/post?u=972a03db9e0c6c25bb58de8c8&amp;amp;id=be143888d2"
87+ method="post"
88+ id="mc-embedded-subscribe-form"
89+ name="mc-embedded-subscribe-form"
90+ class="validate form"
91+ target="_blank"
92+ novalidate>
93+ <div class="input-group" id="mc_embed_signup_scroll">
94+ <div class="mc-field-group w-100 relative">
95+ <input
96+ class="bg-white black b--black ba pa3 w-100 mb2 br0 wk-appearance-none"
97+ type="email"
98+ name="EMAIL"
99+ id="mce-EMAIL"
100+ placeholder="your@email.com"/>
101+ <button
102+ id="mc-embedded-subscribe"
103+ class="dib bn absolute bg-transparent"
104+ style="font-family: 'Inter UI', san-serif; right: 3px; top: 15px; -webkit-appearance: none;"
105+ type="submit"
106+ name="subscribe"
107+ onclick="_paq.push(['trackEvent', 'Mailing List', 'Subscribe'])">
108+ <span class="fr pr1">-></span>
109+ </button>
110+ </div>
111+ </div>
112+ </form>
113+ <p class="full mt3 mb3 mb3-xl lh-copy">You can also follow us on <a class="bb" href="https://twitter.com/urbit">Twitter</a> or <a class="bb" href="https://github.com/urbit">Github</a>.</p>
114+ <p class="full mt0 mb3 mb4-xl lh-copy">Or, preferably, on Urbit itself in <code>~dopzod/urbit-help</code></p>
115+</section>
122116{% endblock content %}
templates/understanding-urbit/post.html+35−1
@@ -53,7 +53,7 @@
5353 {% endfor %}
5454</nav>
5555
56− <article class="mb4 full c4-12-lg measure-wide">
56+ <article class="full c4-10-lg">
5757 <h1 class="mb4 mt4">{{ page.title }}</h1>
5858 {% if page.extra.author %}
5959 <span class="dib" rel="author"> {{ page.extra.author }}
@@ -73,4 +73,38 @@
7373
7474 {% include "partials/pagination.html" %}
7575 </article>
76+ <section class="c4-10-lg mv6">
77+ <iframe name="nothing" style="display:none;"></iframe>
78+ <p class="mt5">If you’d like to follow our progress, we send monthly updates via email:</p>
79+ <form
80+ action="https://urbit.us11.list-manage.com/subscribe/post?u=972a03db9e0c6c25bb58de8c8&amp;amp;id=be143888d2"
81+ method="post"
82+ id="mc-embedded-subscribe-form"
83+ name="mc-embedded-subscribe-form"
84+ class="validate form"
85+ target="_blank"
86+ novalidate>
87+ <div class="input-group" id="mc_embed_signup_scroll">
88+ <div class="mc-field-group w-100 relative">
89+ <input
90+ class="bg-white black b--black ba pa3 w-100 mb2 br0 wk-appearance-none"
91+ type="email"
92+ name="EMAIL"
93+ id="mce-EMAIL"
94+ placeholder="your@email.com"/>
95+ <button
96+ id="mc-embedded-subscribe"
97+ class="dib bn absolute bg-transparent"
98+ style="font-family: 'Inter UI', san-serif; right: 3px; top: 15px; -webkit-appearance: none;"
99+ type="submit"
100+ name="subscribe"
101+ onclick="_paq.push(['trackEvent', 'Mailing List', 'Subscribe'])">
102+ <span class="fr pr1">-></span>
103+ </button>
104+ </div>
105+ </div>
106+ </form>
107+ <p class="full mt3 mb3 mb3-xl lh-copy">You can also follow us on <a class="bb" href="https://twitter.com/urbit">Twitter</a> or <a class="bb" href="https://github.com/urbit">Github</a>.</p>
108+ <p class="full mt0 mb3 mb4-xl lh-copy">Or, preferably, on Urbit itself in <code>~dopzod/urbit-help</code></p>
109+ </section>
76110{% endblock content %}