on master help sign in
re-organised directories
b86f828Matilde Park
learn/arvo/_index.md → arvo/_index.mdrenamed

The content is the same.

learn/arvo/ames.md → arvo/ames.mdrenamed

The content is the same.

reference/arvo-glossary.md → arvo/arvo-glossary.mdrenamed

The content is the same.

learn/arvo/behn.md → arvo/behn.mdrenamed

The content is the same.

learn/arvo/clay.md → arvo/clay.mdrenamed

The content is the same.

learn/arvo/dill.md → arvo/dill.mdrenamed

The content is the same.

learn/arvo/eyre.md → arvo/eyre.mdrenamed

The content is the same.

learn/arvo/ford.md → arvo/ford.mdrenamed

The content is the same.

learn/arvo/gall.md → arvo/gall.mdrenamed

The content is the same.

learn/arvo/hall.md → arvo/hall.mdrenamed

The content is the same.

using/sail-and-udon.md → arvo/sail-and-udon.mdrenamed

The content is the same.

using/ship-troubleshooting.md → arvo/ship-troubleshooting.mdrenamed

The content is the same.

azimuth/_index.mdnew file+5
@@ -0,0 +1,5 @@
1++++
2+title = "Azimuth"
3+weight = 1
4+template = "doc.html"
5++++
reference/azimuth-glossary.md → azimuth/azimuth-glossary.mdrenamed+1−1
@@ -1,6 +1,6 @@
1+++
1+++
2title = "Azimuth Glossary"
2title = "Azimuth Glossary"
3−weight = 4
3+weight = 3
4template = "doc.html"
4template = "doc.html"
5+++
5+++
6
6
learn/azimuth.md → azimuth/azimuth.mdrenamed

The content is the same.

concepts/_index.mddeleted−13
@@ -1,13 +0,0 @@
1−+++
2−title = "Concepts"
3−weight = 3
4−sort_by = "weight"
5−template = "sections/docs/chapters.html"
6−+++
7−The documents in this section are high-level introductions to the Urbit project and components thereof.
8−
9−
10−* [Technical Overview](technical-overview): An in-the-weeds explanation of the components of the Urbit stack.
11−* [Azimuth](azimuth): An overview of Azimuth, the Urbit identity layer.
12−* [Galaxies, Stars, and Planets](galaxies-stars-and-planets): A guide to the Urbit network hierarchy.
13−* [Community Tutorials](community-tutorials): A collection of community guides for various pieces of the project.
concepts/azimuth.mddeleted−93
@@ -1,93 +0,0 @@
1−+++
2−title = "Azimuth"
3−weight = 4
4−template = "doc.html"
5−description = "An explanation of the Urbit identity layer."
6−+++
7−Azimuth is a general-purpose public-key infrastructure (PKI) on the Ethereum blockchain, used as a platform for Urbit identities that we call _points_. You need a point to use the Arvo network.
8−
9−The primary way to interact with Azimuth is through our [Bridge](https://github.com/urbit/bridge) application and the node libraries that it depends on, [azimuth-js](https://github.com/urbit/azimuth-js) and [urbit-key-generation](https://github.com/urbit/urbit-key-generation). Take a look at the source and play around, or see [Getting Started](/docs/getting-started).
10−
11−## Arvo vs. Azimuth
12−
13−Urbit is a project, not a single computer system. It has multiple components: Arvo, the operating system; and Azimuth, the identity system. Let's compare them.
14−
15−**Arvo** is an operating system that provides the software for a personal server. These personal servers together constitute the peer-to-peer Arvo network. To make this network work on the social level, Arvo is built to work with a system of scarce and immutable identities.
16−
17−**Azimuth** is the public-key infrastructure built to be such a system. A suite of smart-contracts on the Ethereum blockchain, Azimuth determines which Ethereum addresses own which Azimuth identities, called _points_. All point-related operations, such as transfers, are governed at this layer. But Azimuth isn't built strictly for Arvo -- it could be used as a generalized identity system for other projects.
18−
19−These otherwise-parallel systems meet when you want to connect to the Arvo network. Your Arvo personal server, called your _ship_, needs to be able to prove cryptographically that it is who it says it is. This proof comes in the form of a keyfile, derived from your point, that you use to start your ship.
20−
21−A metaphor might help illustrate the relationship between these two systems: the Arvo network is the neighborhood that you live in; Azimuth is the bank vault that stores the deed to your house.
22−
23−## Why Urbit Uses a Blockchain
24−
25−The Arvo network is composed of personal servers: instances of the Arvo operating system, called ships, that communicate as peers.
26−
27−Every ship has an associated secure identity, called a point, that it needs to connect to the network. Your point is your name and your network address. Each point has associated authentication and encryption keys for networking. Think of a point as an IP address, a domain name, and a PGP key-pair.
28−
29−There are a limited number of points and, as you might expect, scarcity gives points value. This means that bad actors – spammers, scammers, and malware-spreaders – can be made economically unviable. Points being immutable allows for reputation systems to be built on top, keeping the network friendly and giving users information to help them decide who to treat as a trusted peer.
30−
31−At the user level, having one identity for your digital life means that all the services that you trust recognize you. You no longer need to worry about managing dozens of different logins. When you're using Arvo, everything you do is "verified" in the sense that it links back to your point.
32−
33−But wait! We need some way to secure these identities. To that end, we have built the Azimuth identity layer on the Ethereum blockchain to determine which PKI. As mentioned above, it's separate from and parallel to the Arvo network.
34−
35−In theory, our ecosystem doesn't need a blockchain, because Urbit identities are more like real estate than currency: they change hands slowly. A low-friction, zero-trust solution to the double-spend problem isn't an economic necessity for transactions such as ours. So we could have the Arvo network run its own key-signing system. But, since Azimuth identities are valuable, you don't want to put them in an self-hosted PKI that isn't generally recognized as secure. Arvo is still young, we'd prefer to use an existing system for people to secure their property.
36−
37−Moving the Urbit land registry to Ethereum is an easy and obvious solution to this problem. We chose Ethereum over Bitcoin because the former is built for computation and the latter is not. We need a computational blockchain to enforce the specific rules of the Urbit identity registry.
38−
39−For more background on the decision to use the Ethereum blockchain, check out [these](https://urbit.org/posts/essays/urbit-and-the-blockchain/) [two](https://urbit.org/posts/essays/bootstrapping-urbit-from-ethereum/) posts.
40−
41−## The Urbit HD Wallet
42−
43−Owners of Azimuth points need safeguards that allow for the use of Urbit without jeopardizing cryptographic ownership of their assets. Toward this end, we created the **Urbit Hierarchical Deterministic (HD) Wallet** for the storage of points. The Urbit HD Wallet is not one key-pair, but a system of related key-pairs that each have distinct powers, from setting networking keys for communicating in the Arvo network to transferring ownership of points.
44−
45−The Urbit HD Wallet's derivation paths have a hierarchical structure, so that keys with different powers can be physically separated. A \"master ticket" can re-derive the entire wallet in case of loss. The encryption and authentication keys that points ships use to sign messages within the network are also derived from the wallet.
46−
47−Urbit HD wallets are composed of the following items, which are each assigned to their own individual Ethereum key-pairs.
48−
49−### Master Ticket
50−
51−Think of your master ticket like a very high-value password. The master ticket is the secret code from which all of your other keys are derived. Technically, your master ticket is seed entropy. You should never share it with anyone, and store it very securely. This ticket can derive all of your other keys: your ownership key and all of the related proxies.
52−
53−### Ownership Address
54−
55−An ownership address has all rights over the assets deeded to it. These rights are on-chain actions described and implemented in the Ecliptic, Azimuth's suite of governing smart-contracts.
56−
57−### Proxies
58−
59−Proxy addresses allow you to execute non-ownership related actions like spawning child points, voting, and setting networking keys without jeopardizing the keys you've designated with ownership rights. Setting proxy rights is optional, but it is recommended for on-chain actions you will execute more frequently.
60−
61−- **Management Proxy**
62−
63− Can configure or set Arvo networking keys and conduct sponsorship related
64− operations.
65−
66−- **Voting Proxy**
67−
68− Galaxies only. Galaxies are the part of the galactic senate, and this means
69− they can cast votes on new proposals including changes to the Ecliptic.
70−
71−- **Spawn Proxy**
72−
73− For stars and galaxies only. Can create new child points.
74−
75−![](https://media.urbit.org/fora/proposals/UP-8.jpg)
76−
77−
78−Most Ethereum tokens use the ERC-20 standard for smart contracts. Azimuth points
79−are, however, essentially different from most Ethereum tokens, due to points not
80−being fungible. Since any two stars will handle social-networking realities in a
81−different way, they will carry a different reputation. Points are to houses as
82−tokens are to gold.
83−
84−The ERC-721 standard, having been made specifically to provide a smart-contract
85−interface for non-fungible assets, serves our needs well. This is the standard
86−that we use for deeding Azimuth points.
87−
88−Points, and all of their blockchain operations, are governed by the Ecliptic.
89−The Ecliptic is an Ethereum smart-contract that governs point state and the
90−ownership, spawn, management, and voting rights affiliated with your points.
91−
92−For the technical implementation details, take a look at Azimuth's
93−[Github repository](https://github.com/urbit/azimuth).
concepts/community-tutorials.mddeleted−15
@@ -1,15 +0,0 @@
1−+++
2−title = "Community Tutorials"
3−weight = 9
4−template = "doc.html"
5−description = "A collection of unofficial but useful Urbit learning resources."
6−+++
7−Here are some tutorials written by members of the Urbit community. Some are a little outdated, but they may still prove useful.
8−
9−- [Generators](https://github.com/joemfb/mardev/tree/master/docs/gen) by `~master-morzod`
10−- [Urbit by Doing](https://github.com/Fang-/Urbit-By-Doing) by `~palfun-foslup`
11−- [Learning Hoon](https://github.com/knubie/learning-hoon) by `@knubie`
12−- [A Nock Interpreter](https://jtobin.io/nock) by `~nidsut-tomdun`
13−- [Basic Hoonery](https://jtobin.io/basic-hoonery) by `~nidsut-tomdun`
14−
15−If you want to add something to the list, [shoot us an email](mailto:support@urbit.org) or make a pull request in the [docs repository](https://github.com/urbit/docs).
concepts/galaxies-stars-and-planets.mddeleted−34
@@ -1,34 +0,0 @@
1−+++
2−title = "Galaxies, Stars, and Planets"
3−weight = 7
4−template = "doc.html"
5−description = "An explanation of the Urbit address-space hierarchy. "
6−+++
7−
8−The current internet has no consistent system of identity. There are only quasi-identities such as IP addresses, Google accounts and email addresses, each able to be assumed and abandoned without much trouble. The result is a hostile social experience, since bad actors -- spammers, scammers, malware-spreaders, and harassers -- have an inexhaustible supply of places to hide.
9−
10−That's why we built a system for persistent identity called [Azimuth](@/docs/concepts/azimuth.md). Azimuth identities are called _points_, and you need one to use the Arvo network. Points are secure, since they are owned and controlled with key-pair the Ethereum blockchain, which Azimuth is built on top of.
11−
12−An Azimuth point is a pronounceable string like `~firbyr-napbes`. It means nothing, but it's easy to remember and say out loud. `~firbyr-napbes` is actually just a 32-bit number (`3.237.967.392`, to be exact) that we turn into a human-memorable string.
13−
14−Points come in three classes: **galaxies**, **stars**, and **planets**. You can tell what class a point is in by how long its name is. The address space grows like a family tree. Galaxies are 8-bit and have names like `~mul`. Galaxies can issue 16-bit stars (`~dacpyl`), which can themselves issue 32-bit planets (`~laptel-holfur`).
15−
16−Planets are intended for everyday use by an adult human, and there is a maximum of about 4.3 billion of them (2 to the 32nd power). Stars and galaxies, on the other hand, are meant to act as network infrastructure: in the Arvo network they provide P2P routing and distribute software updates.
17−
18−```
19− Size Name Parent Object Example
20− ----- ------ ------ ------ -------
21− 2^8 galaxy ~ supernode ~zod
22− 2^16 star galaxy supernode ~dozbud
23− 2^32 planet star user ~tasfyn-partyv
24− 2^64 moon planet device ~sigsam-nimbot-tasfyn-partyv
25− 2^128 comet ~ bot ~racmus-mollen-fallyt-linpex--watres-sibbur-modlux-rinmex
26−```
27−
28−## Moons and Comets
29−
30−In addition to these three classes of Azimuth points, there two other kinds of Urbit identities, but they do _not_ use Azimuth.
31−
32−**Moons** are 64 bits, are issued by planets, and have names like `~doznec-salfun-naptul-habrys`. Moons are meant for connected devices: phones, smart TVs, digital thermostats. Moons are not independent, but are subordinated to their parent planet. To create new moon under your planet, follow [this guide](/docs/using/admin#moons).
33−
34−**Comets** are 128-bit points with no parents that can be launched by anyone. They are meant for bots. Being disposable and essentially unlimited, they will likely not be trusted by the others on the Arvo network. They have enormous names, like `~racmus-mollen-fallyt-linpex--watres-sibbur-modlux-rinmex`.
concepts/technical-overview.mddeleted−170
@@ -1,170 +0,0 @@
1−+++
2−title = "Technical overview"
3−weight = 1
4−template = "doc.html"
5−description = "A more in-depth description of the entire Urbit stack."
6−+++
7−Urbit is a clean-slate software stack designed to implement an encrypted P2P
8−network of general-purpose personal servers. Each server on this network is a
9−deterministic computer called an 'urbit' that runs on a Unix-based virtual
10−machine.
11−
12−The current Urbit stack includes (among other things):
13−
14−- Arvo: the functional operating system of each urbit, written in Hoon.
15−- Azimuth: the Urbit identity layer, built on the Ethereum blockchain.
16−- Hoon: a strictly typed functional programming language whose standard library
17− includes a Hoon-to-Nock compiler.
18−- Nock: a low-level combinator language whose formal specification fits readably on a t-shirt.
19−- Vere: a Nock interpreter and Unix-based virtual machine that mediates between
20− each urbit and the Unix software layer.
21−
22−## Anatomy of a personal server
23−
24−Your urbit is a deterministic computer in the sense that its state is a pure
25−function of its event history. Every event in this history is a
26−[transaction](https://en.wikipedia.org/wiki/Transaction_processing); your
27−urbit's state is effectively an [ACID database](https://en.wikipedia.org/wiki/ACID).
28−
29−Because each urbit is deterministic we can describe its role appropriately in
30−purely functional terms: it maps an input event and the old urbit state to a
31−list of output actions and the subsequent state. This is the Urbit transition
32−function.
33−
34−```
35−<input event, old state> -> <output actions, new state>
36−```
37−
38−For example, one input event could be a keystroke from the terminal, say
39−`[enter]` after having already typed `(add 2 2)`; and an output action could be
40−to print in the terminal window the resulting value of a computation performed
41−when the user hit `[enter]`, in this case `4`. The input event is stored in the
42−urbit's event history.
43−
44−Events always start from outside of your urbit, whether they're local to the
45−computer running the urbit (e.g., a keystroke in the terminal) or they originate
46−elsewhere (e.g., a packet received from another urbit). When an event is
47−processed, various parts of the urbit state can be modified before the resulting
48−list of output actions is returned.
49−
50−Can output actions from your urbit cause side-effects in the outside world?
51−The answer had better be "yes," because a personal server without side effects
52−isn't useful for much. In another sense the answer had better be "no," or else
53−there is a risk of losing functional purity; your urbit cannot _guarantee_ that
54−the side effects in question actually occur. What's the solution?
55−
56−Each urbit is
57−[sandboxed](https://en.wikipedia.org/wiki/Sandbox_%28computer_security%29) in a
58−virtual machine, Vere, which runs on Unix. Code running in your urbit cannot
59−make Unix system calls or otherwise directly affect the underlying platform.
60−Strictly speaking, internal urbit code can only change internal urbit state; it
61−has no way of sending events outside of its runtime environment. Functional
62−purity is preserved.
63−
64−In practical terms, however, you don't want your urbit to be an impotent
65−[brain in a vat](https://en.wikipedia.org/wiki/Brain_in_a_vat). That's why
66−Vere also serves as the intermediary between your urbit and Unix. Vere observes
67−the list of output events, and when external action is called for makes the
68−appropriate system calls itself. When external events relevant to your urbit
69−occur in the Unix layer, Vere encodes and delivers them as input events.
70−
71−### Arvo
72−
73−Arvo is a purely functional, [non-preemptive](https://en.wikipedia.org/wiki/Cooperative_multitasking)
74−OS, written in Hoon, that serves as the event manager of your urbit.
75−It can upgrade itself from over the network without downtime. The Arvo kernel
76−proper is quite simple -- it's only about 600 lines of code, excluding its
77−various modules.
78−
79−The Urbit transition function is implemented in Arvo. Upon being 'poked' by
80−Vere with the pair of `<input event, state>`, Arvo directs the event to the
81−appropriate OS module. The result of each Vere 'poke' is a pair of
82−`<output events, new state>`. Events are typed, and each has an explicit
83−call-stack structure indicating the event's source module in Arvo.
84−
85−Arvo modules are also called 'vanes'. Arvo's vanes are:
86−
87−- Ames: defines and implements Urbit's encrypted P2P network protocol, as well
88− as Urbit's identity protocol.
89−- Behn: manages timer events for other vanes.
90−- Clay: global, version-controlled, and referentially-transparent file system.
91−- Dill: terminal driver.
92−- Eyre: HTTP web client and server.
93−- Ford: typed functional build system.
94−- Gall: application sandbox and manager.
95− - Dojo (app): Shell and Hoon REPL.
96− - Talk (app): Chat client.
97−
98−### Hoon
99−
100−Hoon is a strictly typed functional programming language that compiles itself
101−to Nock and is designed to support higher-order functional programming without
102−requiring knowledge of category theory or other advanced mathematics. Haskell
103−is fun but it isn't for everybody.
104−
105−Hoon aspires to a concrete, imperative feel. To discourage the creation of
106−write-only code, Hoon forbids user-level macros and uses ASCII digraphs instead
107−of keywords. The type system infers only forward and does not use unification,
108−but is not much weaker than Haskell's. The compiler and inference engine is
109−about 3000 lines of Hoon.
110−
111−### Nock
112−
113−Nock is a low-level [homoiconic](https://en.wikipedia.org/wiki/Homoiconicity)
114−combinator language. It's so simple that its [specification](@/docs/learn/nock/definition.md)
115−fits on a t-shirt. In some ways Nock resembles a nano-Lisp but its ambitions
116−are more narrow. Most Lisps are one-layer: a practical language is to be
117−created by extending a theoretically simple interpreter. The abstraction is
118−simple and the implementation is practical. Unfortunately it's far more difficult
119−to enforce both simplicity and practicality in an actual Lisp codebase. Hoon
120−and Nock are two layers: Hoon, the practical layer, compiles itself to Nock, the
121−simple layer. Your urbit runs in Vere, which includes a Nock interpreter, so it
122−can upgrade Hoon over the network without downtime.
123−
124−The Nock data model is quite simple. Every piece of data is a 'noun'. A noun
125−is an atom or a cell. An atom is any unsigned integer. A cell is an ordered
126−pair of nouns. Nouns are acyclic and expose no pointer equality test.
127−
128−### Vere
129−
130−Vere is the Nock runtime environment and Urbit VM. It's written in C, runs on
131−Unix, and is the intermediate layer between your urbit and Unix. As noted
132−earlier, Unix system calls are made by Vere, not Arvo; Vere must also encode
133−and deliver relevant external events to Arvo. Vere is also responsible for
134−implementing jets and maintaining the persistent state of each urbit.
135−
136−In principle, Vere keeps a comprehensive log of every event from the time you
137−initially booted your urbit. What happens if the physical machine loses power
138−and your urbit's state is 'lost' from memory? When your urbit restarts it will
139−replay its entire event history and totally recover its latest state from
140−scratch.
141−
142−In practice, event logs become large and unwieldy over time. Periodically a
143−snapshot of the permanent state is taken and the logs are pruned. You're still
144−able to rebuild your state in case of power outage, down to the last keystroke.
145−
146−Vere is not essential to the Urbit stack; one can imagine using Urbit on a
147−hypervisor, or even bare metal. One member of the community is even working on
148−an independent implementation of Urbit using Graal/Truffle on the JVM.
149−
150−The Urbit stack (compiler, standard library, kernel, modules, and applications,
151−but excluding Vere) is about 30,000 lines of Hoon. Urbit is patent-free and MIT
152−licensed.
153−
154−### Azimuth
155−
156−Azimuth is a general-purpose public-key infrastructure (PKI) on the Ethereum
157−blockchain, used as a decentralized ledger for Urbit identities that we call
158−**points**. Having a point is necessary to use the Urbit network, which makes it
159−important to have a neutral ledger to determine who owns what.
160−
161−Azimuth is not, however, part of the Urbit stack. Azimuth is a parallel system
162−that can be used as a generalized identity system for other projects. Azimuth
163−"touches" the Urbit ecosystem when a point is used to boot a virtual computer
164−on the Urbit network for the first time. When that happens, the point considered
165−**linked** to Azimuth and the point’s full powers are available for use. Once a
166−point is linked, it cannot be unlinked.
167−
168−A metaphor might make the relationship between these two systems to understand:
169−Azimuth is the bank vault that stores the deed to your house. The Urbit network
170−is the neighborhood that you live in.
getting-started/_index.mddeleted−37
@@ -1,37 +0,0 @@
1−+++
2−title = "Getting Started"
3−weight = 1
4−sort_by = "weight"
5−template = "sections/docs/chapters.html"
6−+++
7−
8−Welcome to Urbit, a personal server. Urbit isn't ready for serious use yet, but it's available to try out. If you have an Azimuth point, you can follow this step-by-step guide to get your point's _keyfile_, which you need to boot your ship. Then you can install Urbit and join the community.
9−
10−If you don't have an Azimuth point, you can always [create a comet](@/docs/using/creating-a-comet.md) to join the network before committing to a point, or [create a development ship](@/docs/using/creating-a-development-ship.md) and start using Urbit offline first.
11−
12−### [Step 1: Using Bridge](@/docs/getting-started/using-bridge.md)
13−
14−In order to join the Urbit network, you need an Azimuth point, which acts like an identity and a password for your Urbit ship. Bridge is our client for managing Azimuth points, and lets you get your keyfile and claim the point.
15−
16−### [Step 2: Installing Urbit](@/docs/getting-started/installing-urbit.md)
17−
18−The Urbit software is a command-line application that runs the Arvo operating system. This guide walks you through the installation process.
19−
20−### [Step 3: Booting a Ship](@/docs/getting-started/booting-a-ship.md)
21−
22−This guide teaches you how to get your ship operational and onto the Arvo network.
23−
24−### [Optional: Contributing](contributing)
25−
26−This document will get your started with contributing code or contributing to the community.
27−
28−## Terminology
29−
30−You've already encountered some new terminology on this page, and you'll encounter more as you proceed with this guide. Let's go over the basics:
31−
32−- Arvo is the name of the Urbit operating system.
33−- An instance of the Arvo operating system is called a _ship_.
34−- Ships communicate with one another over "the Arvo network."
35−- Azimuth is an Ethereum-based PKI used to give each ship a unique identity on the Arvo network.
36−- An Azimuth identity is called a _point_. You'll need a point to use the Arvo network.
37−- Urbit refers to the project as a whole, including Arvo, Azimuth, and other system components.
getting-started/booting-a-ship.mddeleted−108
@@ -1,108 +0,0 @@
1−+++
2−title = "Booting a Ship"
3−weight = 3
4−template = "doc.html"
5−+++
6−Now the rubber meets the road. You'll be booting your ship with the keyfile that you [downloaded from Bridge](@/docs/concepts/azimuth.md).
7−
8−Note that this document is only for booting a ship that uses the live Arvo network. If you just want to create an unnetworked ship for development purposes, read [this guide](@/docs/using/creating-a-development-ship.md) instead.
9−
10−## Step 1: Find Your Point's Name
11−
12−This will look something like `~lodleb-ritrul`. You can see the name of your point(s) when you log into your wallet using the Bridge client.
13−
14−![](https://media.urbit.org/site/bridge-0.png)
15−
16−## Step 2: Find the path to your keyfile
17−
18−Find the absolute path to the keyfile that you downloaded from Bridge. Copy it.
19−
20−## Step 3: Run the boot command
21−
22−Type `cd` in your terminal to return to your home directory. If you want to
23−store your ship somewhere besides your home directory, change the terminal's
24−working directory to the desired directory.
25−
26−Run the command below, except with `sample-planet` replaced by the name of your
27−Urbit identity, and `path/to/my-planet.key` replaced with the path to your
28−keyfile:
29−
30−```
31−./urbit -w sample-planet -k path/to/my-planet.key
32−```
33−
34−Or, if you'd prefer to copy your key in, you can run:
35−
36−```
37−./urbit -w sample-planet -G rAnDoMkEy
38−```
39−
40−Either command will create a directory called `sample-planet/` and begin
41−building your ship. It may take a few minutes.
42−
43−When your ship is finished booting, you will see the `~sample-planet:dojo>`
44−prompt. At that point, you should permanently erase your keyfile from your
45−machine.
46−
47−## Basic Operations
48−
49−Welcome to your ship! There's a few things you should do to become oriented.
50−
51−### The Dojo
52−
53−Let's try out the Dojo, the Arvo command line and Hoon REPL:
54−
55−```
56−~sample-planet:dojo> (add 2 2)
57−```
58−
59−Should produce:
60−
61−```
62−> (add 2 2)
63−4
64−```
65−
66−Good.
67−
68−### Mounting
69−
70−Your ship's filesystem being "mounted" means that its filesystem can be interacted with through Unix. This makes things much easier for you.
71−
72−The Arvo filesystem isn't mounted to Unix by default. Switch to the Dojo prompt and run:
73−
74−```
75−~sample-planet:dojo> |mount %
76−```
77−
78−This should produce:
79−
80−```
81−> |mount %
82−>=
83−```
84−
85−which indicates that the command was processed.
86−
87−`|mount %` will cause a `home/` directory to appear inside your _pier_ folder in Unix (the "pier" is our shorthand for the directory whose name corresponds to your Azimuth point). Once you've changed a file, `|commit %home` to synchronize changes to your pier.
88−
89−**Note:** Do not delete your pier. Doing so will make your ship unusable, because deleted piers normally cannot be recovered. The exception is during a network breach (a reset) -- in such a rare event, you must delete your pier to update your ship to the new era, and ships with previously deleted piers can be recovered.
90−
91−### Shutting Down and Restarting
92−
93−You can toggle between the Dojo and Talk (chat) prompts with `ctrl-x`. You can turn your ship off with `ctrl-d` from the Talk or Dojo prompts.
94−
95−To restart your ship, simply pass the name of your pier:
96−
97−```
98−./urbit some-planet
99−```
100−
101−### Using Landscape
102−
103−Landscape is the Urbit web interface, and it's the best way to interact with your ship. Chrome and Brave are the recommended browsers for using Landscape. To get onto Landscape:
104−
105−1. Start your ship. In the boot messages, look for a line that says something like `http: live (insecure, public) on 80`. The number given is the port that your ship is using.
106−2. If the port given is 80, simply type `localhost` into your browser's address bar. If the given port is a different number, such as `8080`, you would type `localhost:8080`.
107−3. Type `+code` into your ship's Dojo. Copy-paste the returned code into the field asking for it.
108−4. You're in! Now you can explore apps such as Chat for messages, Publish for blogging, and Weather.
getting-started/contributing.mddeleted−21
@@ -1,21 +0,0 @@
1−+++
2−title = "Contributing"
3−weight = 5
4−template = "doc.html"
5−description = "A guide to getting involved with the Urbit project."
6−+++
7−
8−We welcome submissions for improving our [code](https://github.com/urbit/urbit/) and [documentation](https://github.com/urbit/docs/) alike. If you're looking to get involved, there are a few things you can do to get started right away:
9−
10−- Join the [urbit-dev](https://groups.google.com/a/urbit.org/forum/#!forum/dev) mailing list
11−- [Apply to Hoon School](https://urbit.org/hoonschool/). We run a beginner course and an advanced course to teach the Hoon programming language and Urbit application development. Both courses are free, online, and asynchronous.
12−- Check out the "good contributor issues" tag in the [urbit](https://github.com/urbit/urbit/labels/good%20contributor%20issue) and [arvo](https://github.com/urbit/arvo/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+contributor+issue%22) Github repositories.
13−- Reach out to [support@urbit.org](mailto:support@urbit.org) to say hi and ask any questions you might have. We're always happy to try to point you in the right direction.
14−
15−Many contributors start by contributing to the [documentation](https://github.com/urbit/docs), [urbit.org](https://github.com/urbit/urbit.org), or [bridge](https://github.com/urbit/bridge) repositories. If you're not yet comfortable with Hoon, we recommend starting there.
16−
17−If you're just getting set up to work on the Urbit or Arvo code base for the first time, see our [Getting Started](@/docs/getting-started/_index.md) guide, then have a look at [CONTRIBUTING.md](https://github.com/urbit/urbit/blob/master/CONTRIBUTING.md) in the Urbit repository.
18−
19−## Code style
20−
21−Before contributing Hoon code, you should familiarize yourself with the [Hoon style guide](@/docs/learn/hoon/style.md). For a good example of idiomatic Hoon, see [Ford](https://github.com/urbit/urbit/blob/master/pkg/arvo/sys/vane/ford.hoon).
getting-started/installing-urbit.mddeleted−74
@@ -1,74 +0,0 @@
1−+++
2−title = "Installing Urbit"
3−weight = 2
4−template = "doc.html"
5−+++
6−
7−Arvo runs nicely on a Unix-like operating system – Ubuntu, Fedora, macOS, and FreeBSD, for example. If you're using Windows, you'll need to get one of the aforementioned systems. Don't worry: most of them are free. Let's get it onto your machine.
8−
9−But first, some terminology:
10−
11−- `vere` or `urbit`: the interpreter that runs when you run a command like `urbit` or `/bin/urbit` in your command line
12−- `arvo`: the deterministic OS that lives in a directory whose name matches your Azimuth point, ie `~famreb-todmec` lives in `/famreb-todmec`
13−
14−We have different installation instructions for different platforms. To install and run Arvo, run the commands that are listed for your operating system.
15−
16−On any platform, you can check your Arvo installation by running the `urbit` command. Installation was successful if you get a block of output that begins with the line below:
17−
18−```
19−Urbit: a personal server operating function
20−```
21−
22−## Instructions
23−
24−### macOS (Darwin)
25−
26−We provide static binaries for macOS. You can grab the latest stable release as follows:
27−
28−```
29−curl -O https://bootstrap.urbit.org/urbit-darwin-v0.8.2.tgz
30−tar xzf urbit-darwin-v0.8.2.tgz
31−./urbit
32−```
33−
34−### Linux (64-bit)
35−
36−We also provide static binaries for 64-bit Linux distributions (Ubuntu, Debian, Fedora, Arch, etc.). You can get the latest stable release similarly:
37−
38−```
39−curl -O https://bootstrap.urbit.org/urbit-linux64-v0.8.2.tgz
40−tar xzf urbit-linux64-v0.8.2.tgz
41−./urbit
42−```
43−
44−To access your Urbit via HTTP on port 80 on Ubuntu, you may need to run the following:
45−
46−```
47−sudo apt-get install libcap2-bin
48−sudo setcap 'cap_net_bind_service=+ep' /path/to/urbit
49−```
50−
51−### Other
52−
53−We maintain a [Nix](https://nixos.org/nix) derivation for Urbit in [nixpkgs](https://github.com/NixOS/nixpkgs), however we're still in the process of updating it to `v0.8.2`. Once available, you will be able to install and launch it like so:
54−
55−```
56−nix-env -i urbit
57−urbit
58−```
59−
60−## Booting a Ship
61−
62−One you've completed your installation, you can continue on to the instructions for [booting your ship](@/docs/getting-started/booting-a-ship.md) to get on the Arvo network.
63−
64−Or, if you want to try testing and writing code, check out the guide to [getting an unnetworked development ship](/docs/using/creating-a-development-ship).
65−
66−## Set Up Swap
67−
68−If you're running Urbit in the cloud on a small instance, you may need to additionally configure swap space. If you're not, you can safely ignore this section.
69−
70−Urbit wants to map 2GB of memory when it boots up. We won’t necessarily use all this memory, we just want to see it. On a normal modern PC or Mac, or on a large cloud virtual machine, this is not an issue. On some small cloud virtual machines (Amazon or Digital Ocean), the default memory configuration is smaller than this, and you need to manually configure a swapfile.
71−
72−Digital Ocean has a post on adding swap [here](https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-16-04). For Amazon there’s a StackOverflow thread [here](https://stackoverflow.com/questions/17173972/how-do-you-add-swap-to-an-ec2-instance).
73−
74−Don’t spend a lot of time tweaking these settings; the simplest thing is fine.
getting-started/using-bridge.mddeleted−70
@@ -1,70 +0,0 @@
1−+++
2−title = "Using Bridge"
3−weight = 1
4−template = "doc.html"
5−+++
6−
7−[Bridge](https://github.com/urbit/bridge) is the application we built for interacting with [Azimuth](@/docs/concepts/azimuth.md), the Urbit PKI, and managing your Azimuth identities, also known as _points_. Importantly, Bridge also allows you to generate a keyfile that you will need to boot your ship so that it can use the Arvo network.
8−
9−This guide assumes that you own an Azimuth identity, or that you have found someone to send an Azimuth identity to your Ethereum address and are looking to claim it.
10−
11−## Online Bridge
12−
13−To connect to Bridge, type `https://bridge.urbit.org` into your browser, and enter the your identity's credentials in the appropriate fields. If you were invited to claim an Azimuth identity, it's very likely that you received an email that would direct you to Bridge, and you can simply follow the hyperlink in that email.
14−
15−Once you arrive Proceed through the steps presented to you. You'll eventually arrive at a page with a few choices: `Invite`, `Admin`, and `Boot Arvo`. `Admin` is the only option that you're interested in right now; click on it. On the "Admin" page, click the `Download Arvo Keyfile` button. Once you have downloaded the keyfile, you can exit Bridge ands proceed to the guide to [installing Arvo](@/docs/getting-started/installing-urbit.md).
16−
17−## Offline Bridge
18−
19−Alternatively, Bridge can be run locally. It's more complicated, but we recommend this option for managing sufficiently valuable assets, such as several stars or more. To install local Bridge, navigate to the [release page](https://github.com/urbit/bridge/releases/) on GitHub. Download the `.zip` file of the latest version. After you download it, follow the instructions below.
20−
21−### Installation
22−
23−To use Bridge:
24−
25−+ Unzip the `.zip` file that you downloaded (`bridge-$version.zip`).
26−+ Open up your command line interface (Terminal on OSX, Command Prompt on Windows).
27−+ Navigate to the `bridge-$version` directory, where `$version` is the appropriate version number.
28−+ Run this command: `python3 -m http.server 5000 --bind 127.0.0.1`
29−+ You can then use the Bridge app by navigating to `http://localhost:5000` in your internet browser.
30−
31−**Note:** Bridge allows you both make reads and writes to the Ethereum blockchain. Writing to the blockchain, such as changing your networking keys, will incur a transaction cost that will require you to have some ETH in your address.
32−
33−Once the program is running in your browser, go through each step presented according to what kind of wallet you have. There are a few login options you'll be presented with. A notable option is **Urbit Master Ticket**. This is for those who used our Wallet Generator software. If you bought points from an Urbit sale and then used the Wallet Generator, your networking keys will be set for you. All other login options will result in you needing to set your own networking keys.
34−
35−### Accept Your Transfer
36−
37−If you were given points by Tlon, you likely already fully own them. But if someone sent you a point, then you will first need to use Bridge to accept that transfer.
38−
39−After you access your Ethereum address, if a point was sent to that address,
40−you'll come to a page that has an `Incoming Transfers` header, under which is
41−a graphic. Click the `Details ->` link under that graphic.
42−
43−Now you'll be on the management page of your point. The transfer isn't completed
44−yet, so click `Accept incoming transfer`. Then check both boxes and and click
45−their associated `Sign Transaction` and `Send Transaction` buttons.
46−
47−If you already own a point, then click on the `Details ->` under your sigil in the
48−`Your Points` section.
49−
50−### Set Your Networking Keys
51−
52−If you just accepted a point, you'll be returned to your point screen. Notice that that links and buttons are now clickable. You now own this point!
53−
54−Click the link that says `Set network keys`. The field that is presented in the resulting page expects a 32-byte hexadecimal string. If it's filled already, no action is required. If this is empty, you will need to generate such a string. You can generate this data any way you please, but in the terminal on MacOS or Linux, you can write
55−
56−```
57−hexdump -n 32 -e '4/4 "%08X"' /dev/random
58−```
59−
60−and use the result.
61−
62−It should be noted that setting your network keys is an event on the Ethereum network, and will therefore cost a trivial, but non-zero, amount of [gas](https://github.com/ethereum/wiki/wiki/Design-Rationale#gas-and-fees) to complete.
63−
64−### Generate Your Keyfile
65−
66−From the detail page associated with your point, click the `Generate Arvo Keyfile` link and you'll be taken to a page with a field titled `Network seed`. This field should already be filled in, and should match the hexadecimal string that you entered in the previous step. If its not filled in or does not match, fill it in with the correct string.
67−
68−Click `Generate ->`, which will download a keyfile onto your machine.
69−
70−With that keyfile in hand, you can now exit Bridge, and continue to the guide to [installing Arvo](@/docs/getting-started/installing-urbit.md).
learn/hoon/_index.md → hoon/_index.mdrenamed

The content is the same.

reference/cheat-sheet.md → hoon/cheat-sheet.mdrenamed

The content is the same.

reference/hoon-expressions/_index.md → hoon/hoon-expressions/_index.mdrenamed

The content is the same.

reference/hoon-expressions/advanced.md → hoon/hoon-expressions/advanced.mdrenamed

The content is the same.

reference/hoon-expressions/basic.md → hoon/hoon-expressions/basic.mdrenamed

The content is the same.

reference/hoon-expressions/irregular.md → hoon/hoon-expressions/irregular.mdrenamed

The content is the same.

reference/hoon-expressions/limb/_index.md → hoon/hoon-expressions/limb/_index.mdrenamed

The content is the same.

reference/hoon-expressions/limb/limb.md → hoon/hoon-expressions/limb/limb.mdrenamed

The content is the same.

reference/hoon-expressions/limb/wing.md → hoon/hoon-expressions/limb/wing.mdrenamed

The content is the same.

reference/hoon-expressions/rune/_index.md → hoon/hoon-expressions/rune/_index.mdrenamed

The content is the same.

reference/hoon-expressions/rune/bar.md → hoon/hoon-expressions/rune/bar.mdrenamed

The content is the same.

reference/hoon-expressions/rune/buc.md → hoon/hoon-expressions/rune/buc.mdrenamed

The content is the same.

reference/hoon-expressions/rune/cen.md → hoon/hoon-expressions/rune/cen.mdrenamed

The content is the same.

reference/hoon-expressions/rune/col.md → hoon/hoon-expressions/rune/col.mdrenamed

The content is the same.

reference/hoon-expressions/rune/constants.md → hoon/hoon-expressions/rune/constants.mdrenamed

The content is the same.

reference/hoon-expressions/rune/dot.md → hoon/hoon-expressions/rune/dot.mdrenamed

The content is the same.

reference/hoon-expressions/rune/ket.md → hoon/hoon-expressions/rune/ket.mdrenamed

The content is the same.

reference/hoon-expressions/rune/lus.md → hoon/hoon-expressions/rune/lus.mdrenamed

The content is the same.

reference/hoon-expressions/rune/mic.md → hoon/hoon-expressions/rune/mic.mdrenamed

The content is the same.

reference/hoon-expressions/rune/sig.md → hoon/hoon-expressions/rune/sig.mdrenamed

The content is the same.

reference/hoon-expressions/rune/terminators.md → hoon/hoon-expressions/rune/terminators.mdrenamed

The content is the same.

reference/hoon-expressions/rune/tis.md → hoon/hoon-expressions/rune/tis.mdrenamed

The content is the same.

reference/hoon-expressions/rune/wut.md → hoon/hoon-expressions/rune/wut.mdrenamed

The content is the same.

reference/hoon-expressions/rune/zap.md → hoon/hoon-expressions/rune/zap.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/_index.md → hoon/hoon-tutorial/_index.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/ackermann.md → hoon/hoon-tutorial/ackermann.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/arms-and-cores.md → hoon/hoon-tutorial/arms-and-cores.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/atoms-auras-and-simple-cell-types.md → hoon/hoon-tutorial/atoms-auras-and-simple-cell-types.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/bank-account.md → hoon/hoon-tutorial/bank-account.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/caesar.md → hoon/hoon-tutorial/caesar.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/conditionals.md → hoon/hoon-tutorial/conditionals.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/doors.md → hoon/hoon-tutorial/doors.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/egg-timer.md → hoon/hoon-tutorial/egg-timer.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/fibonacci.md → hoon/hoon-tutorial/fibonacci.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/gall.md → hoon/hoon-tutorial/gall.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/gates.md → hoon/hoon-tutorial/gates.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/generators.md → hoon/hoon-tutorial/generators.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/hoon-syntax.md → hoon/hoon-tutorial/hoon-syntax.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/iron-polymorphism.md → hoon/hoon-tutorial/iron-polymorphism.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/lead-polymorphism.md → hoon/hoon-tutorial/lead-polymorphism.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/libraries.md → hoon/hoon-tutorial/libraries.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/list-of-numbers.md → hoon/hoon-tutorial/list-of-numbers.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/lists.md → hoon/hoon-tutorial/lists.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/molds.md → hoon/hoon-tutorial/molds.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/nouns.md → hoon/hoon-tutorial/nouns.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/recursion.md → hoon/hoon-tutorial/recursion.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/setup.md → hoon/hoon-tutorial/setup.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/structures-and-complex-types.md → hoon/hoon-tutorial/structures-and-complex-types.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/the-subject-and-its-legs.md → hoon/hoon-tutorial/the-subject-and-its-legs.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/trees-sets-and-maps.md → hoon/hoon-tutorial/trees-sets-and-maps.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/type-checking-and-type-inference.md → hoon/hoon-tutorial/type-checking-and-type-inference.mdrenamed

The content is the same.

learn/hoon/hoon-tutorial/type-polymorphism.md → hoon/hoon-tutorial/type-polymorphism.mdrenamed

The content is the same.

reference/library/1a.md → hoon/library/1a.mdrenamed

The content is the same.

reference/library/1b.md → hoon/library/1b.mdrenamed

The content is the same.

reference/library/1c.md → hoon/library/1c.mdrenamed

The content is the same.

reference/library/2a.md → hoon/library/2a.mdrenamed

The content is the same.

reference/library/2b.md → hoon/library/2b.mdrenamed

The content is the same.

reference/library/2c.md → hoon/library/2c.mdrenamed

The content is the same.

reference/library/2d.md → hoon/library/2d.mdrenamed

The content is the same.

reference/library/2e.md → hoon/library/2e.mdrenamed

The content is the same.

reference/library/2f.md → hoon/library/2f.mdrenamed

The content is the same.

reference/library/2g.md → hoon/library/2g.mdrenamed

The content is the same.

reference/library/2h.md → hoon/library/2h.mdrenamed

The content is the same.

reference/library/2i.md → hoon/library/2i.mdrenamed

The content is the same.

reference/library/2j.md → hoon/library/2j.mdrenamed

The content is the same.

reference/library/2k.md → hoon/library/2k.mdrenamed

The content is the same.

reference/library/2l.md → hoon/library/2l.mdrenamed

The content is the same.

reference/library/2m.md → hoon/library/2m.mdrenamed

The content is the same.

reference/library/2n.md → hoon/library/2n.mdrenamed

The content is the same.

reference/library/2o.md → hoon/library/2o.mdrenamed

The content is the same.

reference/library/2p.md → hoon/library/2p.mdrenamed

The content is the same.

reference/library/2q.md → hoon/library/2q.mdrenamed

The content is the same.

reference/library/3a.md → hoon/library/3a.mdrenamed

The content is the same.

reference/library/3b.md → hoon/library/3b.mdrenamed

The content is the same.

reference/library/3c.md → hoon/library/3c.mdrenamed

The content is the same.

reference/library/3d.md → hoon/library/3d.mdrenamed

The content is the same.

reference/library/3e.md → hoon/library/3e.mdrenamed

The content is the same.

reference/library/3f.md → hoon/library/3f.mdrenamed

The content is the same.

reference/library/3g.md → hoon/library/3g.mdrenamed

The content is the same.

reference/library/4a.md → hoon/library/4a.mdrenamed

The content is the same.

reference/library/4b.md → hoon/library/4b.mdrenamed

The content is the same.

reference/library/4c.md → hoon/library/4c.mdrenamed

The content is the same.

reference/library/4d.md → hoon/library/4d.mdrenamed

The content is the same.

reference/library/4e.md → hoon/library/4e.mdrenamed

The content is the same.

reference/library/4f.md → hoon/library/4f.mdrenamed

The content is the same.

reference/library/4g.md → hoon/library/4g.mdrenamed

The content is the same.

reference/library/4h.md → hoon/library/4h.mdrenamed

The content is the same.

reference/library/4i.md → hoon/library/4i.mdrenamed

The content is the same.

reference/library/4j.md → hoon/library/4j.mdrenamed

The content is the same.

reference/library/4k.md → hoon/library/4k.mdrenamed

The content is the same.

reference/library/4l.md → hoon/library/4l.mdrenamed

The content is the same.

reference/library/4m.md → hoon/library/4m.mdrenamed

The content is the same.

reference/library/4n.md → hoon/library/4n.mdrenamed

The content is the same.

reference/library/4o.md → hoon/library/4o.mdrenamed

The content is the same.

reference/library/5a.md → hoon/library/5a.mdrenamed

The content is the same.

reference/library/5b.md → hoon/library/5b.mdrenamed

The content is the same.

reference/library/5c.md → hoon/library/5c.mdrenamed

The content is the same.

reference/library/5d.md → hoon/library/5d.mdrenamed

The content is the same.

reference/library/5e.md → hoon/library/5e.mdrenamed

The content is the same.

reference/library/5f.md → hoon/library/5f.mdrenamed

The content is the same.

reference/library/5g.md → hoon/library/5g.mdrenamed

The content is the same.

reference/library/_index.md → hoon/library/_index.mdrenamed

The content is the same.

reference/library/table-of-contents.md → hoon/library/table-of-contents.mdrenamed

The content is the same.

reference/library/zuse.md → hoon/library/zuse.mdrenamed

The content is the same.

learn/hoon/style.md → hoon/style.mdrenamed

The content is the same.

reference/hoon-errors.md → hoon/troubleshooting.mdrenamed+2−2
@@ -1,6 +1,6 @@
1+++
1+++
2−title = "Hoon Errors"
2+title = "Troubleshooting Hoon"
3−weight = 6
3+weight = 5
4template = "doc.html"
4template = "doc.html"
5+++
5+++
6Ideally your Hoon works perfectly the first time. But...
6Ideally your Hoon works perfectly the first time. But...
learn/hoon/workbook/_index.md → hoon/workbook/_index.mdrenamed

The content is the same.

learn/hoon/workbook/bomb.md → hoon/workbook/bomb.mdrenamed

The content is the same.

learn/hoon/workbook/digits.md → hoon/workbook/digits.mdrenamed

The content is the same.

learn/hoon/workbook/eightball.md → hoon/workbook/eightball.mdrenamed

The content is the same.

learn/hoon/workbook/traffic-light.md → hoon/workbook/traffic-light.mdrenamed

The content is the same.

learn/_index.mddeleted−27
@@ -1,27 +0,0 @@
1−+++
2−title = "Learn"
3−weight = 4
4−sort_by = "weight"
5−template = "sections/docs/chapters.html"
6−+++
7−Tutorials and explanations for all the components of Urbit.
8−
9−## [Arvo](@/docs/learn/arvo/_index.md)
10−
11−Arvo is a clean-slate system software stack defined as a deterministic computer. An encrypted P2P network, %ames, runs on a functional operating system, Arvo, written in a strict, typed functional language, Hoon, which compiles itself to a combinator interpreter, Nock, whose spec gzips to 340 bytes.
12−
13−## [Hoon](@/docs/learn/hoon/_index.md)
14−
15−Hoon is a high-level, statically typed, functional programming language, custom-designed for use with Urbit. For a functional language it has a surprisingly imperative style, and mastering it doesn't require knowing any advanced mathematics.
16−
17−The [Hoon Tutorial](@/docs/learn/hoon/hoon-tutorial/_index.md) is the best place to start if you want to learn Urbit.
18−
19−## [Nock](@/docs/learn/nock/_index.md)
20−
21−Nock is the low-level functional programming language that is interpreted by Vere. You don't need to know Nock to write Hoon, or even to work on most parts of Vere. But if you want to understand the foundations of Urbit and are mathematically-inclined, dive right in.
22−
23−## [Vere](@/docs/learn/vere/_index.md)
24−
25−The Nock runtime system, written in C.
26−
27−Keep reading if you're planning to work on the Urbit interpreter, you're a language implementation geek, or you don't really understand anything until you've seen the actual structs.
learn/nock/_index.md → nock/_index.mdrenamed

The content is the same.

learn/nock/definition.md → nock/definition.mdrenamed

The content is the same.

learn/nock/example.md → nock/example.mdrenamed

The content is the same.

learn/nock/explanation.md → nock/explanation.mdrenamed

The content is the same.

learn/nock/implementations.md → nock/implementations.mdrenamed

The content is the same.

reference/_index.mddeleted−29
@@ -1,29 +0,0 @@
1−+++
2−title = "Reference"
3−weight = 5
4−sort_by = "weight"
5−template = "sections/docs/chapters.html"
6−+++
7−Various reference documents are stored here, particularly for Hoon, but also for other parts of the system.
8−
9−## [The Arvo Glossary](@/docs/reference/arvo-glossary.md)
10−
11−Urbit is known for introducing a great deal of new terminology. The glossary will
12−help demystify our jargon.
13−
14−## [The Cheat Sheet](@/docs/reference/cheat-sheet.md)
15−
16−The cheat sheet is a compact document for looking up Hoon runes.
17−
18−## [Hoon Expressions](@/docs/reference/hoon-expressions/_index.md)
19−
20−This section contains more comprehensive reference materials for Hoon runes and other expressions, describing their exact
21−semantics and syntax.
22−
23−## [Standard Library](@/docs/reference/library/_index.md)
24−
25−This section documents the gates and mold-builders of the Hoon standard library.
26−
27−## [Troubleshooting](@/docs/reference/troubleshooting.md)
28−
29−When your Hoon produces an error, check what it means here.
using/_index.mddeleted−18
@@ -1,18 +0,0 @@
1−+++
2−title = "Using"
3−weight = 2
4−sort_by = "weight"
5−template = "sections/docs/chapters.html"
6−+++
7−This section contains guides to using your urbit.
8−
9−- [Creating a Development Ship](creating-a-development-ship) will show you how to set up the environment for coding on Urbit.
10−- [Creating a Comet](creating-a-comet) will show you how to create a comet: quick, disposable 128-bit identities on the Urbit network.
11−- [Admin and Operation](admin) is a guide to the basic commands used to interact with your ship.
12−- [Messaging](messaging) tells you how to use Talk, our chat system.
13−- [Shell](shell) is a guide to using Dojo, our command-line interface.
14−- [Introduction to the Filesystem](filesystem) explains the basics of using use Clay, our revision-control filesystem.
15−- [Source Layout](layout) walks you through the various directories of the Arvo operating system.
16−- [Sail](sail) is a guide to Sail: Hoon markup that's used to build web pages with XML.
17−- [Udon](udon) is a guide to Udon, which is our take on Markdown.
18−- [Generators](generators) will explain how to use the "generator," a kind of file that's the easiest way to run Hoon programs.
using/admin.mddeleted−213
@@ -1,213 +0,0 @@
1−+++
2−title = "Admin and Operations"
3−weight = 2
4−template = "doc.html"
5−+++
6−Your urbit (also called your _ship_) is a persistent Unix process that you
7−mainly control from the console. For some things, a browser will also work.
8−
9−## Shutdown
10−
11−You can turn your urbit off with `Ctrl-d` from the Talk or Dojo prompts.
12−
13−You can force-quit your urbit with `Ctrl-z` from anywhere.
14−
15−## Restart
16−
17−To restart your urbit simply pass the name of your pier:
18−
19−```
20−$ urbit some-planet
21−```
22−
23−or
24−
25−```
26−$ urbit comet
27−```
28−
29−## Logging
30−
31−To log an urbit's command line output to a file, use `script`:
32−
33−```
34−$ script urbit.log urbit your-urbit
35−```
36−
37−## Moving your pier
38−
39−Piers are designed to be portable, but it _must_ be done while the urbit
40−is turned off. Urbit networking is stateful, so you can't run two copies
41−of the same urbit in two places.
42−
43−To move a pier, simply move the contents of the directory it lives in.
44−To keep these files as small as possible we usually use the `--sparse`
45−option in `tar`. With a pier `your-urbit/`, something like this should work:
46−
47−```
48−tar -Scvzf ~/your-urbit.tar.gz ~/your-urbit/
49−scp your-old-server:~/your-urbit.tar.gz your-new-server:~
50−```
51−
52−Then to unzip it, on your other Unix server, run:
53−
54−```
55−tar xfvz your-urbit.tar.gz
56−```
57−
58−Delete the tar file, and, after installing Urbit on your new server,
59−start your urbit back up with:
60−
61−```
62−urbit your-urbit
63−```
64−
65−## Console
66−
67−Your Urbit terminal is separated into two parts: the prompt (the bottom
68−line) and the record (everything above that). The record is shared; all
69−the output from all the apps in your command set appears in it. The
70−prompt is multiplexed.
71−
72−In the CLI, Urbit apps can process your input before you hit return. To
73−see this in action try entering `)` as the first character at the Dojo
74−prompt. Since there is no Dojo command or Hoon expression that starts
75−with ')', the Dojo rejects it.
76−
77−`Ctrl-x` - Switches the prompt between running console apps.
78−
79−`Ctrl-c` - Crash current event. Processed at the Unix layer and prints a stack.
80−trace.
81−
82−`Ctrl-d` - From Talk or Dojo, stops your Urbit process.
83−
84−`Ctrl-z` - Stops the Urbit process from _anywhere_.
85−
86−`↑` / `↓` - History navigation.
87−
88−`Backspace` - Interrupts running commands. For example, if you have begun a multiline Hoon expression and then press backspace, it will discard the already-written code, or if you press backspace while a request is still pending it will cancel it and print `! cancel /hand`.
89−
90−The following emacs-style key bindings are available:
91−
92−```
93−Ctrl-a Cursor to beginning of the line (Home)
94−Ctrl-b Cursor one character backward (left-arrow)
95−Ctrl-e Cursor to the end of the line (End)
96−Ctrl-f Cursor one character forward (right-arrow)
97−Ctrl-g Beep; cancel reverse-search
98−Ctrl-k Kill to end of line
99−Ctrl-l Clear the screen
100−Ctrl-n Next line in history (down-arrow)
101−Ctrl-p Previous line in history (up-arrow)
102−Ctrl-r Reverse-search
103−Ctrl-t Transpose characters
104−Ctrl-u Kill to beginning of line
105−Ctrl-y Yank from kill buffer
106−```
107−
108−Full coverage of the Urbit shell, the Dojo is covered in the
109−[Shell walkthrough](@/docs/using/shell.md).
110−
111−## Web
112−
113−On startup Urbit tries to bind to `localhost:80`. If you're already
114−running something on port `80` -- such as any other HTTP server, or another urbit -- you'll find the urbit
115−that you just started on `8080`, `8081`, and so on. For planets only, we also proxy web
116−domains through Urbit's own servers. Any planet `~your-urbit` is also at
117−`your-urbit.arvo.network`, but only after you [set up DNS](../dns-proxying).
118−
119−Your urbit serves a simple homepage from `http://localhost` or
120−`https://your-urbit.arvo.network` that should be self-explanatory. Since
121−our HTTPS isn't audited / battle tested, we just call it "secure" HTTPS.
122−You can find that on `8443`. Or `8444` (and so on) if you're already
123−running something on `8443`.
124−
125−## Moons {#moons}
126−
127−Planets can spawn moons, which are meant for connected devices: phones, smart
128−TVs, digital thermostats. The basic idea is: your planet runs permanently in a
129−data center somewhere and moons run on all your devices. Each planet can issue
130−~4 billion (`2^32`) moons.
131−
132−To generate a random moon from your planet, run:
133−
134−```
135−~sampel-palnet:dojo> +moon
136−moon: ~faswep-navred-sampel-palnet
137−\/~.0wd.rZU67.3jSny.z1vda.7sr-s.EL1Jt.-76Nj.ugXxY.g6-Bx.HvKZl.G53oV.hPnXe.7U3E3.J4CEe.MEVuq.~08Nt\/
138− .zNT0K.k-Ab~.Nn90d.OZ2fT.-XlQQ.Cfrkf.y6~K0.2Do09.EaE3W.BSK--.5Q~9N.y3QIP.eokH-.T6lwz.gg8MX.7LU5
139− x.DJROE.IzQsy.OXOLr.IOE3a.-QI40.H5ukK.Cw-u4.uxE-y.V-o1F.Q84g0.effP0.de01g.600g1
140−\/ \/
141−```
142−
143−You must manually edit the output of `+moon` to get
144−the correct format for the `<key>`:
145−
146−- strip out the `\/`
147−
148−- combine into one line, omitting spaces
149−
150−- trim the leading `~.`
151−
152−`<key>` would be `0wd.rZU67.3jSny.z1vda ... <snip> ... effP0.de01g.600g1`
153−in this example.
154−
155−Put `<key>` in a file and that file becomes `<keyfile>`.
156−
157−Another way of generating `<keyfile>` is:
158−
159−```
160−~sampel-palnet:dojo> @moon/key +moon
161−moon: ~faswep-navred-sampel-palnet
162−```
163−
164−`<keyfile>` will be at `path/to/sampel-palnet/.urb/put/moon.key`
165−and does not need editing to be used with the `-k` option.
166−
167−You can use the resulting output in the same installation flow from the
168−[Booting a Ship](@/docs/getting-started/booting-a-ship.md) guide, following the same scheme as for booting a planet. That scheme is:
169−
170−```
171−$ urbit -w <moonname> -G <key> -c <piername>
172−```
173−
174−or
175−
176−```
177−$ urbit -w <moonname> -k <keyfile> -c <piername>
178−```
179−
180−The `-c <piername>` argument is not required, but it is recommended; otherwise,
181−the resulting directory is a rather unwieldy moon name.
182−
183−Here's how an example moon might be booted:
184−
185−```
186−$ urbit -w faswep-navred-sampel-palnet -G <key> -c mymoon
187−```
188−
189−or
190−
191−```
192−$ urbit -w faswep-navred-sampel-palnet -k <keyfile> -c mymoon
193−```
194−
195−Moons are automatically synced to their parent `%kids` desk, and can control
196−applications on their parent planet using `|link`. You can read more about
197−those operations in the [filesystem](@/docs/using/filesystem.md) and [console](@/docs/using/shell.md)
198−walkthroughs, respectively.
199−
200−
201−## Continuity breaches
202−
203−While the Urbit network is in this alpha state, we sometimes have to
204−reboot the whole network. This happens either when major changes need
205−to be shipped or we hit a bug that can't be fixed over the air.
206−
207−Because Urbit networking is stateful we call this a _continuity breach_.
208−Everything has to be restarted from scratch. Your pier will continue to
209−function after we have breached, but it wont connect to the rest of the
210−Urbit network.
211−
212−When this happens, back up any files you'd like to save, shut down your
213−urbit and recreate it (as if you were starting for the first time).
using/arvo-network-dns.mddeleted−52
@@ -1,52 +0,0 @@
1−+++
2−title = "Arvo.network DNS"
3−weight = 2
4−template = "doc.html"
5−+++
6−
7−We have a system that lets you request a domain name for your ship in the form of `ship.arvo.network`, where `ship` is your ship's name minus the `~`. This allows users to access their ships remotely using Landscape, our graphical web interface.
8−
9−Stars and planets follow the same process DNS proxying process, and galaxies have their own requirements. Moons and comets are not supported.
10−
11−## Planets and Stars
12−
13−For a planet or star's DNS proxying request to be made and fulfilled, they must be hosting their ship someplace with a public IP address, and its HTTP server must be listening on port 80.
14−
15−To get `ship.arvo.network` on a planet or star, you must set up DNS routing with its parent ship by starting the `:dns` app.
16−To do so, simply run this command in your ship's Dojo:
17−
18−```
19−> :dns|request
20−```
21−
22−You'll then be prompted to enter the public IP address of your ship. You can also pass the IP address as an argument, using the .0.0.0.0 (`@if`) syntax. For example:
23−
24−```
25−> :dns|request .1.2.3.4
26−```
27−
28−`:dns`, running locally, will make an HTTP request to that IP address on port 80 to confirm that it is itself available at that IP and port. If that fails, you'll receive a `%bail-early` message in `:talk`; this request will retry a few times. If the self-check is successful, the request is relayed to `~zod`, and you'll receive a message saying, `request for DNS sent to ~zod`. Once `~zod` has acknowledged receipt of the request, your local `:dns` app will send a `:talk` message saying `awaiting response from ~zod`.
29−
30−The request will be picked up shortly, and the `ship.arvo.network` DNS record will be set to the given IP address. Once that's setup, `~zod` will be notified, and `~zod` will, in turn, notify your ship. That ship will now try to verify that it can reach itself on `ship.arvo.network` over port 80. If it can't, it'll send a message saying `unable to access via ship.arvo.network`. If it can, it will configure itself with that domain, and say `confirmed access via ship.arvo.network`.
31−
32−Great! You're set up now. Try accessing your `ship.arvo.network` in your browser to use Landscape; we recommend using Chrome or Brave.
33−
34−## Galaxies
35−
36−Galaxies are already required to have separate DNS entry at galaxy.urbit.org. There's no automated process for getting that binding, so if you're a galaxy-holder, get in touch with us at support@urbit.org.
37−
38−There is a command for galaxies that will try to re-use their already-necessary Ames DNS entry for HTTPS:
39−
40−```
41−> :dns|auto
42−```
43−
44−This will make HTTP-requests to self-check availability over `galaxy.$AMES-DOMAIN` (currently galaxy.urbit.org), where `galaxy` is the galaxy's name minus the `~`.
45−
46−Otherwise, `:dns|auto` works the same as `:dns|ip` does with stars and planets: if it's available or unavailable, talk messages, and so on.
47−
48−## More Information
49−
50−Configuring a ship's domain causes the `:acme` app to request an HTTPS certificate for that domain from LetsEncrypt. Note that LetsEncrypt also requires that the HTTP server be listening on port 80. If the certificate request fails, `:acme` will send a `:talk` message with an explanation. Once the certificate is successfully retrieved, `:acme` will install it, causing the HTTP servers to restart. A secure server will be started on port 443 (the HTTPS default) if it's available. Otherwise, it will try 8443, and then increment to the next port until it can successfully bind one.
51−
52−The built-in logic for listening on port 80 similar. Urbit tries to bind port 80; if it cannot, it tries 8080, then increments until it can bind a port. Port 80 is available to unprivileged process on recent version of macOS. Otherwise, the process needs to either be run as root, or be given special permission (CAP\_NET_BIND on Linux).
using/creating-a-comet.mddeleted−29
@@ -1,29 +0,0 @@
1−+++
2−title = "Creating a Comet"
3−weight = 1
4−template = "doc.html"
5−+++
6−
7−**Comets** are urbits whose names are 128-bits or 16 syllables, such as:
8−
9−`~dasres-ragnep-lislyt-ribpyl--mosnyx-bisdem-nidful-marzod`
10−
11−Comet names aren't quite as memorable as others, but they're disposable identities that anyone can make for free to join the live network.
12−
13−## Booting a Comet
14−
15−To boot your comet, go into the command line and run the following command from the directory that was created during Urbit installation:
16−
17−```
18−$ urbit -c mycomet
19−```
20−
21−This will take a few minutes and will spin out a bunch of boot messages. Toward the end, you'll see something like:
22−
23−```
24−ames: on localhost, UDP 31337.
25−http: live (insecure, public) on 8080
26−http: live ("secure", public) on 8443
27−http: live (insecure, loopback) on 12321
28−~dasres_marzod:dojo>
29−```
using/creating-a-development-ship.mddeleted−69
@@ -1,69 +0,0 @@
1−+++
2−title = "Creating a Development Ship"
3−weight = 0
4−template = "doc.html"
5−+++
6−
7−To do work with Hoon and with the system, we recommended using a "fake" ship -- one not connected to the network.
8−
9−Because such a ship has no presence on the network, you don't need an Azimuth identity for its purposes. You just need to have [installed our software](@/docs/getting-started/installing-urbit.md).
10−
11−To create a fake ship named `~zod`, run the command below. You can replace `zod` with any valid Urbit ship-name.
12−
13−```
14−urbit -F zod
15−```
16−
17−Now you should see a block of boot messages, starting with the Urbit version number. Welcome!
18−
19−## Basic Operations
20−
21−Welcome to your ship! There's a few things you should do to become oriented.
22−
23−### The Dojo
24−
25−Let's try out the Dojo, the Arvo command line and Hoon REPL:
26−
27−```
28−~sample-planet:dojo> (add 2 2)
29−```
30−
31−Should produce:
32−
33−```
34−> (add 2 2)
35−4
36−```
37−
38−Good.
39−
40−### Mounting
41−
42−Your ship's filesystem being "mounted" means that its filesystem can be interacted with through Unix. This makes things much easier for you.
43−
44−The Arvo filesystem isn't mounted to Unix by default. Switch to the Dojo prompt and run:
45−
46−```
47−~sample-planet:dojo> |mount %
48−```
49−
50−This should produce:
51−
52−```
53−> |mount %
54−>=
55−```
56−
57−which indicates that the command was processed.
58−
59−`|mount %` will cause a `home/` directory to appear inside your _pier_ folder in Unix (the "pier" is our shorthand for the directory whose name corresponds to your Azimuth point). Changes to these files can be committed to your pier by running `|commit %home` once you're done.
60−
61−### Shutting Down and Restarting
62−
63−You can turn your ship off with `ctrl-d` from the Talk or Dojo prompts.
64−
65−To restart your ship, simply pass the name of your pier:
66−
67−```
68−urbit some-planet
69−```
using/filesystem.mddeleted−471
@@ -1,471 +0,0 @@
1−+++
2−title = "Filesystem"
3−weight = 5
4−template = "doc.html"
5−+++
6−Urbit has its own revision-controlled filesystem, Clay. Clay is a typed, global,
7−referentially transparent namespace. An easy way to think about it is like typed
8−`git`.
9−
10−The most common way to use Clay is to mount a Clay node in a Unix directory. The mounted directory is always at the root of your
11−pier directory.
12−
13−## Quickstart
14−
15−This quick-start guide will walk you through some common commands. Follow along
16−using your Dojo. When you get a `>=` message after entering a command, this means
17−that the command was successful.
18−
19−When developing it's a good idea to use a separate desk. Create a `%sandbox`
20−desk based on the `%home` desk:
21−
22−```
23−~your-urbit:dojo> |merge %sandbox ~your-urbit %home
24−```
25−
26−Running `our` produces your ship-name, meaning that you can run the following
27−command instead of typing out the entire thing. Useful for comets, due to their
28−very long names.
29−
30−```
31−~your-urbit:dojo> |merge %sandbox our %home
32−```
33−
34−Most of the time we want to use Clay from Unix. Mount the entire contents of
35−your `sandbox` desk to Unix:
36−
37−```
38−~your-urbit:dojo> |mount /=sandbox=
39−```
40−
41−To explore the filesystem from inside Urbit `+ls` and `+cat` are useful. `+ls`
42−displays files in the current directory, and `+cat` displays the contents of
43−a file.
44−
45−We can use `%` to mean "current directory." The result of the command below
46−is just like using `ls` in a Unix terminal.
47−
48−```
49−~your-urbit:dojo> +ls %
50−```
51−
52−Notice how `+cat %` does the same thing. That's because everything in Clay,
53−including directories, is a file.
54−
55−Let's explore the `/web` directory of the `%sandbox` desk.
56−
57−```
58−~your-urbit:dojo> +ls /=sandbox=/web
59−```
60−
61−Let's see the contents of `/=sandbox=/web/404/hoon`:
62−
63−```
64−~your-urbit:dojo> +cat /=sandbox=/web/404/hoon
65−```
66−
67−Now let's navigate to `/web` on `%sandbox` using `=dir`, which is like `cd` in Unix.
68−
69−```
70−~your-urbit:dojo> =dir /=sandbox=/web
71−```
72−
73−You'll notice that your prompt is now
74−`~your-urbit:dojo/=/sandbox/~2018.10.2..00.35.44..d7e8/web>`.
75−
76−```
77−~your-urbit:dojo/=/sandbox/~2018.10.2..00.35.44..d7e8/web> +ls %
78−```
79−
80−To change back to our home directory, we use `=dir` without any path.
81−
82−```
83−~your-urbit:dojo/=/sandbox/~2018.10.2..00.35.44..d7e8/web> =dir
84−```
85−
86−Sync from your friend `~some-ship`'s `%experiment` desk to your
87−`%sandbox` desk:
88−
89−```
90−~your-urbit:dojo> |sync %sandbox ~some-ship %experiment
91−```
92−
93−If and when your sync is successful, you will receive a message:
94−
95−```
96−activated sync from %experiment on ~some-ship to %sandbox
97−```
98−
99−The ship that you sync from will get their own message indicating that you're
100−both connected as peers:
101−
102−```
103−; ~your-urbit is your neighbor.
104−```
105−
106−---
107−
108−## Manual
109−
110−### Paths
111−
112−A path in Clay is a list of URL-safe text, restricted to the characters
113−`[a z]`,`[0 9]`, `.`, `-`, `_`, and `~`. Formally this is a `(list knot)`,
114−meaning that each segment, delineated by `/`, is of the `knot` ASCII-text type.
115−In other words, paths are expressed as `/foo/bar/baz`. File extensions are
116−separated from file names with `/`, not `.`. Extensions are syntactically
117−identical to subdirectories, except that they must terminate the path.
118−
119−Paths begin with a piece of data called a `beak`. A beak is formally a
120−`(p=ship q=desk r=case)`; it has three components, and might look like
121−`/~dozbud-namsep/home/11`.
122−
123−The first `beak` component is `ship`, which is, as you might guess, the name of
124−an Urbit ship. The second component is `desk`, which is a workspace meant to
125−contain other directories; the default desk is `%home`. The third component is
126−`case`, which represents version information in various ways: date and time;
127−a version sequence, which is a value incremented by one whenever a file on the
128−given `desk` is modified; or an arbitrary plaintext label.
129−
130−You can find what your `beak` is at any given moment by
131−typing `%` in the Dojo and looking at the first three results.
132−
133−We use `beak`s because, unlike the current internet, the Urbit network uses a
134−global namespace. That means that a file named `example.hoon` in the `/gen`
135−directory on the `%home` desk of your ship `~lodleb-ritrul` would have a
136−universal address to anyone else on the network:
137−`/~lodleb-ritrul/home/186/gen/example/hoon`. That, of
138−course, doesn't mean that everyone on the network has privileges to access that
139−path.
140−
141−The structure that combines a `beak` with further path information is called a
142−`beam`.
143−
144−#### Relative paths
145−
146−The `%` command, which we gestured at in the above section, represents the
147−**relative path**, which is the path where you are currently working. If your
148−working directory is just your home desk, indicated by the
149−prompt `~your-planet:dojo>`, then running the command below will print your
150−working directory's `beam` information: your `beak`, and a `~` that represents
151−the empty list since no path is present.
152−
153−```
154−~your-urbit:dojo> %
155−```
156−
157−`%`s can be stacked to indicate one level further up in the hierarchy for each
158−additional `%`. Try the following command:
159−
160−```
161−~your-planet:dojo> %%%
162−```
163−
164−You'll probably notice that it only has your ship name and the empty list. The
165−two additional `%`s abandoned the `case` and the `desk` information by moving
166−up twice the hierarchy.
167−
168−There are no local relative paths. `/foo/bar` must be written as
169−`%/foo/bar`.
170−
171−#### Substitution
172−
173−You don't need to write out the explicit path every time you want to reference
174−somewhere outside of your working directory. You can substitute `=` for the
175−segments of a path.
176−
177−Recall that a full address in the the Urbit namespace is a `beam`: the
178−`/ship/desk/case/path`. If you've switched to another desk before, you're
179−already familiar with substitution syntax:
180−
181−```
182−~your-urbit:dojo> =dir /=sandbox=
183−```
184−
185−The above command substitutes uses substitution to use your current `ship` and
186−`case`; only the `desk` argument, which is located between the other two, is
187−given something new. Without substitution, you would need to write:
188−
189−```
190−~your-urbit:dojo> =dir /~your-urbit/home/85
191−```
192−
193−Substitutions work the same way in `beak`s (the `ship/desk/case` part) and
194−paths. For example, if you are in the `/gen` directory, you can reference a file
195−in the `/app` directory like below. (`+cat` displays the contents of a file).
196−
197−```
198−~your-urbit:dojo> =dir %/gen
199−~your-urbit:dojo/=/=/~2018.10.2..00.35.44..d7e8/gen> +cat /===/app/curl/hoon
200−```
201−
202−Note what was substituted out, and note that we don't need to separate `=` with
203−`/`.
204−
205−If we changed our working directory to something called `/gen/gmail`, we could
206−access a file called
207−
208−```
209−~your-urbit:dojo/=/=/~2018.10.2..00.35.44..d7e8/gen> =dir %/gmail
210−~your-urbit:dojo/=/=/~2018.10.2..00.35.44..d7e8/gen/gmail> +cat /===/app/=/split/hoon
211−```
212−
213−Because both paths share a directory named `/gmail` at the same position in the
214−address hierarchy -- which, if you recall, is just a `list` -- the above command
215−works!
216−
217−We can do the same thing between desks. If `%sandbox` has been merged with
218−`%home`, the following command will produce the same results as the above
219−command.
220−
221−```
222−~your-urbit:dojo/=/=/~2018.10.2..00.35.44..d7e8/gen/gmail> +cat /=sandbox=/app/=/split/hoon
223−```
224−
225−Most commonly this is used to avoid having to know the current revision
226−number in the `dojo`: `/~lodleb-ritrul/home/~2018.10.2..00.35.44..d7e8/gen/example/hoon`
227−
228−#### Changing directories
229−
230−Change the working directory with `=dir`. It's our equivalent of the Unix `cd`.
231−
232−For example, the syntax to navigate to `/home/gen/ask` is:
233−
234−```
235−~your-urbit:dojo> =dir /=home=/gen/ask
236−```
237−
238−This command will turn your prompt into something like this:
239−
240−```
241−~your-urbit:dojo/=/=/~2018.10.2..00.35.44..d7e8/gen/ask>
242−```
243−
244−Using `=dir` without anything else uses the null path, which returns you to
245−your home desk.
246−
247−```
248−~your-urbit:dojo/=/=/~2018.10.2..00.35.44..d7e8/gen/ask> =dir
249−```
250−
251−Your dojo prompt will turn back into `~your-urbit:dojo>`.
252−
253−To go up levels in the path hierarchy, recall the relative path expression
254−`%`. Stacking them represents another level higher in the hierarchy than
255−the current working directory for each `%` beyond the initial. The command below
256−brings you one level up:
257−
258−```
259−~your-urbit:dojo> =dir %/gen
260−~your-urbit:dojo/=/=/~2018.10.2..00.35.44..d7e8/gen> =dir %%
261−```
262−
263−### Revision-control
264−
265−#### Mount
266−
267−Syntax: `|mount /clay/path [Unix-name]`
268−
269−Mount the `clay-path` at the Unix mount point `Unix-name`.
270−
271−**Examples:**
272−
273−```
274−|mount %/web
275−```
276−
277−Mounts `%/web` to `/web` inside your pier directory.
278−
279−```
280−|mount %/gen generators
281−```
282−
283−Mounts `%/gen` to `/generators` inside your pier directory.
284−
285−#### Unmount
286−
287−```
288−|unmount [clay-path || Unix-name]
289−```
290−
291−Unmount the path or name from Unix.
292−
293−**Examples:**
294−
295−```
296−|unmount %/web
297−```
298−
299−Unmounts the path `%/web` from whatever name it was mounted as.
300−
301−```
302−|unmount %generators
303−```
304−
305−Unmounts the Unix path `/generators`.
306−
307−#### Merge
308−
309−```
310−|merge desk beak[, =gem strategy]
311−```
312−
313−Merges a `beak` into a `desk` using an optional merge `strategy`.
314−
315−A `beak` is a ship-desk-case triple, encoded as a
316−path(`/~dozbud/home/2`)
317−
318−**Examples:**
319−
320−```
321−|merge %home-work /=home=, =gem %fine
322−```
323−
324−Merge `/=home=` into `%home-work` using merge strategy `%fine`.
325−
326−```
327−|merge %examples ~wacbex-ribmex %examples
328−```
329−
330−Merge the `%examples` desk from `~waxbex-ribmex`
331−
332−#### Sync
333−
334−```
335−|sync desk plot [plot-desk]
336−```
337−
338−Subscribe to continuous updates from remote `plot` on local `desk`.
339−`plot-desk` can specify the remote `desk` name. When omitted it is
340−defaulted to being the same as `desk`. Non-comet urbits have
341−`|sync %home ~parent %kids` automatically set up (where `~parent` is the
342−planet that issued a moon, the star that issued a planet, or the galaxy
343−that issued a star).
344−
345−**Examples:**
346−
347−```
348−|sync %home-local ~dozbud %home
349−
350−|sync %home ~doznec
351−```
352−
353−#### Unsync
354−
355−```
356−|unsync desk plot [plot-desk]
357−```
358−
359−Unsubscribe from updates from remote `plot` on local `desk` with
360−optional `plot-desk`. Arguments must match original `|sync` command.
361−
362−Example:
363−
364−```
365−|unsync %home-local ~dozbud %home
366−```
367−
368−#### Label
369−
370−```
371−|label desk name`
372−```
373−
374−Label the current version of `desk` `name`.
375−
376−Example:
377−
378−```
379−|label %home release
380−```
381−
382−### Merge strategies
383−
384−`%init` - Used if it's the first commit to a desk. Also can be used to
385−"reinitialize" a desk -- revision numbers keep going up, but the new
386−revision isn't necessarily a descendent of the previously numbered
387−version, allowing merges to be rerun.
388−
389−`%this` - Keep what's in Bob's desk, but join the ancestry.
390−
391−`%that` - take what's in Alice's desk, but join the ancestry. This is
392−the reverse of `%this`. This is different from `%init` because the new
393−commit has both sides in its ancestry.
394−
395−`%fine` - "fast-forward" merge. This succeeds if and only if one head is in the
396−ancestry of the other.
397−
398−`%meet`, `%mate`, and `%meld` - find the most recent common ancestor to
399−use as our merge base.
400−
401−A `%meet` merge only succeeds if the changes from the merge base to
402−Alice's head (hereafter, "Alice's changes") are in different files than
403−Bob's changes. In this case, the parents are both Alice's and Bob's
404−heads, and the data is the merge base plus Alice's changed files plus
405−Bob's changed files.
406−
407−A `%mate` merge attempts to merge changes to the same file when both
408−Alice and Bob change it. If the merge is clean, we use it; otherwise, we
409−fail. A merge between different types of changes -- for example,
410−deleting a file vs changing it -- is always a conflict. If we succeed,
411−the parents are both Alice's and Bob's heads, and the data is the merge
412−base plus Alice's changed files plus Bob's changed files plus the merged
413−files.
414−
415−A `%meld` merge will succeed even if there are conflicts. If there are
416−conflicts in a file, then we use the merge base's version of that file,
417−and we produce a set of files with conflicts. The parents are both
418−Alice's and Bob's heads, and the data is the merge base plus Alice's
419−changed files plus Bob's changed files plus the successfully merged
420−files plus the merge base's version of the conflicting files.
421−
422−`%auto` - meta-strategy. Check to see if Bob's desk exists, and if it
423−doesn't we use an `%init` merge. Otherwise, we progressively try
424−`%fine`, `%meet`, and `%mate` until one succeeds. If none succeed, we
425−merge Bob's desk into a scratch desk. Then, we merge Alice's desk into
426−the scratch desk with the `%meld` option to force the merge. Finally, we
427−annotate any conflicts, if we know how.
428−
429−### Manipulation
430−
431−#### +cat
432−
433−Syntax: `+cat path [path ...]`
434−
435−Similar to Unix `cat`. `+cat` takes one or more `path`s, and prints their
436−contents. If that `path` is a file, the contents of the file is printed. If the
437−`path` terminates in a directory, the list of names at that path is produced.
438−
439−#### +ls
440−
441−Syntax: `+ls path`
442−
443−Similar to Unix `ls`. `+ls` takes a single `path`.
444−
445−Produces a list of names at the `path`.
446−
447−```
448−~your-urbit:dojo> +cat %/our/home/gen/curl/hoon
449−```
450−
451−#### |rm
452−
453−Syntax: `|rm path`
454−
455−Remove the data at `path`. `path` must be a path to actual node, not a
456−'directory'
457−
458−#### |cp
459−
460−Syntax: `|cp to from`
461−
462−Copy the file at `from` into the path `to`.
463−
464−#### |mv
465−
466−Syntax: `|mv to from`
467−
468−Move the file at `from` into the path `to`.
469−
470−In Clay, `|mv` is just a shorthand for `|cp` then `|rm`. The `|rm`
471−doesn't happen unless the `|cp` succeeds.
using/messaging.mddeleted−680
@@ -1,680 +0,0 @@
1−+++
2−title = "Messaging"
3−weight = 2
4−template = "doc.html"
5−+++
6−
7−Talk is the built-in frontend for the Urbit messaging and notifications
8−protocol, Hall. Today we use Hall to chat and coordinate, but it's really
9−a general purpose piece of infrastructure.
10−
11−For the time being come join us in `~dopzod/urbit-help` by using the
12−'quickstart' section below. `~dopzod` is the host ship, and `/urbit-help` is the
13−channel on that ship.
14−
15−Today, Hall is sort of like a distributed, encrypted Slack that can be
16−used from the CLI and the browser. There’s no central Hall server.
17−Any urbit can host one.
18−
19−Hall is a general purpose tool for both aggregating and publishing
20−streams of messages. Applications can use Hall as their transport
21−protocol, API connectors can push disparate data sources into Hall,
22−and so on. There are lots of things a distributed message protocol can
23−be used for that we haven't even thought of.
24−
25−Here we'll be discussing how to operate the default CLI frontend, Talk,
26−to send and receive messages. For a more in-depth look at Hall's internals,
27−take a look at its [documentation](@/docs/learn/arvo/hall.md).
28−
29−## Quickstart
30−
31−The most common uses of Talk right now are communicating over a public chat channel called `~dopzod/urbit-help` and sending direct messages. Everyone is more than welcome in `~dopzod/urbit-help`. It's the place to get help, ask questions and chat about Urbit in general.
32−
33−There are two ways of using Talk: from the terminal running the Urbit process, or through the Landscape web UI available at `http://localhost/~~/landscape`.
34−
35−If you're using Landscape for the first time, you'll need to enter a code to gain access. You can obtain this code by running `+code` from the Dojo.
36−
37−### Joining a Channel
38−
39−In Hall, a medium for a message is called a _circle_. There are four types of circles, but we for now we'll be dealing with the _channel_: a publicly accessible chatroom for general use. We'll discuss the other three kinds in the [manual](#manual) section.
40−
41−Let's join the `~dopzod/urbit-help` channel. Use `ctrl-x` to switch from Dojo to Talk.
42−
43−Then:
44−
45−```
46−~your-urbit:talk> ;join ~dopzod/urbit-help
47−```
48−
49−Scrolling down your terminal window, you'll probably see the playback of
50−previous `~dopzod/urbit-help` messages that you missed.
51−
52−Post a line to `~dopzod/urbit-help:`
53−
54−```
55−~your-urbit:talk= Hello, world!
56−```
57−
58−You'll see your message printed below messages from others that came before it:
59−
60−```
61−~your-urbit= Hello, world!
62−```
63−
64−### Subscribing to a Channel in Landscape
65−
66−In Landscape, you can always navigate to a channel by opening the menu, or using the shortcut `cmd-k`, then typing `go ~host-urbit/channel-name`. However, if you want to see messages in your inbox, you'll need to join from the Talk terminal.
67−
68−Again, that's:
69−
70−```
71−;join ~dopzod/urbit-help
72−```
73−
74−Now, navigate to `localhost/~~/landscape`. You should see recent messages under the "Recent" tab, and if you navigate to the "All" tab, you should see your subscription to `~dopzod/urbit-help` under "Chats".
75−
76−### Direct Messaging
77−
78−To send a direct message to someone, first set your audience:
79−
80−```
81−~your-urbit:talk= ;~talsur-todres
82−```
83−
84−You'll see your prompt change:
85−
86−```
87−~your-urbit:talk[~talsur-todres]
88−```
89−
90−Now you and `~talsur-todres` can exchange messages directly.
91−
92−```
93−~your-urbit:talk[~talsur-todres] Hey buddy!
94−```
95−
96−To set your audience back to `~dopzod/urbit-help`:
97−
98−```
99−~your-urbit:talk[~talsur-todres] ;~dopzod/urbit-help
100−```
101−
102−You'll see your prompt change back:
103−
104−```
105−~your-urbit:talk=
106−```
107−
108−You can also use the ASCII "glyph" assigned to your `~dopzod/urbit-help` circle as a shortcut:
109−
110−```
111−~your-urbit:talk[~talsur-todres] ;=
112−~your-urbit:talk=
113−```
114−
115−(Your ship may have a different glyph than `=` for your circle)
116−
117−Use `;leave` to unsubscribe from a channel:
118−
119−```
120−~your-urbit:talk= ;leave ~dopzod/urbit-help
121−```
122−
123−The web UI ships as compiled JavaScript on your urbit, but has its own
124−source repo [here](https://github.com/urbit/talk).
125−
126−Last, let's create a channel we can invite some friends to:
127−
128−```
129−~your-urbit:talk= ;create channel %my-channel 'Some description.'
130−```
131−
132−Now you can tell your friends to `;join ~your-urbit/my-channel`.
133−
134−---
135−
136−## Manual
137−
138−Hall's design is similar in spirit to
139−[NNTP](https://en.wikipedia.org/wiki/Network_News_Transfer_Protocol),
140−the underlying protocol for Usenet.
141−
142−Our design is pretty simple: Hall messages are called _posts_. Posts
143−go to _circles_. Any urbit can host or subscribe to any number of circles.
144−
145−There are four kinds of circles: a write-only `%mailbox` for direct
146−messages, an invite-only `%village` for private conversation, a read-only
147−`%journal` for curated content, and a public-access `%channel` for
148−general use.
149−
150−### Posts
151−
152−A post can be a variety of different data structures. Let's look at the
153−ones you can use from within Talk: lines, URLs, Hoon and replies.
154−
155−#### Lines
156−
157−A line is simply a string of text. Depending on the filtering rules set
158−by the circle's host, these may or may not include uppercase and Unicode
159−characters (see [filter](#filter)).
160−
161−If the line starts with `@`, it's an action (like `/me` in IRC).
162−
163−```
164−~your-urbit:talk= @sends a message.
165−```
166−
167−will print as
168−
169−```
170−~your-urbit sends a message.
171−```
172−
173−#### URLs
174−
175−A URL is any valid URL.
176−
177−```
178−~your-urbit:talk= https://example.com/
179−```
180−
181−#### Hoon
182−
183−You can use Talk to evaluate Hoon code and share the result with everyone in a
184−Hall circle. To do so, preface your Hoon with `#`.
185−
186−```
187−~your-urbit:talk= #(add 2 2)
188−```
189−
190−will print as
191−
192−```
193−~your-urbit# (add 2 2)
194−4
195−```
196−
197−#### Replies
198−
199−To indicate what you're saying is in direct response to a specific message, select the message (see Activating Lines below) and type your response.
200−
201−```
202−~some-urbit= Hello! How are you?
203−~your-urbit:talk= ; Well, thanks!
204−```
205−
206−will print as
207−
208−```
209−~your-urbit=^ Well, thanks!
210−```
211−
212−### Activating Lines
213−
214−A line number identifying the **subsequent** line is displayed every 5
215−lines.
216−
217−```
218−---------[0]
219−~your-urbit= This is my message.
220−~your-urbit= This is another message.
221−~your-urbit sends a message.
222−~your-urbit/ http://example.com/
223−~your-urbit# (add 2 2)
224− 4
225−---------[5]
226−~your-urbit=^ That's my message!
227−```
228−
229−You can use a line number to **activate** a line:
230−
231−```
232−~your-urbit:talk= ;5
233−```
234−
235−which prints the number, line identifier, timestamp, sender, audience,
236−and contents:
237−
238−```
239−? 0
240−0v3.hl51p.jhege.amhec.vb37r.3rejr at ~2016.6.24..04.48.21..a235
241−~your-urbit to ~another-urbit
242−in reply to: ~your-urbit:
243−> This is my message.
244−That's my message!
245−```
246−
247−If information got truncated — like what happens for long URLs or expressions,
248−or if there's additional information available — as is the case with
249−replies and attachments (e.g. stack traces) — activating the message will show
250−you all the details.
251−
252−You can also activate the most recent line with `;`, the second-most recent
253−with `;;`, and so on.
254−
255−### Creating and managing circles
256−
257−As mentioned before, any urbit can host any number of circles. Existing circles
258−can be deleted or modified with various commands. All commands in this section
259−shoild be sent from the `talk>` prompt.
260−
261−#### Create
262−
263−Syntax: `;create [type] %name 'description'`
264−
265−Creates and joins a circle, where `[type]` is any of the following:
266−- `channel`: public circle. Has a blacklist for write control.
267−- `village`: invite-only circle.
268−- `journal`: publicly readable, invite-only for writing.
269−- `mailbox`: publicly writeable, can only be read by its host.
270−
271−Let's create an example mailbox:
272−
273−```
274−sampel-palnet:talk> ;create mailbox %coolbox 'cool messages only'
275−```
276−
277−Something like this should print:
278−
279−```
280−--------------| ;create mailbox %coolbox 'cool messages only'
281−--------------| :: onn %coolbox
282−--------------| bound '>' {[hos=~sampel-palnet nom=%coolbox]}
283−--------------| %coolbox: see ~sampel-palnet hear
284−--------------| new > %coolbox
285−--------------| %coolbox: cap: cool messages only
286−--------------| %coolbox: fit: caps:Y unic:✔
287−```
288−
289−###### Delete
290−
291−Syntax: `;delete %name 'optional reason'`
292−
293−Deletes a circle. If a reason is specified, that gets sent to all
294−subscribers before the circle gets deleted.
295−
296−To delete our example above:
297−
298−```
299−sampel-palnet:talk> ;delete %coolbox 'people sent uncool messages'
300−```
301−
302−#### Change Description
303−
304−Syntax: `;depict %name 'description'`
305−
306−Changes the description of an existing circle `%name`.
307−
308−For example:
309−
310−```
311−sampel-palnet:talk> ;depict %coolbox 'cool messages only. NO EXCEPTIONS.'
312−```
313−
314−
315−#### Filter
316−
317−Syntax: `;filter %name [capitals] [unicode]`
318−
319−Configures the message filter for circle `%name`: whether to allow
320−capital and/or unicode characters. `y`/`&`/`true` for allowed,
321−`n`/`|`/`false` for disallowed.
322−
323−So, to allow capital letters and disallow unicode in the circle `%coolbox`:
324−
325−```
326−sampel-palnet:talk> ;filter %coolbox & |
327−```
328−or
329−```
330−sampel-palnet:talk> ;filter %coolbox y n
331−```
332−
333−And we get the output:
334−
335−```
336−--------------| ;filter %coolbox & |
337−--------------| %coolbox: fit: caps:Y unic:n
338−```
339−
340−#### Invite
341−
342−Syntax: `;invite %name ~someone`
343−
344−Invites someone into your circle `%name`. If they were previously banished,
345−removes them from the blacklist.
346−Can also invite multiple ships at once, `~comma, ~separated`.
347−
348−For example:
349−
350−```
351−~sampel-palnet:talk> ;invite %coolbox ~lodleb-ritrul
352−```
353−
354−#### Banish
355−
356−Syntax: `;banish %name ~someone`
357−
358−Removes someone from your circle `%name`. If they were previously invited,
359−removes them from the whitelist.
360−Can also banish multiple ships at once, `~comma, ~separated`.
361−
362−#### Source
363−
364−Syntax: `;source %name ~other/circle`
365−
366−Adds `~other/circle` as a source for circle `%name`. This causes all
367−messages sent to `~other/circle` to also appear in `%name`.
368−
369−For example:
370−
371−```
372−~sampel-palnet:talk> ;source %coolbox ~marzod/urbit-help
373−```
374−
375−#### Unsource
376−
377−Syntax: `;unsource %name ~other/circle`
378−
379−Removes `~other/circle` as a source for circle `%name`.
380−
381−For example:
382−
383−```
384−~sampel-palnet:talk> ;unsource %coolbox ~marzod/urbit-help
385−```
386−
387−### Circle Membership
388−
389−If you have joined a circle, you can make this information publicly
390−available to help others find that circle as well.
391−
392−#### Show Membership
393−
394−Syntax: `;show ~some/circle`
395−
396−Adds a circle to your public membership list on your Hall profile. Hall profiles
397−are not used yet.
398−
399−#### Hide Membership
400−
401−Syntax: `;hide ~some/circle`
402−
403−Removes a circle from your public membership list on your Hall profile. Hall
404−profiles are not used yet.
405−
406−### Status
407−
408−You'll see status notifications when people enter or leave circles you're
409−subscribed to.
410−
411−#### Notifications Off
412−
413−Syntax: `;set quiet`
414−
415−Turn off status (and config) notifications.
416−
417−#### Notifications On
418−
419−Syntax: `;unset quiet`
420−
421−Turn on status (and config) notifications.
422−
423−#### Who
424−
425−Syntax: `;who`
426−
427−List everyone in all your subscribed circles. Optionally specify a
428−specific circle to list members of just those: `;who ~some/circle`
429−
430−For example:
431−
432−```
433−~sampel-palnet:talk> ;who ~marzod/urbit-help
434−```
435−
436−#### Attend
437−
438−Syntax: `;attend ~some/circle [presence]`
439−
440−Manually set your presence to show up as one of the following. (In the
441−future, a sufficiently advanced client can automatically set these for
442−you.)
443−
444−- `talk` - typing
445−- `hear` - listening
446−- `idle` - inactive
447−- `gone` - not present
448−
449−For example:
450−
451−```
452−~sampel-palnet:talk> ;attend ~marzod/urbit-help idle
453−```
454−
455−#### Set Display Name
456−
457−Syntax: `;name ~some/circle 'my handle'`
458−
459−Set a handle ("name") for yourself in a specific circle. It will display
460−to users who have done `;set nicks`, but gets truncated if it's longer
461−than 14 characters.
462−
463−## Audience
464−
465−An audience consists of one or more messaging targets. These can be
466−circles or ships. (In the latter case, it's secretly the `~ship/inbox`
467−circle.)
468−
469−### Circle Glyphs
470−
471−Glyphs are found at the end of your prompt to as a quick indicator of where
472−your messages will be sent.
473−
474−Glyphs are assigned by circle hash out of the following list:
475−
476−```
477−> = + - } ) , . " ' ^ $ % & @
478−```
479−
480−Alphanumeric characters and `|#;:*~_` are reserved; all others (the
481−above list, and `\/!?({<`) can be manually assigned.
482−
483−For example, `-` the glyph at the end of the prompt below might indicates that
484−messages sent from this prompt will go to some circle with that glyph:
485−
486−```
487−~sampel-palnet:talk-
488−```
489−
490−To see what circle is bound to a glyph, use the `;what` command followed by the
491−glyph in question, or use `;what` without specifying a glyph to see all of your
492−subscriptions which are bound to glyphs. For example, to see `=`:
493−
494−```
495−~sampel-palnet:talk> ;what =
496−~dopzod/urbit-help
497−```
498−
499−To see all of your glyph-bound subscriptions:
500−
501−```
502−~sampel-palnet:talk> ;what
503−> ~paldev/numismatic-forum
504−. ~middev/ny-martians
505−= ~dopzod/urbit-help
506−```
507−
508−Not every audience has a glyph, however. When the audience doesn't have a glyph,
509−such as in the case of direct-messaging a ship, we see their name at the end of
510−the prompt instead. Here we're talking directly to `~dannum-mitryl`:
511−
512−```
513−~sampel-palnet:talk[~dannum-mitryl]
514−```
515−
516−#### Bind
517−
518−Syntax: `;bind [glyph] /circle-name`
519−
520−Assigns the chosen glyph to a circle owned by your ship.
521−
522−For example:
523−
524−```
525−~sampel-palnet:talk> ;bind + /my-circle
526−```
527−
528−#### Unbind
529−
530−Syntax: `;unbind [glyph] /circle-name`
531−
532−Unassigns the chosen glyph from a circle owned by your ship.
533−
534−For example:
535−
536−```
537−~sampel-palnet:talk> ;unbind + /my-circle
538−```
539−
540−### Prefixes
541−
542−Received posts are prefixed with a glyph to let you know what the
543−audience is. You can activate an individual post to see the full
544−audience.
545−
546−There are a few special-purpose glyphs:
547−
548−- `|` - Informational messages
549−- `:` - Posts directly to you
550−- `;` - Posts to you and others (a multiparty conversation)
551−- `*` - Posts to a complex audience that doesn't directly include you.
552−
553−
554−### Configuration
555−
556−#### Set Audience
557−
558−`;~ship/circle`
559−
560−Set audience to `~ship/circle`.
561−
562−#### Set Audience by Glyph
563−
564−Syntax: `;[glyph]`
565−
566−Set audience to the circle previously bound to the chosen glyph.
567−
568−#### Set Audience to Ship
569−
570−syntax `;~ship`
571−
572−Set audience to another ship.
573−
574−#### Set Audience to Own Circle
575−
576−Syntax: `;%circle`
577−
578−Set audience to a circle on your own ship
579−
580−#### Set Audience + Send Message
581−
582−Syntax: `;~dannum-mitryl this is a private message`
583−
584−Set the audience and send a post in the same line. This works for all of the
585−above audience commands.
586−
587−Your audience is configured with regard to the following rules (in order):
588−
589−- if you manually set the audience, that audience.
590−- if you activated a post, the post you activated.
591−- audience of the last post sent.
592−
593−### Local nicknames
594−
595−#### See Nicknames
596−
597−Syntax: `;nick`
598−
599−List all local nicknames.
600−
601−#### Find Nickname
602−
603−Syntax: `;nick ~some-urbit`
604−
605−Look up a nickname using the known ship-name.
606−
607−#### Reverse Find Nickname
608−
609−syntax: `;nick plato`
610−
611−Find a ship's name using its nickname.
612−
613−#### Set Nickname
614−
615−Syntax: `;nick ~some-urbit plato`
616−
617−Create a new nickname.
618−
619−#### Clear Nickname
620−
621−Syntax: `;nick ~some-urbit ~`
622−
623−Clear an assigned nickname.
624−
625−#### Display Nicks, Not Ship-Names
626−
627−Syntax: `;set nicks`
628−
629−Show nicknames instead of ship-names. If no local nickname is set, uses
630−that user's handle. If the user has no handle, just the urbit name.
631−
632−#### Display Ship-Names, Not Nicks
633−
634−Syntax: `;unset nicks`
635−
636−Show ship-names instead of nicknames.
637−
638−Nicknames and handles longer than 14 character will be truncated in
639−output. Nicknames are strictly local - like the names on entries in a
640−phonebook.
641−
642−### Miscellaneous configuration
643−
644−#### Show Timestamps
645−
646−Syntax: `;set showtime`
647−
648−Show the timestamp for each message.
649−
650−#### Hide Timestamps
651−
652−Syntax: `;unset showtime`
653−
654−Stop showing the timestamp for each message.
655−
656−#### Change Time Zone
657−
658−Syntax: `;set timezone [+/-][hours]`
659−
660−Adjust the display of the timestamps to a specific timezone. Relative to UTC.
661−
662−#### Sound Notification On
663−
664−Syntax: `;set notify`
665−
666−Emit a terminal bell sound if your six-syllable ship name is mentioned in
667−a message.
668−
669−#### Sound Notification Off
670−
671−Syntax `;unset notify`
672−
673−Do not notify when your ship name is mentioned.
674−
675−#### Set Width
676−
677−Syntax: `;set width [number]`
678−
679−Set the rendering width of `:talk` to a specific number of characters.
680−(Minimum of 30.)
using/operating-a-star.mddeleted−49
@@ -1,49 +0,0 @@
1−+++
2−title = "Operating a Star"
3−weight = 6
4−template = "doc.html"
5−+++
6−A _ship_ is an instance of the Arvo operating system that is used as a personal server on the Arvo network. Stars are a type of ship that act as infrastructure for the Arvo network. In the Arvo ship-hierarchy, stars are below galaxies and above planets.
7−
8−Parallel to the Arvo network is Azimuth, the Urbit identity system that uses the Ethereum blockchain. All ships must boot with a corresponding _point_ -- an Azimuth identity -- to use the Arvo network.
9−
10−Important star operations happen on both the Arvo side and the Azimuth side. On the Arvo side, these operations come in the form of Dojo commands. On the Azimuth side, operations happen by making changes to smart-contracts on the blockchain via a point.
11−
12−## Powers of a Star
13−
14−Stars are above planets in the network hierarchy in the sense that each star sponsors some number of planets: stars discover peers for planets, route packets for planets, provide DNS routing for planets, and push software updates to planets. A star that fulfills this is called the **sponsor** of planets that receive such services from the star; those planets, in turn, are called **dependents** of that star.
15−
16−Stars are also the "parents" of planets. A new planet comes into existence only when spawned by a parent star. A parent planet is the sponsor of its children planets by default. This can change if a planet chooses to find a new sponsor (see the "Escaping a Sponsor" section below).
17−
18−Planets must have a sponsor star to use most features of the Arvo network. A planet cannot boot without a sponsor, and cannot make new connections to peers as long as it is not connected to a sponsor. Planets without a sponsor will still be able to message discovered peers until any such peers change their IP addresses.
19−
20−## Responsibilities
21−
22−Like with real-life infrastructure, the operation of Arvo infrastructure comes with unique responsibilities. For reasons stated above, stars should be always be online on a reliable cloud service, such as Amazon Web Services or Google Cloud Platform. These systems have layers of redundancies that make them much more resilient than local machines, so stars hosted on the cloud are unlikely to leave their dependents in the dark.
23−
24−## Operations
25−
26−Below are some handy operations for the use and maintenance of your star.
27−
28−### arvo.network DNS Records
29−
30−We have a system that lets users request a domain name for their star under `arvo.network`, in the form of `shipname.arvo.network`, where `shipname` is their ship's name, so that it can be accessed remotely via our Landscape web interface. To find out how to do this, take a look at the [DNS Proxying](../dns-proxying) documentation.
31−
32−### Maintaining Connectivity
33−
34−Occasionally, your star might lose network connectivity due to a known timer issue or by falling out of sync with the Ethereum blockchain. When this happens, there are a few things to try:
35−
36−1. Enter the `|bonk` command in the Dojo to reset the timer and restore connectivity.
37−2. Run `|start %eth-manage`, then `:eth-manage %look-ethnode` to ensure that your star is synced up to the latest block.
38−
39−When in doubt, contact [support@urbit.org](mailto:support@urbit.org).
40−
41−### Escaping a Sponsor
42−
43−Planets are, of course, able to change sponsors. To do this, they must request that a different star takes them on as a dependent and that star must accept the request. Planets cannot emancipate themselves from a sponsor without having a new sponsor lined up.
44−
45−All of these actions happen on Azimuth. There will be Bridge functionality to handle these actions in the future, but for now users will need to interact directly with the contracts with MetaMask, through services such as [Etherscan.io](https://etherscan.io/address/ecliptic.eth#writeContract). A sketch of the process is listed below; for now, only the Ethereum-savvy should act on these steps.
46−
47−+ The planet calls the `escape` function in the Ecliptic contract and writes the resulting data to the blockchain.
48−+ If the chosen star wants to become the planet's sponsor, it calls the `adopt` function in the Ecliptic contract.
49−+ The Arvo network notices the change, and the operation is complete.
using/shell.mddeleted−440
@@ -1,440 +0,0 @@
1−+++
2−title = "Shell"
3−weight = 4
4−template = "doc.html"
5−+++
6−The Dojo is our shell; it processes system commands and returns output. It's a
7−good place to quickly experiment with Urbit. On the surface the Dojo is just a
8−Hoon REPL. On the inside, the Dojo is a system for operating on and transforming
9−data in Urbit.
10−
11−
12−## Quickstart
13−
14−You can use the Dojo to run arbitrary Hoon code, as well as non-Hoon system
15−commands.
16−
17−### Math
18−
19−Evaluate a Hoon expression (whitespace matters):
20−
21−```
22−~your-urbit:dojo> (add 2 2)
23−~your-urbit:dojo> %+ add 2 2
24−```
25−
26−Tall-form Hoon may require multiple lines:
27−
28−```
29−~your-urbit:dojo> %+ add
30−~your-urbit:dojo< 2
31−~your-urbit:dojo< 2
32−```
33−
34−Hoon uses something called [the subject](@/docs/learn/hoon/hoon-tutorial/the-subject-and-its-legs.md).
35−The Dojo has its own subject, and that's where Hoon's equivalent of variables,
36−called faces, are stored.
37−
38−Use `=var` to save faces to the Dojo subject.
39−
40−```
41−~your-urbit:dojo> =foo (add 2 2)
42−```
43−
44−Note, however, that `=var` is Dojo syntax, not Hoon syntax. You cannot bind a
45−face in a `.hoon` file in this way.
46−
47−### System Commands
48−
49−Use `=dir` to set the current working directory:
50−
51−```
52−~your-urbit:dojo> =dir %/web
53−```
54−
55−(`%` represents your current directory. For a complete explanation on urbit
56−paths, see the [filesystem section](@/docs/using/filesystem.md))
57−
58−Generators (files in `/gen`) are run with `+`:
59−
60−```
61−~your-urbit:dojo> +hello 'world'
62−```
63−
64−Save output to a file in `%clay` with `*`:
65−
66−```
67−~your-urbit:dojo> *some/file/path/hoon 'hello world'
68−```
69−
70−Run system commands from `:hood`, like `reload`, using `|`:
71−
72−```
73−~your-urbit:dojo> |reload %eyre
74−```
75−
76−## Generators
77−
78−Generators are short Hoon scripts, saved as `.hoon` files in the `/gen`
79−directory. Many Dojo commands exist in the form of generators. The syntax for
80−running a generator is `+genname` for a generator saved as `genname.hoon`.
81−
82−### +cat
83−
84−Accepts a path and displays the file. Similar to Unix `cat`.
85−
86−```
87−~your-urbit:dojo> +cat %/gen/curl/hoon
88−```
89−
90−### +code
91−
92−Generates a code that is used to remotely log into your ship. No
93−arguments.
94−
95−```
96−~your-urbit:dojo> +code
97−```
98−
99−### +curl
100−
101−Retrives data from a URL. Accepts a `tape`. Similar to Unix `curl`.
102−
103−```
104−~your-urbit:dojo> +curl "http://nyt.com"
105−```
106−
107−### +hello
108−
109−Just prints the argument. Accepts a `@ta`.
110−
111−```
112−~your-urbit:dojo> +hello 'mars'
113−```
114−
115−### +ls
116−
117−Similar to Unix `ls`. Accepts a path.
118−
119−```
120−~your-urbit:dojo> +ls %/web
121−~your-urbit:dojo> +ls /~talsur-todres/home/2/web/notes
122−```
123−
124−### +moon
125−
126−Generates a random moon from a planet. No arguments.
127−
128−```
129−~your-urbit:dojo> +moon
130−```
131−
132−### +solid
133−
134−Compile the current state of the kernel and output a
135−noun. Usually downloaded to a file in unix. No arguments.
136−
137−```
138−~your-urbit:dojo> .urbit/pill +solid
139−```
140−
141−### +test
142−
143−Testrunner. Can test multiple generators at once, conventionally ones
144−in the `/test` folder. Takes a path.
145−
146−```
147−~your-urbit:dojo> +test /lib
148−```
149−
150−### +ticket
151−
152−Generate a ticket for an urbit ship. Takes an urbit name (`@p`).
153−
154−
155−```
156−~your-urbit:dojo> +ticket ~talsur-todres-your-urbit
157−```
158−
159−### +tree
160−
161−Generate a recursive directory listing. Takes a path.
162−
163−```
164−~your-urbit:dojo> +tree %/web
165−```
166−
167−## Hood
168−
169−The hood is the system daemon. See `gen/hood` and `app/hood`.
170−
171−`|hi` - Sends a direct message. Sort of like Unix `write`. Accepts
172−an urbit name (`@p`) and a string (`tape`, which is text wrapped with double-quotes).
173−
174−```
175−~your-urbit:dojo> |hi ~binzod "you there?"
176−```
177−
178−`|link` / `|unlink` - Link / unlink a remote app. Accepts an
179−Urbit name and an app name.
180−
181−```
182−~your-urbit:dojo> |link ~talsur-todres %octo
183−```
184−
185−`|mass` - Prints the current memory usage of all the kernel modules.
186−No arguments.
187−
188−```
189−~your-urbit:dojo> |mass
190−```
191−
192−`|reload` - Reloads a kernel module (vane) from source. Accepts any
193−number of vane names.
194−
195−```
196−~your-urbit:dojo> |reload %clay %eyre
197−```
198−
199−`|reset` - Reloads `hoon.hoon` and all modules. No arguments.
200−
201−```
202−~your-urbit:dojo> |reset
203−```
204−
205−`|start` - Starts an app. Accepts an app name.
206−
207−```
208−~your-urbit:dojo> |start %curl
209−```
210−
211−---
212−
213−## Manual
214−
215−## Sources and sinks
216−
217−A Dojo command is either a **source** or a **sink**. A source is just something
218−that can be printed to your console or the result of some computation. A
219−sink is an **effect**: a change to the filesystem, a network message, a
220−change to your environment, or typed message to an app.
221−
222−Sources can be chained together, but we can only produce one effect per
223−command.
224−
225−### Sinks
226−
227−#### `=` - Set variable
228−
229−Set any environment variable:
230−
231−```
232−~your-urbit:dojo> =foo 42
233−~your-urbit:dojo> (add 2 foo)
234−
235−44
236−```
237−
238−Make sure to note that `=var` is Dojo syntax, not Hoon syntax. You cannot bind a
239−variable in a `.hoon` file in this way.
240−
241−#### Special Variables
242−
243−There are a few special variables that the Dojo maintains.
244−
245−#### `:` - Send to app
246−
247−`:app` goes to a local `app`, `:~ship/app` goes to the `app` on `~ship`.
248−
249−Send a `helm-hi` message to `hood`:
250−
251−```
252−~your-urbit:dojo> :hood &helm-hi 'hi'
253−```
254−
255−Apps usually expect marked data, so `&` is often used here.
256−
257−#### `*` - Save in `%clay`
258−
259−Save a new `.udon` ([Udon](@/docs/using/sail-and-udon.md)) file in `web`:
260−
261−```
262−~your-urbit:dojo> *%/web/foo/udon '# hello'
263−```
264−
265−The last component of the path is expected to be the mark (or mime
266−type).
267−
268−#### `.` - Export to Unix
269−
270−Export a noun to Unix with `.`:
271−
272−```
273−~your-urbit:dojo> .foo/bar/baz (add 2 2)
274−```
275−
276−Which creates a file at `pier/.urb/put/foo/bar.baz`.
277−
278−This is very often used with `+solid`:
279−
280−```
281−~your-urbit:dojo> .urbit/pill +solid
282−```
283−
284−Which outputs a new `urbit.pill` to `pier/.urb/put/urbit.pill`
285−
286−### Sources
287−
288−#### `&` - Mark conversion
289−
290−Convert between marks using `&`, with the destination mark first. You can stack multiple mark conversions together, and some marks can only be converted to specific other marks. In this example, [Udon](@/docs/using/sail-and-udon.md#udon) is converted to `&hymn` (a mark which supplies the `html`, `head`, `body` and closing tags) first, before being converted to HTML:
291−
292−```
293−~your-urbit:dojo>&html &hymn &udon ';h1#hello: hello'
294−'<html><head></head><body><h1 id="hello">hello</h1></body></html>'
295−```
296−
297−Performing a conversion straight from Udon to the `&hymn` mark reveals a bit more about its mark conversion:
298−
299−```
300−~your-urbit:dojo>&hymn &udon ';h1#hello: hello'
301−[[%html ~] [[%head ~] ~] [[%body ~] [g=[n=%h1 a=~[[n=%id v="hello"]]] c=~[[g=[n=%$ a=~[[n=%$ v="hello"]]] c=~]]] ~] ~]
302−```
303−
304−As does converting straight from Udon to HTML:
305−
306−```
307−~your-urbit:dojo>&html &udon ';h1#hello: hello'
308−';h1#hello: hello'
309−```
310−
311−#### `_` - Run a function
312−
313−Use `_` to run a gate (or function):
314−
315−Write an arbitrary function and pass data to it:
316−
317−```
318−~your-urbit:dojo> _|=([a=@] (mul a 3)) 3
319−9
320−```
321−
322−Use a function to get the status code from an http request:
323−
324−```
325−~your-urbit:dojo> _|=([p=@ud q=* r=*] p) +http://google.com
326−301
327−```
328−
329−#### `+` `-` - HTTP requests
330−
331−`+http[s]://example.com` - sends a GET request
332−
333−`+http[s]://example.com &json [%s 'hi']` - sends a POST request with the
334−JSON `"hi"` in the body.
335−
336−`-http[s]://example.com &json [%s 'hi']` - sends a PUT request with the
337−JSON `"hi"` in the body.
338−
339−Note that the first of these is a source while the last two are sinks.
340−
341−#### `+` - Generators
342−
343−Generators are simple Hoon scripts loaded from the filesystem. They live
344−in `gen/`.
345−
346−An example of a generator that is built into your urbit is `+code`. It produces
347−the code needed to log into your ship remotely.
348−
349−```
350−~your-urbit:dojo> +code
351−fintyr-haldet-fassev-solhex
352−```
353−
354−### Variables
355−
356−You can use `=` to set an environment variable in Dojo, but there are
357−a few reserved names that have special uses.
358−
359−#### dir
360−
361−Current working `%clay` desk and revision. Read / write.
362−
363−**Examples:**
364−
365−```
366−~your-urbit:dojo> =dir %/web
367−~your-urbit:dojo> +ls %
368−404/hoon docs/ dojo/hoon lib/ listen/hoon md static/udon talk/ testing/udon tree/main/ unmark/ womb/
369−```
370−
371−#### lib
372−
373−Current set of libraries (`/lib`) in your environment. Can be set
374−with `/+`. Read / write.
375−
376−**Examples:**
377−
378−```
379−~your-urbit:dojo> /+ number-to-words
380−```
381−Now we can use arms from lib/number-to-words.hoon
382−```
383−~your-urbit:dojo> (to-words:eng-us:number-to-words 123.456)
384−```
385−
386−#### sur
387−
388−Current set of structures (`/sur`) in your environment. Can be set
389−with `/-`. Read / write.
390−
391−**Examples:**
392−
393−```
394−~your-urbit:dojo> /- sole
395−```
396−Now we can use arms in sur/sole.hoon.
397−```
398−~your-urbit:dojo> `sole-effect:sole`[%bel ~]
399−```
400−
401−#### now
402−
403−The current (128-bit `@da`) time. Read-only.
404−
405−**Example:**
406−
407−```
408−~your-urbit:dojo> now
409−~2016.3.21..21.10.57..429a
410−```
411−
412−#### our
413−
414−The current urbit ship. Read-only.
415−
416−**Example:**
417−
418−```
419−~your-urbit:dojo> our
420−~your-urbit
421−```
422−
423−#### eny
424−
425−512 bits of entropy. Read-only.
426−
427−**Example:**
428−
429−```
430−~your-urbit:dojo> eny
431−\/0vnt.d474o.gpahj.jcf3o.448fh.2lamb.82ljm.8ol8u.b02vi.mrvvp.b7et2.knb7m.l8he\/
432− 8.8qb9s.drm36.77n9b.a0qst.30g03.l5lb5.nvsbc.v39tn
433−\/
434−```
435−
436−## Troubleshooting
437−
438−If you encounter `%dy-edit-busy` while entering commands, it is
439−because your Dojo is blocked on a timer or an HTTP request. Type backspace
440−and your Dojo will end the blocked command.
learn/vere/_index.md → vere/_index.mdrenamed

The content is the same.

learn/vere/api.md → vere/api.mdrenamed

The content is the same.

learn/vere/c.md → vere/c.mdrenamed

The content is the same.

learn/vere/jetting.md → vere/jetting.mdrenamed

The content is the same.

learn/vere/nouns.md → vere/nouns.mdrenamed

The content is the same.

learn/vere/runtime.md → vere/runtime.mdrenamed

The content is the same.