dffd855 · urbit.org · git.iko.soy

git.iko.soy/urbit.org

content: remove s

commitdffd85577c67fbfb02bc1e63606e8940394f0c97 authorMatilde Park <matilde.park@urbit.org> dateWed 1 Jun 2022, 17:35 (4 years ago) parentec1da52

36 files changed+5−161

compare with master

unifiedsplit

content/blog/2020-to-2021.md−4

@@ -9,12 +9,8 @@ ship = "~wolref-podlex"

99image = "https://media.urbit.org/site/posts/essays/arch-sunrise-2.jpeg"

1010+++

1111

12−

13−

1412![arch](https://media.urbit.org/site/posts/essays/arch-sunrise-2.jpeg)

1513

16−

17−

1814In this post, which has been adapted from our most recent [newsletter](https://urbit.us11.list-manage.com/subscribe/post?u=972a03db9e0c6c25bb58de8c8&id=be143888d2), we'll take a moment to reflect on the events of the last year, and then turn our attention to the next one.

1915

2016## 2020

content/blog/20200929-state-of-urbit.md−4

@@ -9,12 +9,8 @@ ship = "~ravmel-ropdyl"

99image = "https://storage.googleapis.com/media.urbit.org/site/posts/essays/state-of-urbit-1.jpg"

1010+++

1111

12−

13−

1412![Grassy Knoll](https://storage.googleapis.com/media.urbit.org/site/posts/essays/state-of-urbit-1.jpg)

1513

16−

17−

1814When we announced OS 1, in April, we started to disappear into Urbit. Since then, we’ve been living on Urbit like we never have before. This has been our goal for years: to mature the system we’re building by becoming its first committed users. We knew that critical step toward Urbit’s maturity was being able to depend on it ourselves, but the system itself had to mature to the point that we could do that practically.

1915

2016We’ve done this in fits and starts. We’ve _tried_ and failed a few times over the years. We’ve always _used_ Urbit to some extent, but we’ve never _relied_ on it. These past six months have been different. I can’t tell whether it was out of sheer determination and commitment, or that the system was just genuinely ‘there’. Either way, both Tlon and the Urbit Community genuinely live on Urbit now.

content/blog/20201119-models-of-society.md−12

@@ -17,12 +17,8 @@ All people like to talk. Society is built by talking. In this—the year of

1717

1818## Modes of Messaging

1919

20−

21−

2220![Ludovic Maclellan Mann examining the Cochno Stone](https://media.urbit.org/site/posts/essays/cochno-stone.png)

2321

24−

25−

2622In general, technology serves humanity as a kind of appendage—instead of thinking new thoughts or acting on its own, it does what we command. Technology never creates new social structures—it merely makes existing ones easier, or it facilitates the creation of new ones. We use our tools to expand our capacities, and once we are capable of doing more, we can imagine new things to do. Inventing the wheel did not invent motorized transportation—but it did facilitate it and it was a necessary step, even an inspirational one. Similarly, the invention of writing made new forms of human interaction and new tools for organization possible.

2723

2824Consider the following conversational conventions, or modes of messaging: a letter; a dialogue; a book; a meeting; minutes of that meeting. These are each pieces of technology: finely constrained solutions to human problems. Now, we have digital forms of each of these which diverge variously from the original. A letter becomes an email. A dialogue becomes a chat room, or a series of blog posts, or a twitter spat. A book becomes a website or an ebook. Meetings in 2020 have virtually been replaced by their virtual counterparts. Minutes become recordings or transcripts.

@@ -44,12 +40,8 @@ Having an indistinct sense of place makes the form of conversation ambiguous and

4440

4541## People in Places

4642

47−

48−

4943![Halle Saale Marktplatz](https://media.urbit.org/site/posts/essays/halle-saale-marktplatz.jpg)

5044

51−

52−

5345As the internet grew to accommodate new conversation forms using the basic substrate of hypertext, web developers began to conceive of "digital spaces" through analogy—chat "rooms" and "forums,” or the "silo" and the "walled garden." Today, most of our conversation takes place in these walled gardens—privately-owned places which may be beautiful on the inside, but inaccessible from elsewhere. While some of these walled gardens are very large, our conversation is essentially confined to them. There is no roaming from one space to another while keeping one’s identity. We create new identities for new spaces both because we must and because we are afraid of repercussions on one platform for what we say on another. This is because we do not own our identity; we merely have a key—our password. The owners of the walled garden still own the artifacts of our tenure there, and can revoke our access to them at any time.

5446

5547The concept of identity and the concept of place are fundamentally linked. We imagine the prince who travels overseas where no one knows his name, or we imagine the old prospect of traveling to a new world to make a fortune. While those both exemplify a dramatic change in identity and place, we usually want to keep our identity consistent. We want to be recognized by friends whichever place we go, and we all strive toward having a good reputation, which is a consistent identity across places. This consistent identity also allows control of that reputation per place. A man is not judged in public by the words he says among friends. And there is no way to search what someone has said except by asking him. With our current system of identity providers (an absurd term, but a real one), we surrender our rights to selectively expose our thoughts, regardless of the place they have been uttered. A data breach or a weak password might lay bare our most private thoughts. We run the real risk of being confronted by an old conversation presented out of context or after we have learned better.

@@ -60,12 +52,8 @@ In theory, we would have a digital city with unique regions, public fora, and so

6052

6153## Urbis ec Bit

6254

63−

64−

6555![View of Florence from San Miniato](https://media.urbit.org/site/posts/essays/view-of-florence.jpg)

6656

67−

68−

6957Urbit does solve this underlying problem. At this point the explanation goes so far down the stack that you could spend years tracing it all, but the relevant part is this: Urbit is not an empire; it’s a territory. An empire is an entangling of land and rule: within the bounds of said empire, you agree to be bound by its laws and the penalties for transgression. The laws exist at the whim of a despot or cabal. Your standing as a Roman citizen buys you no favors in Persia. In contrast, a territory imposes only physical laws. For example, in the desert, you will die faster. The only way to change that is to alter the desert. Urbit imposes nothing but the digital equivalent of physical laws. You have an identity which can be said to be truly yours, and you have a piece of software that runs on whatever computer you choose and can do anything you want with the messages sent to your identity. There are no social protocols enforced, because no one can control what software you run on your computer. As long as you agree to communicate using the same basic substrate, you can communicate with anyone using Urbit. This is the digital equivalent of speaking the same language. Whether or not others will accept you into their coalitions is not the technology's concern.

7058

7159In the same way that the land provides clay and timber, Urbit also provides the tools and material for building places both public and private. These include the aforementioned consistent message substrate (content), as well as tools for organizing people/audiences, structure for referencing other content, and an identity system that is owned only by you while being verified by all. The places are being built—private rooms with just a few people, meeting halls, club houses, huge public spaces, and countless personal encounters, the contents of which are known to none but the participants.

content/blog/aesthetic-culture-1.md−4

@@ -10,12 +10,8 @@ ship = "~nartes-fasrum"

1010image = "https://media.urbit.org/site/posts/essays/help-the-environment.jpg"

1111+++

1212

13−

14−

1513![A set of four sigils arranged & coloured to appear as various natural forms, above the ~sorwet sigil & the text "help the environment and help yourself"](https://media.urbit.org/site/posts/essays/help-the-environment.jpg)

1614

17−

18−

1915_This post is the first in a series of digests centered on art produced within and about Urbit by a member of the community, ~nartes-fasrum. Monthly digests will be available within the Urbit Community group in Landscape, and will occasionally be compiled here on the blog to give you a sneak peek at some of what’s happening on the network. Enjoy! ~wolref-podlex_

2016

2117One of the most exciting things about Urbit is the aesthetic and design around it, developed partly by Tlon (through the design of Urbit itself) and partly by the community (by producing great Urbit art). As the community grows, it creates more art, and we have the opportunity to showcase some of the pieces we love. These works can draw curious new users in, and they give existing users ways to communicate their excitement to friends.

content/blog/after-machine-war.md−6

@@ -9,12 +9,8 @@ ship = "~bacbec-lormur"

99image = "https://storage.googleapis.com/media.urbit.org/site/posts/essays/berlin-wall.jpeg"

1010+++

1111

12−

13−

1412![berlin-wall](https://storage.googleapis.com/media.urbit.org/site/posts/essays/berlin-wall.jpeg)

1513

16−

17−

1814> The following fictional passage, from a book being written in an Urbit Group called “the Aleph,” sketches out a dismal future for the human race. As an item of speculative fiction, the piece is not what one might call original. Anyone could have come up with these ideas. In fact, several already have. The Matrix is an obvious antecedent. Vonnegut isn’t far behind either. And the treacly humanism lodged beneath the bitter humor resembles nothing so much as the work of that beau monde satirist, George Saunders.

1915>

2016> Really the only notable thing about it is that it was written on Urbit. And that, perhaps, has made all the difference.

@@ -25,8 +21,6 @@ image = "https://storage.googleapis.com/media.urbit.org/site/posts/essays/berlin

2521>

2622> Then as now, the unexpected is more likely to occur than most would believe. One thing is not only possible, but an established fact: A brand new digital infrastructure is slowly, quietly being built. While U.S. political parties haggle over $1,400 disbursements for citizens, the rules of global finance are being re-written in code. While pundits debate the merits of Dr. Seuss’s lesser known titles, a global shift away from traditional publishing is gaining steam. And while users and social apps themselves pop up and down like whack-a-mole, folks are putting down roots with permanent peer-to-peer digital identities. If you’re anything like an optimist, you’ll probably want to get on Urbit ASAP and put down your own.

2723

28−

29−

3024The date is January 1, 2050. The place, New York City. The vibe...subdued. Back in 2020, you made a note to yourself to take stock of the world around you here at the half-century mark. And now the time has come. What do you find? The air quality is a bit worse, the bad parts of town are a bit more dilapidated, the Knicks are still terrible—all in all, from the outside at least, not much has changed from 30 years ago. Today you wake up groggy on your self-adjusting Smart Bed (Smart Bed Never Sleeps), you make yourself a steaming pot of coffee (locally sourced, delivered within the half-hour by a drone, now that you’ve got Titicaca Prime), you shower and get ready for work.

3125

3226But what was that dream you had last night? Only the faintest traces of it remain. A luminous rainbow, a mountain landscape, a sense of profound inner peace, mixed with euphoria, mixed with...an intense desire to go out and buy some Health Morsels cereal?

content/blog/eliza.md−4

@@ -9,12 +9,8 @@ ship = "~pindet-timmut"

99image = "https://media.urbit.org/site/posts/essays/valleys.jpg"

1010+++

1111

12−

13−

1412![valleys](https://media.urbit.org/site/posts/essays/valleys.jpg)

1513

16−

17−

1814## The Storm before the Calm

1915

2016Building things, even Calm™ things, makes noise. George Nakashima’s wooden furniture evokes peace, but its construction still begins with a chainsaw. We mention this because we’re firing up our newest power tool.

content/blog/events-series.md−4

@@ -10,12 +10,8 @@ ship = "~naplet-hildec"

1010image = "https://media.urbit.org/site/posts/essays/bau.jpg"

1111+++

1212

13−

14−

1513![people gathered](https://media.urbit.org/site/posts/essays/bau.jpg)

1614

17−

18−

1915_TL;DR: Urbit is launching a series of community events, the first of which is a developer call taking place on Thursday, November 5 at 9am PT. [Sign up here](https://www.meetup.com/urbit-sf/events/274279522/), and read on for all of the details._

2016

2117--

content/blog/first-contract.md−4

@@ -9,12 +9,8 @@ ship = "~datnut-pollen and ~palfun-foslup"

99image = "https://media.urbit.org/site/posts/essays/land3.jpg"

1010+++

1111

12−

13−

1412![milestone](https://media.urbit.org/site/posts/essays/land3.jpg)

1513

16−

17−

1814Recently, the [first upgrade](https://github.com/urbit/azimuth/pull/35) to the

1915[Azimuth](/docs/glossary/azimuth) smart contracts which make up Urbit ID was

2016put up to an [upgrade proposal vote](/docs/glossary/upgrade) by the

content/blog/first-steps-towards-urbit-org.md−2

@@ -9,8 +9,6 @@ ship = "~wolref-podlex"

99image = "https://media.urbit.org/site/posts/essays/first-steps.png"

1010+++

1111

12−

13−

1412![](https://media.urbit.org/site/posts/essays/first-steps.png)

1513

1614## Summary

content/blog/ford-fusion.md−4

@@ -9,12 +9,8 @@ ship = "~rovnys-ricfer"

99image = "https://media.urbit.org/site/posts/essays/ford-fusion.png"

1010+++

1111

12−

13−

1412![](https://media.urbit.org/site/posts/essays/ford-fusion.png)

1513

16−

17−

1814## Overview and Rationale

1915

2016Ford Fusion was an overhaul of Urbit's over-the-air upgrade process and a rewrite of its build system. The new update system corrects a few long-standing bugs with the previous one, and the new build system is simpler, smaller (by around 5,000 lines), and easier to manage.

content/blog/gifts-q3-2020.md−4

@@ -13,12 +13,8 @@ ship = "~wolref-podlex"

1313image = "https://media.urbit.org/site/posts/essays/gifts.png"

1414+++

1515

16−

17−

1816![](https://media.urbit.org/site/posts/essays/gifts.png)

1917

20−

21−

2218Twice a year we distribute address space to those that have made valuable contributions to Urbit. Now called our _Gifts_ program, the gifting of address space has been part of Urbit long before we had a grants program.

2319

2420I'm happy to announce that urbit.org has a record number of gifts to distribute to community contributors for the period from February to August of 2020. Because the gifting of address space is an old tradition, and the last several months have seen an unprecedented amount of user growth, let’s talk about why we do this.

content/blog/hackathon-results.md−4

@@ -9,12 +9,8 @@ ship = "~lodleb-ritrul"

99image = "https://media.urbit.org/site/posts/essays/hackathon-results-wide.png"

1010+++

1111

12−

13−

1412![](https://media.urbit.org/site/posts/essays/hackathon-results.png)

1513

16−

17−

1814Results of the Urbit Hackathon

1915

2016We recently held an invite-only Urbit Hackathon for graduates of our Hoon School program, and the submissions really impressed us across the board. Submissions were judged on several criteria: creativity, usefulness, and code quality.

content/blog/hosting-the-future.md−4

@@ -9,12 +9,8 @@ ship = "~simfur-ritwed"

99image = "https://storage.googleapis.com/media.urbit.org/site/posts/essays/200930-hosting-by-tlon.jpg"

1010+++

1111

12−

13−

1412![Ocean](https://storage.googleapis.com/media.urbit.org/site/posts/essays/200930-hosting-by-tlon.jpg)

1513

16−

17−

1814Urbit users tend to be interesting, creative, and capable people; we’re genuinely impressed with the communities that have formed on the network, and with the quality of discourse there. But for the number of communities to continue to grow, getting on the network has to become dramatically easier. It’s not realistic to expect most people to configure their own Urbit OS node in the command line.

1915

2016At the moment, the biggest lever we have here is to help ordinary users get online, so they can participate in communities inside Urbit, and eventually form their own. This means hosting their Urbit nodes and showing them around the network when they first arrive. There are already several businesses overlapping with this space to varying degrees: [planet.market](https://planet.market/), [urth.systems](https://urth.systems/), and [geturbitid](https://www.geturbitid.com/). Now, Tlon is releasing its own hosting offering. For the uninitiated, “Hosting” just means that we run your urbit ship for you, making it easier for you to get onto the network. We’ve been testing our hosting service with friends and family for the past few months, and now we’re ready to bring it to the rest of the world.

content/blog/infrastructural.md−6

@@ -9,8 +9,6 @@ ship = "~fabled-faster"

99image = "https://media.urbit.org/site/posts/essays/infrastructural-2.jpg"

1010+++

1111

12−

13−

1412![](https://media.urbit.org/site/posts/essays/infrastructural-1.jpg)

1513

1614## Seasons

@@ -53,10 +51,6 @@ We deeply hope that Urbit can form a support structure for you and your communit

5351

5452These self-evident statements underlie the core problems we sought to address in designing a userspace for OS 1: How do we design an _actually_ personal digital infrastructure? What does infrastructure look like when shared with immediate friends? With a cooperative organization? How can we impress upon Urbit's earliest adopters that once they've obtained an Urbit ID, their computer is at that moment _literally_ entirely theirs?

5553

56−

57−

58−

59−

6054![](https://media.urbit.org/site/posts/essays/infrastructural-2.jpg)

6155

6256## Expressing Infrastructure

content/blog/interplanetary_commerce.md−4

@@ -9,12 +9,8 @@ ship = "~pindet-timmut"

99image = "https://media.urbit.org/site/posts/essays/ocean.jpeg"

1010+++

1111

12−

13−

1412![ocean](https://media.urbit.org/site/posts/essays/ocean.jpeg)

1513

16−

17−

1814## Paying

1915

2016A year ago, we started [integrating](https://urbit.org/blog/urbit-and-bitcoin/) Bitcoin into Urbit to be an OS-level primitive for money. Our initial objective: build a payments wallet, equally sovereign and ergonomic. The first public version, releasing this month, will have a broad set of capabilities including ship-to-ship payments, hardware wallet support, and full node integration. We’ll be unveiling this wallet on [April 27th](https://www.meetup.com/urbit-sf/events/276741426/). Do join us.

content/blog/introducing-os1.md−2

@@ -9,8 +9,6 @@ ship = "~ravmel-ropdyl"

99image = "https://media.urbit.org/site/posts/essays/intro-os1-landscape.png"

1010+++

1111

12−

13−

1412<video class="ba w-100" autoplay loop src="https://media.urbit.org/site/posts/essays/intro-os1.mov"></video>

1513

1614## Introducing OS 1

content/blog/io-in-hoon.md−4

@@ -9,12 +9,8 @@ ship = "~wicdev-wisryt"

99image = "https://media.urbit.org/site/posts/essays/zion-canyon-1.jpg"

1010+++

1111

12−

13−

1412![canyon](https://media.urbit.org/site/posts/essays/zion-canyon-1.jpg)

1513

16−

17−

1814Let's talk about IO in Urbit. I won't say much about how events and effects are processed by the runtime; it suffices to note that the runtime is a normal Unix program which (1) listens for various events, (2) passes them to Arvo (Urbit OS), and (3) processes the effects produced by Arvo. Instead, I’ll focus on how IO works from the perspective of Hoon programs, like Arvo or apps running on Arvo. But first, let's review IO paradigms in other languages.

1915

2016All examples are in a made-up language, since it's useful to understand this information even before you're comfortable in Hoon. If you're learning Hoon and want a challenge, try translating them!

content/blog/iot.md−4

@@ -9,12 +9,8 @@ ship = "~datnut-pollen"

99image = "https://media.urbit.org/site/posts/essays/phobos.jpeg"

1010+++

1111

12−

13−

1412![phobos](https://media.urbit.org/site/posts/essays/phobos.jpeg)

1513

16−

17−

1814Each of the ~4B 32-or-fewer-bit or [Azimuth](/docs/glossary/azimuth)

1915identities, namely [planets](/docs/glossary/planet),

2016[stars](/docs/glossary/star), and [galaxies](/docs/glossary/galaxy), may

content/blog/layer-2-faq.md+2−2

@@ -92,12 +92,12 @@ Bridge.

9292

9393There are a number of ways to host a planet in the cloud. Your options:

9494

95−- DIY:

95+- DIY:

9696 The most cost-effective method is [setting it up

9797 yourself](https://urbit.org/using/running/hosting), though this route requires

9898 some system administration, and troubleshooting if any issues arise.

9999

100−- Via a Hosting Provider:

100+- Via a Hosting Provider:

101101 The more “headache-free” option is paying for a

102102 hosting provider to take care of all these processes for you, plus support. The

103103 following service providers offer hosting (some include a free planet):

content/blog/metaphase.md−4

@@ -9,12 +9,8 @@ ship = "~haddef-sigwen"

99image = "https://media.urbit.org/site/posts/essays/metaphase.jpg"

1010+++

1111

12−

13−

1412![mitosis](https://media.urbit.org/site/posts/essays/metaphase.jpg)

1513

16−

17−

1814_Previous versions of this essay specified the stream deploy date as December 11, 2020; then December 18, 2020. This has been amended to the actual date of release, with our sincere apologies. For new readers, you can opt into the dev stream by running:_

1915

2016```

content/blog/platform-decay.md−2

@@ -9,8 +9,6 @@ ship = "~simfur-ritwed"

99image = "https://media.urbit.org/site/posts/essays/platform-decay-preview.png"

1010+++

1111

12−

13−

1412![](https://media.urbit.org/site/posts/essays/platform-decay.png)

1513

1614## Platform decay, decentralized marketplaces, and Urbit

content/blog/precepts-discussion.md−14

@@ -9,8 +9,6 @@ ship = "~wicdev-wisryt"

99image = "https://media.urbit.org/site/posts/essays/discuss-01.jpg"

1010+++

1111

12−

13−

1412![](https://media.urbit.org/site/posts/essays/discuss-01.jpg)

1513

1614The precepts aren’t arguments. We will discuss and justify them here. We don't expect to convince you this is exactly the right set of precepts, but we hope to convince you that this is a coherent set of precepts that might lead to something very interesting.

@@ -36,8 +34,6 @@ We will address these in the same categories presented above:

3634- F: Real Software. Not all software matters. Any software which

3735 wouldn't exist on Mars isn't real.

3836

39−

40−

4137![](https://media.urbit.org/site/posts/essays/discuss-02.jpg)

4238

4339### A: General Design

@@ -355,8 +351,6 @@ An example of the second is "security through obscurity is ineffective". Securit

355351

356352However, it's important for whoever's coming up with the cliches to understand the specifics of how they're untruthful. Some of these very precepts may fall under the category of "literally untrue but more useful than the truth".

357353

358−

359−

360354![](https://media.urbit.org/site/posts/essays/discuss-03.jpg)

361355

362356## B: Specific Design

@@ -415,8 +409,6 @@ Memory access restrictions are blunt tools. Blunt tools are nice in simple syste

415409

416410Better to define rules in a more powerful language. This allows you to follow A6 and A8. It also lets you use all the correctness tools, like type systems, that you've developed for the rest of your code.

417411

418−

419−

420412![](https://media.urbit.org/site/posts/essays/discuss-04.jpg)

421413

422414### C: Attitude

@@ -468,8 +460,6 @@ of your own mind.

468460This is also one of the best ways to build stuff correctly. Very often, you will be tempted to cut a corner, and someone will point out that it should be done correctly. You should consider why you immediately rejected it. Was it because you were afraid of the relevant piece of code? If so, you should learn more about that code to determine if it's actually a good idea. Did you reject it because you felt it would distract you from working on what you thought was more important?

469461Consider carefully whether this particular piece of technical debt is worth taking on. It's worth 60 seconds of thinking about how you could solve it correctly right now — often it would be quite easy to do correctly and you'd be paying interest on the incorrectness for a long time.

470462

471−

472−

473463![](https://media.urbit.org/site/posts/essays/discuss-05.jpg)

474464

475465### D: Theory

@@ -513,8 +503,6 @@ However, that explanatory power is indeed powerful, and the exploratory suggesti

513503

514504![](https://media.urbit.org/site/posts/essays/discuss-06.jpg)

515505

516−

517−

518506### E: Text Style

519507

520508Code form matters. Code that is hard to read is hard to maintain. Code that is inconsistently formatted is hard to read, but consistency isn't the end of the story. Some formats are simply hard to read.

@@ -615,8 +603,6 @@ We're really good at memorizing sets of things, like runes. We're also good at i

615603

616604So don't be afraid to use new names for new concepts. If concepts are siblings, they needn't necessarily have a direct connection in their name, but if they're hierarchical, then something should suggest that. This can be syntactic or semantic.

617605

618−

619−

620606![](https://media.urbit.org/site/posts/essays/discuss-07.jpg)

621607

622608### F: Real Software

content/blog/precepts.md−14

@@ -9,8 +9,6 @@ ship = "~wicdev-wisryt"

99image = "https://media.urbit.org/site/posts/essays/pre-01.jpg"

1010+++

1111

12−

13−

1412![](https://media.urbit.org/site/posts/essays/pre-01.jpg)

1513

1614Urbit is a principled approach to system design and programming, but it's often not obvious what those principles are. We have many specific terms for the different parts of the project: Arvo is the OS, Hoon is the language, Tlon is the company, Azimuth is the identity system, Ames is the network. But the word most associated with the project is "Urbit", and it's not clear what technically it refers to. It's only a small stretch to say that "Urbit" _is_ this set of principles, and that if anybody follows these principles strictly they will create a system that is isomorphic to the Urbit.

@@ -19,8 +17,6 @@ Some of these are commonly held among many software projects, and some are not.

1917

2018We’ll start with a brief description of many principles, then we’ll go into a long-form justification.

2119

22−

23−

2420![](https://media.urbit.org/site/posts/essays/pre-02.jpg)

2521

2622### A: General Design

@@ -138,8 +134,6 @@ We’ll start with a brief description of many principles, then we’ll go into

13813423. Some cliches are repeated because they are true; others must be

139135 repeated because they are not.

140136

141−

142−

143137![](https://media.urbit.org/site/posts/essays/pre-03.jpg)

144138

145139### B: Specific Design

@@ -170,8 +164,6 @@ We’ll start with a brief description of many principles, then we’ll go into

170164 A compiler can use type safety as an effective tool to enforce

171165 some classes of security guarantees.

172166

173−

174−

175167![](https://media.urbit.org/site/posts/essays/pre-04.jpg)

176168

177169### C: Attitude

@@ -203,8 +195,6 @@ We’ll start with a brief description of many principles, then we’ll go into

203195 responding take a full 60 seconds to envision how you would implement

204196 it and what the effects would be.

205197

206−

207−

208198![](https://media.urbit.org/site/posts/essays/pre-05.jpg)

209199

210200### D: Theory

@@ -250,8 +240,6 @@ We’ll start with a brief description of many principles, then we’ll go into

250240 use theory to fix the bad, add the missing, and remove the

251241 unnecessary. Repeat.

252242

253−

254−

255243![](https://media.urbit.org/site/posts/essays/pre-06.jpg)

256244

257245### E: Text Style

@@ -285,8 +273,6 @@ We’ll start with a brief description of many principles, then we’ll go into

285273

2862748. Abbreviations aren't worth it.

287275

288−

289−

290276![](https://media.urbit.org/site/posts/essays/pre-07.jpg)

291277

292278### F: Real Software

content/blog/providers.md−4

@@ -9,12 +9,8 @@ ship = "~ravmel-ropdyl"

99image = "https://storage.googleapis.com/media.urbit.org/site/posts/essays/providers.png"

1010+++

1111

12−

13−

1412![](https://storage.googleapis.com/media.urbit.org/site/posts/essays/providers.png)

1513

16−

17−

1814We look forward to a future where your Urbit is an always-on, always-available service. You should be able to pick up any device and conjure up your whole digital life immediately.

1915

2016Sounds good—but how does this actually come to pass? Urbit has to be technically robust and have a nice interface. Assuming we can deliver both of those things, your Urbit node also has to be safe, secure, and running somewhere with a network connection.

content/blog/security-audit.md−4

@@ -9,12 +9,8 @@ ship = "~rovnys-ricfer + ~poldec-tonteg"

99image = "https://storage.googleapis.com/media.urbit.org/site/posts/essays/20201218-audit.png"

1010+++

1111

12−

13−

1412![audit](https://storage.googleapis.com/media.urbit.org/site/posts/essays/20201218-audit.png)

1513

16−

17−

1814The security firm Leviathan has now finished their initial audit of the security of Urbit's Ames network protocol. In addition to their review of Ames, we also asked them to identify any other issues in order to help guide further development.

1915

2016I'm pleased to report they confirmed the cryptographic soundness of the protocol, namely that "a ship must have possession of their own valid Urbit key in order to authenticate as that ship and to send valid Ames messages. Additionally, no other ship except the two communicating may be able to decrypt or modify messages during transport."

content/blog/the-missing-middle.md−4

@@ -9,12 +9,8 @@ ship = "~simfur-ritwed"

99image = "https://media.urbit.org/site/posts/essays/missing-middle.png"

1010+++

1111

12−

13−

1412![](https://media.urbit.org/site/posts/essays/missing-middle.png)

1513

16−

17−

1814The promise of social technology is that we can discover more friends; _specifically, people more similar to us_ than we previously had access to. The means by which we do so, the methods of collaboration, the quality of connected experiences; these factors matter, but they are marginal considerations compared to the basic offering of an expanded choice of connections.

1915

2016The wilder-eyed, utopian end of early computing drew greatly from this promise; such unprecedented connection could bring about world peace, intellectual serendipity, higher consciousness. We didn’t get world peace, but we did get a genuine revolution in collaborative information-sharing and rapid communication. That ability to refactor our social preferences gave birth to an uncountable universe of online communities and subcultures that would be unimaginable to anyone who didn’t see it happen.

content/blog/the-understanding-urbit-podcast.md−2

@@ -9,8 +9,6 @@ ship = "~satsyt-sogleb"

99image = "https://media.urbit.org/site/posts/essays/uu-podcast.png"

1010+++

1111

12−

13−

1412![](https://media.urbit.org/site/posts/essays/uu-podcast.png)

1513

1614At the end of January, the team at Tlon invited me to spend some time at their San Francisco office and to create a podcast series about Urbit. The idea was to produce an interview-based series about the project told in the words of those working on it. In this modest goal, I think we were very successful. Beyond a transactional description, however, we captured a range of perspectives of the flaws in our current computing landscape and visions for how Urbit will alter it.

content/blog/tools-of-our-own.md−8

@@ -9,12 +9,8 @@ ship = "~haddef-sigwen"

99image = "https://media.urbit.org/site/posts/essays/tools-of-our-own-1.png"

1010+++

1111

12−

13−

1412![](https://media.urbit.org/site/posts/essays/tools-of-our-own-1.png)

1513

16−

17−

1814> People need only not to obtain things, they need above all the freedom to make things among which they can live, or give shape to them according to their own tastes, and to put them to use in caring for and about others.

1915>

2016> <cite>Ivan Illich, Tools for Conviviality</cite>

@@ -27,8 +23,6 @@ The [Rube Goldberg machine](https://en.wikipedia.org/wiki/Rube_Goldberg_machine)

2723

2824And it's nobody's distinct fault that the experience of aligning all these disparate services into a workflow is a skill in itself. It's a collective restriction that comes from the systems beneath.

2925

30−

31−

3226![](https://media.urbit.org/site/posts/essays/tools-of-our-own-2.png)

3327

3428### Systems as masters

@@ -53,8 +47,6 @@ And for productivity tools—for the personal activities we do every day—the s

5347

5448This is why hybrid products are born _and_ why massive enterprises are shifting toward subscription models for office software. With the [clearnet](<https://en.wikipedia.org/wiki/Clearnet_(networking)>), using our own computers for everyday tasks that extend outside themselves is not easy. It's way easier to sign into an enterprise's server farm for your persistent data storage and manipulation. In 2020, the prefab parts for the exoskeleton only come in "left arm, right leg" pairs, or you can just give up and plug straight into SkyNet.

5549

56−

57−

5850![](https://media.urbit.org/site/posts/essays/tools-of-our-own-3.png)

5951

6052### The collective body

content/blog/urbit-for-normies.md+1−1

@@ -121,7 +121,7 @@ I’ll try to explain the most important of these without straying too deep into

121121

122122 What all this adds up to is that the Urbit network is immensely more resource efficient, secure, easier to customize, and smaller in size than any other computing system in the world. If you care about data security, privacy, durability, or even just elegance, Urbit has the best design going.

123123

124−

124+

125125

126126![](https://media.urbit.org/site/posts/essays/normies-2.png)

127127

content/blog/urbit-is-for-communities.md−2

@@ -9,8 +9,6 @@ ship = "~ravmel-ropdyl"

99image = "https://media.urbit.org/site/posts/essays/urbit-is-for-communities.jpg"

1010+++

1111

12−

13−

1412![](https://media.urbit.org/site/posts/essays/urbit-is-for-communities.jpg)

1513

1614## Generated, not fabricated

content/blog/value-of-address-space-pt3.md−2

@@ -9,8 +9,6 @@ ship = "~patnes-rigtyn + ~ravmel-ropdyl"

99image = "https://media.urbit.org/site/posts/essays/value-of-address-space-pt3.jpg"

1010+++

1111

12−

13−

1412![](https://media.urbit.org/site/posts/essays/value-of-address-space-pt3.jpg)

1513

1614_This is the third in a series of three posts on Urbit address space. See also [part 1](https://urbit.org/blog/value-of-address-space-pt1/) and [part 2](https://urbit.org/blog/value-of-address-space-pt2/)._

content/docs/development/precepts.md−4

@@ -4,8 +4,6 @@ weight = 40

44template = "doc.html"

55+++

7−

8−

97![](https://media.urbit.org/site/posts/essays/pre-01.jpg)

108

119Urbit is a principled approach to system design and programming, but it's often not obvious what those principles are. We have many specific terms for the different parts of the project: Arvo is the OS, Hoon is the language, Tlon is the company, Azimuth is the identity system, Ames is the network. But the word most associated with the project is "Urbit", and it's not clear what technically it refers to. It's only a small stretch to say that "Urbit" _is_ this set of principles, and that if anybody follows these principles strictly they will create a system that is isomorphic to the Urbit.

@@ -129,8 +127,6 @@ We’ll start with a brief description of many principles, then we’ll go into

12912723. Some cliches are repeated because they are true; others must be

130128 repeated because they are not.

131129

132−

133−

134130![](https://media.urbit.org/site/posts/essays/pre-03.jpg)

135131

136132### B: Specific Design {% #specific %}

content/getting-started/installing-applications.md+1−1

@@ -37,5 +37,5 @@ After selecting the “picture” app, a pane will open that shows some informat

3737Soon you’ll have a new application tile on your home screen that will let you upload and display a picture to your home screen.

3838

3939![](https://media.urbit.org/site/additional-guides/Installing-apps-3.jpg)

40−

40+

4141![](https://media.urbit.org/site/additional-guides/Installing-apps-4.jpg)

content/groups/~ladtem-filmyr/urbit-ny-week.md+1−1

@@ -202,7 +202,7 @@ Contact: [`~marrys-sapbyt`](https://urbit.org/ids/~marrys-sapbyt) / rsvp@noagenc

202202

203203</div>

204204</div>

205−

205+

206206<H2>EXTRA</H2>

207207

208208<div class="box">

content/understanding-urbit/roadmap.md−10

@@ -24,16 +24,12 @@ Bringing together many different things in one place is something only a general

2424

2525As Urbit matures, other killer digital environments may emerge—but Landscape is the app we need if we want to move away from the world of MEGACORP software and onto a secure, distraction-free network of our own.

2626

27−

28−

2927![A Landscape](https://storage.googleapis.com/media.urbit.org/tlon/landscape.png)

3028

3129Today, we pour all of our focus into making Landscape a comfortable place for digital communities to call home, starting with our own. This effort forces us to mature the entire stack, from the interpreter to the interface.

3230

3331Let’s walk through the next few phases of Landscape to get a sense of where we are and where we’re headed.

3432

35−

36−

3733![The current state of Landscape/OS1](https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/uu-interface-3.png)

3834

3935### Today: Landscape OS 1.N

@@ -48,8 +44,6 @@ Our initial goal was just to get ourselves living on Urbit everyday. We achieved

4844

4945OS 1 was a huge step forward. Let’s talk about what’s next.

5046

51−

52−

5347![A speculative interface for Landscape S2](https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/uu-interface-4.png)

5448

5549## Late 2020: Landscape S2

@@ -68,8 +62,6 @@ We know that getting onto the network can be difficult for less technical users.

6862

6963We’re planning to share the hosted version of S2 with a few small communities to test it out and put it through the paces. If you’re curious, [let us know](https://tlon.io).

7064

71−

72−

7365![A speculative payments interface](https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/uu-roadmap-4.jpg)

7466

7567## Early 2021: Landscape S3

@@ -82,8 +74,6 @@ Perhaps most importantly, Landscape 3 will be backed by a fully audited networki

8274

8375Landscape inherits the benefits of Urbit itself: simplicity, durability, and a real sense of ownership. These come out of the box, from the beginning, but supporting a fully-featured interface makes a lot of demands of a new stack. By Landscape 3 our interface and infrastructure will have matured to the point that it can be confidently held up against alternatives.

8476

85−

86−

8777![A landscape](https://storage.googleapis.com/media.urbit.org/site/understanding-urbit/uu-roadmap-5.jpg)

8878

8979## 2021 and beyond

content/updates/2020-07-27-update.md−2

@@ -28,8 +28,6 @@ We’re also working on delivering a new, keyboard-oriented, searchable navigati

2828

2929We’re also beginning to plan our next slate of work: we are preparing to make the leap to the OS2 codebase, and it involves quite a bit of research, but it’ll arrive sooner than you think…

3030

31−

32−

3331Reminder: Hoon School begins August 1

3432

3533[Hooniversity](https://hooniversity.org/) is the new home of Hoon School run by `~rabsef-bicrym` and `~risruc-habteb`. To enroll, visit hooniversity.org or email join@hooniversity.org