on master help sign in
Merge branch 'main' of github.com:g-a-v-i-n/urbit.org2 into main
commitf3dbb84daece51211d24b7eafab1d8eb2b1283f5 authorGavin Atkinson <gvnatknsn@protonmail.com> dateTue 15 Jun 2021, 16:02 (5 years ago) parentc08330dd6175ab
26 files changed+163−159
.gitmodules+3 content/blog/iot.md+14−14 content/blog/rollups.md+17−17 content/community/community-grants.md+1−1 content/community/governance.md+1−1 content/docs+1 content/faq.md+39−39 content/getting-started/_index.md+2−2 content/getting-started/cli.md+5−5 content/getting-started/planet.md+9−9 content/reset.md+3−3 content/understanding-urbit/interface.md+1−1 content/understanding-urbit/people-history.md+1−1 content/using/_index.md+6−6 content/using/id/_index.md+7−7 content/using/id/creating-an-invite-pool.md+2−2 content/using/id/guide-to-breaches.md+11−11 content/using/id/using-bridge.md+5−5 content/using/os/_index.md+6−6 content/using/os/filesystem.md+4−4 content/using/os/getting-started.md+5−5 content/using/os/shell.md+2−2 content/using/os/ship-troubleshooting.md+3−3 content/using/os/stars-and-galaxies.md+3−3 content/using/running/_index.md+2−2 content/using/running/hosting.md+10−10
.gitmodulesnew file+3
@@ -0,0 +1,3 @@
1+[submodule "content/docs"]
2+ path = content/docs
3+ url = git@github.com:matildepark/docs.git
content/blog/iot.md+14−14
@@ -14,10 +14,10 @@ image = "https://media.urbit.org/site/posts/essays/phobos.jpeg"
1414
1515<br>
1616
17−Each of the ~4B 32-or-fewer-bit or [Azimuth](@/docs/glossary/azimuth.md)
18−identities, namely [planets](@/docs/glossary/planet.md),
19−[stars](@/docs/glossary/star.md), and [galaxies](@/docs/glossary/galaxy.md), may
20−spawn ~4B 64-bit child identities known as [moons](@/docs/glossary/moon.md).
17+Each of the ~4B 32-or-fewer-bit or [Azimuth](/docs/glossary/azimuth)
18+identities, namely [planets](/docs/glossary/planet),
19+[stars](/docs/glossary/star), and [galaxies](/docs/glossary/galaxy), may
20+spawn ~4B 64-bit child identities known as [moons](/docs/glossary/moon).
2121Moons are the undeveloped wild outback of Urbit, with a story waiting to be told
2222that promises to be as enormous in scale as the cloud personal computing story
2323told by planets, and possibly even more so.
@@ -37,7 +37,7 @@ settings, especially with respect to agriculture, and how they may manifest as
3737the workhorse collection unit of decentralized data markets.
3838
3939For those unfamiliar, moons differ from all other
40−[ships](@/docs/glossary/ship.md) in that they are not independent identities
40+[ships](/docs/glossary/ship) in that they are not independent identities
4141with total sovereignty over their data and keys. Instead, their cryptographic
4242keys are issued and controlled by their parent identity. The relationship
4343between the keys of a parent ship and its moons are analogous to the
@@ -114,7 +114,7 @@ In 2021, moons are mostly unused on Urbit. There's a smattering of minor use
114114cases which we'll describe here, but they represent only a tiny fraction of
115115their ultimate potential.
116116
117−Tlon recently launched a survey bot called [Eliza](@/blog/eliza.md), which was
117+Tlon recently launched a survey bot called [Eliza](/blog/eliza), which was
118118initially a comet. We frequently got questions on whether Eliza was actually
119119Tlon's bot, because it could just as easily be a malicious actor posing as Tlon.
120120We soon plan to relaunch Eliza as a moon of `~zod`, which is the most
@@ -143,7 +143,7 @@ to maintain a more performant planet.
143143As we currently lack a real system for 3rd party software distribution (though
144144see this recent [developer call](https://youtu.be/XwICC6Its1E) on a solution in
145145progress), one stopgap has been to download software by syncing a foreign
146−[desk](@/docs/glossary/desk.md) to your ship. This is risky, as buggy software
146+[desk](/docs/glossary/desk) to your ship. This is risky, as buggy software
147147may make break your ship and make it difficult to get running properly again.
148148For this reason, testing new software on the livenet is frequently performed on
149149moons, so as not to risk the parent ship if something were to go wrong.
@@ -228,8 +228,8 @@ Here, the hub or controller referred to would be your planet.
228228Urbit has many other features that make it well-suited for IoT, above and beyond
229229eliminating the SaaS model and providing self-authenticating identities. Many of
230230these additional advantages derive from the fact that Urbit is a [solid state
231−interpreter](@/docs/arvo/overview.md#solid-state-interpreter) and that
232−[Ames](@/docs/glossary/ames.md) is a network of solid-state interpreters
231+interpreter](/docs/arvo/overview#solid-state-interpreter) and that
232+[Ames](/docs/glossary/ames) is a network of solid-state interpreters
233233equipped with cryptographic identity. We explore this in the next section.
234234
235235### Future lunar cosmotechnics
@@ -253,7 +253,7 @@ In order to respect the reader's time, I'm narrowing our scope to a particular
253253topic: the agriculture industry. I'm also assuming a future with specialized and
254254increasingly small hardware to run Urbit. Right now, a 4 GB Raspberry Pi is the
255255standard for "small Urbit". If someday there are CPUs specifically designed for
256−running [Nock](@/docs/glossary/nock.md), one could imagine going much smaller.
256+running [Nock](/docs/glossary/nock), one could imagine going much smaller.
257257Ultimately, I'm going to assume that there will someday be [solid-state
258258interpreter](#ssi) microcontrollers - so the inclusion of Urbit on a device may
259259require nothing more than a couple [surface-mount
@@ -272,7 +272,7 @@ industrial scale, and show how computerized and mechanized workflows add to the
272272amazing productivity of modern farms and demonstrate that individual-sized
273273inputs are able to create industrial-sized outputs. I predict that the set of
274274trades for which this dynamic holds will only increase over time.
275−
275+
276276Agricultural automation has been a primary engine for the growth of
277277civilization, but it has been hampered by the downsides of IoT elaborated in the
278278previous section. One bellwether of this dynamic is the right to repair one's
@@ -325,8 +325,8 @@ properties are of great benefit in an industrial IoT context such as
325325agriculture. We'd also like to predict that Urbit will not be the only SSI.
326326Other sorts of SSI's specialized to various tasks may one day roam the planet,
327327and these may be better suited for particular IoT tasks than
328−[Arvo](@/docs/glossary/arvo.md). However, this article will be couched in terms
329−of SSIs communicating with an [Ames](@/docs/glossary/ames.md)-like networking
328+[Arvo](/docs/glossary/arvo). However, this article will be couched in terms
329+of SSIs communicating with an [Ames](/docs/glossary/ames)-like networking
330330protocol and Urbit ID-style cryptographic identity, rather than Urbit in
331331particular.
332332
@@ -350,7 +350,7 @@ deterministic at the CPU level, interruptions to power can result in an
350350undefined semantic state and result in the random erasure of half of its brain.
351351This determinism is what begets ease of maintainability of Urbit—problems
352352generally only need to be solved once by experts and the solution propagates to
353−the rest of the network via [OTA updates](@/docs/glossary/ota-updates.md). We
353+the rest of the network via [OTA updates](/docs/glossary/ota-updates). We
354354addressed this maintenance issue previously—we only remark now that this
355355property is derived from being a SSI, rather than something particular only to
356356Arvo or Urbit. When one has hundreds or thousands of devices to manage, the
content/blog/rollups.md+17−17
@@ -15,14 +15,14 @@ gotten _expensive_. There are a large quantity of
1515complicated and clever techniques each with their own trade-offs
1616that are collectively referred to as "layer 2 solutions" (see [further
1717resources](#resources) for more information about these). This is in contrast to
18−the base computational layer of Ethereum called "layer 1", which is what constitutes most Ethereum usage and where [Urbit ID](@/docs/glossary/azimuth.md)’s smart contracts currently exist.
18+the base computational layer of Ethereum called "layer 1", which is what constitutes most Ethereum usage and where [Urbit ID](/docs/glossary/azimuth)’s smart contracts currently exist.
1919
20−Tlon has always covered gas costs for Urbit ID up to a set limit, and this was easy a couple of years ago when the cost of transactions required to get a [planet](@/docs/glossary/planet.md) up and running came out to less than a dollar. Unfortunately the ongoing Ethereum gas crisis, along with the rising price of Ethereum itself, has made this impossible. We’ve seen gas costs to set up a planet as high as several hundred US dollars at time of writing!
20+Tlon has always covered gas costs for Urbit ID up to a set limit, and this was easy a couple of years ago when the cost of transactions required to get a [planet](/docs/glossary/planet) up and running came out to less than a dollar. Unfortunately the ongoing Ethereum gas crisis, along with the rising price of Ethereum itself, has made this impossible. We’ve seen gas costs to set up a planet as high as several hundred US dollars at time of writing!
2121
2222In response to the gas crisis, Tlon has spent the last several months developing
2323a simple, in-house layer 2 solution which we anticipate will reduce typical gas costs by 65x or more.
2424
25−This post is primarily a short non-technical explainer of the end-user experience of our solution aimed at planet and [star](@/docs/glossary/star.md) owners and those in the market for one, as well as a status update on where we're at in development. At [the end](#technical) we give some minimal technical details and resources to help you dig deeper should you wish.
25+This post is primarily a short non-technical explainer of the end-user experience of our solution aimed at planet and [star](/docs/glossary/star) owners and those in the market for one, as well as a status update on where we're at in development. At [the end](#technical) we give some minimal technical details and resources to help you dig deeper should you wish.
2626This is also primarily aimed at those who currently self-host or plan to self-host their
2727urbit. For anybody utilizing a hosted service, this matter will all be handled
2828by your provider. There is a [separate section](#stars) addressed specifically at star owners, and another [section](#rollers) for those who wish to set up their urbit to accept and submit layer 2 transactions. We’d like to emphasize that this system is 100% opt-in—if you are satisfied with the current experience of Urbit ID, then nothing changes for you whatsoever.
@@ -37,7 +37,7 @@ of the back-end is approaching completion, and we are confident in a release bef
3737Our layer 2 solution, designed primarily by Tlon lead engineer `~wicdev-wisryt`,
3838is known as "naive rollups" and we will be using this term interchangeably with
3939"layer 2"—though it is important to note that there are many layer 2 solutions
40−utilized by projects other than Urbit. As we're avoiding technicality here, we’re focusing primarily on the advantages and disadvantages of utilizing our layer 2 solution, and how that affects the management of your [ship](@/docs/glossary/ship.md).
40+utilized by projects other than Urbit. As we're avoiding technicality here, we’re focusing primarily on the advantages and disadvantages of utilizing our layer 2 solution, and how that affects the management of your [ship](/docs/glossary/ship).
4141
4242Very briefly, a rollup is a way to combine many transactions into one, and we
4343are building infrastructure so that any Urbit ship may be utilized as a "roller". A
@@ -69,7 +69,7 @@ hours or even days for your transaction to clear. But the way we are saving on
6969gas is essentially by "bundling" or "rolling up" many transactions into one, and
7070submitting them as a single transaction. The more transactions in the rollup,
7171the better the savings. This bundling is not the only factor at play here
72−though—costs are reduced other ways, but this is a technical detail
72+though—costs are reduced other ways, but this is a technical detail
7373[discussed later in this post](#technical). It is possible to use layer 2 to submit single
7474transactions (and this will still save on gas costs!), so utilization of layer 2
7575should not incur any delay over layer 1 when utilized in this fashion.
@@ -82,7 +82,7 @@ view Urbit ID as "digital land", and a few hours to acquire land, or waiting for
8282your new personal computer to be delivered, is still lightning fast in
8383comparison to the real world. We also have ideas on methods that will allow you to get on the network before the transfer has been confirmed, but that is outside of the scope of this article.
8484
85−Our layer 2 preserves the main value proposition of Urbit ID, which is that your ship
85+Our layer 2 preserves the main value proposition of Urbit ID, which is that your ship
8686belongs to you forever, and that this is assured by very strong cryptographic methods and
8787game-theoretic arguments comparable to the ones that exist on layer 1. We
8888consider this principle to be uncompromisable, and maintaining ultimate
@@ -94,8 +94,8 @@ goes into greater detail in the [resources](#resources).
9494
9595The primary way one manages their Urbit ID, namely performing tasks such as
9696transferring ships, setting networking keys, or setting
97−[proxies](@/docs/glossary/proxies.md), is with a web interface called
98−[Bridge](@/docs/glossary/bridge.md) found at
97+[proxies](/docs/glossary/proxies), is with a web interface called
98+[Bridge](/docs/glossary/bridge) found at
9999[bridge.urbit.org](https://bridge.urbit.org). If you already own a planet,
100100you've probably used Bridge before - perhaps only a single time.
101101
@@ -109,7 +109,7 @@ choice of a roller to submit transactions to. Tlon's will be free for ordinary,
109109You could use your own ship for a fast single transaction for a little more gas. We expect that planet markets and stars may wish to set up their own rollers as well.
110110
111111Every planet has a sponsor star, which distributes [OTA
112−updates](@/docs/glossary/ota-updates.md) to their sponsored planets and assists with peer discovery. Both layer 1 and layer 2 planets will be able to be
112+updates](/docs/glossary/ota-updates) to their sponsored planets and assists with peer discovery. Both layer 1 and layer 2 planets will be able to be
113113sponsored by either layer 1 or layer 2 stars, meaning that nothing will change
114114in terms of how sponsorship works.
115115
@@ -123,9 +123,9 @@ And that's it! If you'd like to know how things will be changing for
123123### Changes to stars {#stars}
124124
125125Both planets and stars will be able to move to layer 2.
126−[Galaxies](@/docs/glossary/galaxy.md) must remain on layer 1 for technical
127−reasons, and [moons](@/docs/glossary/moon.md) and
128−[comets](@/docs/glossary/comet.md) never interacted with Ethereum anyways, so
126+[Galaxies](/docs/glossary/galaxy) must remain on layer 1 for technical
127+reasons, and [moons](/docs/glossary/moon) and
128+[comets](/docs/glossary/comet) never interacted with Ethereum anyways, so
129129they are completely out of the picture.
130130
131131Stars will be able to remain on layer 1 with no action required. For star owners
@@ -171,7 +171,7 @@ these factors to be included in the roller documentation.
171171
172172### Changes to Azimuth
173173
174−[Azimuth](@/docs/glossary/azimuth.md) is the set of Ethereum smart contracts
174+[Azimuth](/docs/glossary/azimuth) is the set of Ethereum smart contracts
175175governing Urbit ID. They will require a few changes to accommodate the new
176176system. Some of this has been implicit above, but to be clear, we will only be
177177making a couple minor alterations:
@@ -191,20 +191,20 @@ Changes to the state of Urbit ID on layer 1 works as follows:
191191 2. The EVM calculates the resulting state transition and checks its validity, then updates the state.
192192 3. Your urbit downloads the new state from an Ethereum node.
193193 4. Your urbit makes the final decision on whether the new state is valid.
194−
194+
195195In practice, the fourth step is never used in layer 1. The primary change to our
196196security model is that we are cutting out step 2 and beefing up step 4. Your
197197ship will now perform validation of the transactions posted to the Ethereum
198198blockchain, rather than the EVM.
199199
200−Since [Urbit OS](@/docs/glossary/arvo.md) is deterministic, and Hoon has some nice formal
201−properties, it turns out to be a great language for writing smart contracts. Thus we are effectively swapping the Ethereum smart contract with a “Hoon smart contract” run locally on your ship.
200+Since [Urbit OS](/docs/glossary/arvo) is deterministic, and Hoon has some nice formal
201+properties, it turns out to be a great language for writing smart contracts. Thus we are effectively swapping the Ethereum smart contract with a “Hoon smart contract” run locally on your ship.
202202
203203#### Further Resources {#resources}
204204
205205We want to keep this post brief and non-technical, so that's all we'll say about
206206it for now. To find out more, you have a few directions to go on. We held a
207−[Developer Call](@/events/2021-03-04-developer-call-scaling-azimuth.md) where
207+[Developer Call](/events/2021-03-04-developer-call-scaling-azimuth) where
208208`~wicdev-wisryt` outlines the design in much more technical detail, and also
209209explains why we decided to utilize our own design rather than other known layer
2102102 solutions such as [Optimistic
content/community/community-grants.md+1−1
@@ -7,7 +7,7 @@ hideprevious = "true"
77hidenext = "true"
88+++
99
10−Interested in getting your community on Urbit? We are currently accepting applications for select groups to get started on Urbit together using an [invite pool](@/using/id/creating-an-invite-pool.md).
10+Interested in getting your community on Urbit? We are currently accepting applications for select groups to get started on Urbit together using an [invite pool](/using/id/creating-an-invite-pool).
1111
1212To get started, fill out the application below. Any information you share will be held privately, and only for the purpose of consideration for the grant.
1313
content/community/governance.md+1−1
@@ -20,6 +20,6 @@ For off-chain process around proposals, as suggested by core developers, please
2020
2121The group of core developers manages Urbit’s [GitHub repository](https://github.com/urbit/), which controls Arvo, Urbit’s operating system. Changes and upgrades are decided upon by consensus.
2222
23−You can participate in the governance of the senate by acquiring a galaxy. If you would like to be involved with the governance of Arvo, check out our [developer guide](@/docs/development/develop.md) to learn how you can contribute to core development.
23+You can participate in the governance of the senate by acquiring a galaxy. If you would like to be involved with the governance of Arvo, check out our [developer guide](/docs/development/develop) to learn how you can contribute to core development.
2424
2525
content/docsnew file+1

Submodule changed.

content/faq.md+39−39
@@ -19,7 +19,7 @@ The connected world anticipated by Urbit is a much friendlier one, much like the
1919
2020[Urbit ID](#what-is-urbit-id) / [Azimuth](#what-is-azimuth), Urbit's identity layer, is live on the Ethereum blockchain and has been audited by Open Zeppelin, Blockchain at Berkeley, and Bloctrax.
2121
22−In late 2020, Urbit's [Ames](@/docs/glossary/ames.md) networking protocol was audited by [Leviathan Security](https://www.leviathansecurity.com/). You can read about this milestone [here](@/blog/security-and-continuity.md).
22+In late 2020, Urbit's [Ames](/docs/glossary/ames) networking protocol was audited by [Leviathan Security](https://www.leviathansecurity.com/). You can read about this milestone [here](/blog/security-and-continuity).
2323
2424Looking to the future, Tlon has plans to begin working to make Urbit secure against attacks from quantum computers in 2021.
2525
@@ -35,7 +35,7 @@ We encourage outside contributors to become a part of the project. The best way
3535
3636### What is Urbit ID? {#what-is-urbit-id}
3737
38−Urbit ID is the identity system utilized by Urbit, which associates to each [ship](@/docs/glossary/ship.md) a public and private key used to establish encrypted connections between one another and to guard private data. For [planets](@/docs/glossary/planet.md), [stars](@/docs/glossary/star.md), and [galaxies](@/docs/glossary/galaxy.md), this is achieved with a set of Ethereum smart contracts called [Azimuth](#what-is-azimuth). Keys for [moons](@/docs/glossary/moon.md) and [comets](@/docs/glossary/comet.md) are handled within Urbit.
38+Urbit ID is the identity system utilized by Urbit, which associates to each [ship](/docs/glossary/ship) a public and private key used to establish encrypted connections between one another and to guard private data. For [planets](/docs/glossary/planet), [stars](/docs/glossary/star), and [galaxies](/docs/glossary/galaxy), this is achieved with a set of Ethereum smart contracts called [Azimuth](#what-is-azimuth). Keys for [moons](/docs/glossary/moon) and [comets](/docs/glossary/comet) are handled within Urbit.
3939
4040### What are stars, galaxies, and planets? {#stars-galaxies-planets}
4141
@@ -45,20 +45,20 @@ Planets are intended for everyday use by individuals, and there are 4.3 billion
4545
4646### Why is is currently expensive to acquire a planet? {#gas-prices}
4747
48−For the latest on this topic, see our recent blog post: [The Gang Solves the Gas Crisis](@/blog/rollups.md).
48+For the latest on this topic, see our recent blog post: [The Gang Solves the Gas Crisis](/blog/rollups).
4949
5050As of early 2021, if you try to acquire a planet from a market, you will likely encounter an enormous "gas price" fee. Ethereum is going through some growing pains, and this is an issue for every
5151smart contract on the network. This fee is unrelated to Urbit specifically, rather it results from how Ethereum transactions are paid for. The gas fee does not go to the person selling you the planet, nor to the market, nor to anybody associated with Urbit - it goes to the "miners" processing all Ethereum transactions.
5252
5353Tlon is aggressively pursuing a solution we call "naive rollups" which we predict to reduce gas costs by a factor of at least 100. We cannot give a precise estimate on when this will be complete, but it is top priority and this solution was chosen in part for the speed with which it can be implemented without sacrificing security. If you'd like to know more, we recommend watching this [Developer Call](https://www.youtube.com/watch?v=CKuHXrdkIw0) with `~wicdev-wisryt`.
5454
55−In the meantime, we recommend either using the network as a [comet](@/docs/glossary/comet.md), or signing up with a [hosting provider](#why-hosting), which includes a free planet.
55+In the meantime, we recommend either using the network as a [comet](/docs/glossary/comet), or signing up with a [hosting provider](#why-hosting), which includes a free planet.
5656
5757We understand that this is an enormous frustration, and will keep this section updated as we get closer to resolving it.
5858
5959### What is Azimuth? {#what-is-azimuth}
6060
61−[Azimuth](@/docs/glossary/azimuth.md) is what we call the set of Ethereum contracts that make up a general-purpose decentralized PKI ("public key infrastructure") utilized by Urbit ID. It keeps a record of which Ethereum addresses own which Urbit planets, stars, and galaxies, as well as the public keys associated with those ships.
61+[Azimuth](/docs/glossary/azimuth) is what we call the set of Ethereum contracts that make up a general-purpose decentralized PKI ("public key infrastructure") utilized by Urbit ID. It keeps a record of which Ethereum addresses own which Urbit planets, stars, and galaxies, as well as the public keys associated with those ships.
6262
6363It's also kind of a [cool astronomical concept](https://en.wikipedia.org/wiki/Azimuth).
6464
@@ -70,15 +70,15 @@ You can also inspect and execute functions in the [azimuth.eth](https://ethersca
7070
7171### What are comets and moons? {#comets-moons}
7272
73−In addition to the three classes of identities mentioned above, there are two other kinds of Urbit [ship](@/docs/glossary/ship.md)s that are _not_ registered in the Urbit ID / Azimuth contracts.
73+In addition to the three classes of identities mentioned above, there are two other kinds of Urbit [ship](/docs/glossary/ship)s that are _not_ registered in the Urbit ID / Azimuth contracts.
7474
75−[Moons](@/docs/glossary/moon.md) are 64 bits, issued by [planets](@/docs/glossary/planet.md), and have names like `~doznec-salfun-naptul-habrys`. Moons are meant for connected devices: phones, desktops, smart TVs, digital thermostats, and other IoT devices. Moons are subordinate to their parent planet. A strong analogy here is that ordinary social media sites are somewhat like planets, and your account on them is a moon. Urbit elevates everybody to the level of planet.
75+[Moons](/docs/glossary/moon) are 64 bits, issued by [planets](/docs/glossary/planet), and have names like `~doznec-salfun-naptul-habrys`. Moons are meant for connected devices: phones, desktops, smart TVs, digital thermostats, and other IoT devices. Moons are subordinate to their parent planet. A strong analogy here is that ordinary social media sites are somewhat like planets, and your account on them is a moon. Urbit elevates everybody to the level of planet.
7676
77−[Comets](@/docs/glossary/comet.md) are 128 bits and have no parents. They can be launched by anyone for free. Since their identity is not maintained on the blockchain, they will likely not be trusted by default by others on the [Urbit OS](#what-is-arvo) network, though you shouldn't have any problem until the network grows much larger. They have long, hard-to-memorize names, like `~racmus-mollen-fallyt-linpex-watres-sibbur-modlux-rinmex`.
77+[Comets](/docs/glossary/comet) are 128 bits and have no parents. They can be launched by anyone for free. Since their identity is not maintained on the blockchain, they will likely not be trusted by default by others on the [Urbit OS](#what-is-arvo) network, though you shouldn't have any problem until the network grows much larger. They have long, hard-to-memorize names, like `~racmus-mollen-fallyt-linpex-watres-sibbur-modlux-rinmex`.
7878
7979### What is a `@p`? Why is my username generated for me? {#what-is-patp}
8080
81−A `@p` ([pronounced](@/docs/hoon/hoon-school/hoon-syntax.md#reading-hoon-aloud) *pat-pee*) is a name like `~zod` or `~lodleb-ritrul` composed of pronounceable, three-letter phonemic elements like `zod`, `lod`, `leb`, `rit` and `rul`. Shorter names, such as `~zod` and `~marzod`, are assigned to [ship](@/docs/glossary/ship.md)s with special duties on the [Arvo](#what-is-arvo) network galaxies and stars, respectively. Longer names like `~palfun-foslup` are identities for typical users.
81+A `@p` ([pronounced](/docs/hoon/hoon-school/hoon-syntax#reading-hoon-aloud) *pat-pee*) is a name like `~zod` or `~lodleb-ritrul` composed of pronounceable, three-letter phonemic elements like `zod`, `lod`, `leb`, `rit` and `rul`. Shorter names, such as `~zod` and `~marzod`, are assigned to [ship](/docs/glossary/ship)s with special duties on the [Arvo](#what-is-arvo) network galaxies and stars, respectively. Longer names like `~palfun-foslup` are identities for typical users.
8282
8383These names map directly to a corresponding number in the Urbit ID address space. Galaxies occupy the 8-bit address space, so any galaxy is actually a number between zero and 255. Stars occupy the 16-bit address space, and planets occupy the 32-bit address space.
8484
@@ -92,9 +92,9 @@ Nope. There is a 1:1 mapping between name and identity. Think of your `@p` sort
9292
9393### How do I get an identity? {#get-an-identity}
9494
95−The easiest way is to find a friend who can give you one. They're out there — just ask around. You'll have a good chance of meeting one if you join Urbit Community, the default group for new [ship](@/docs/glossary/ship.md)s at `~bitbet-bolbel/urbit-community`, as a [comet](@/docs/glossary/comet.md) and contribute pleasantly to the conversation.
95+The easiest way is to find a friend who can give you one. They're out there — just ask around. You'll have a good chance of meeting one if you join Urbit Community, the default group for new [ship](/docs/glossary/ship)s at `~bitbet-bolbel/urbit-community`, as a [comet](/docs/glossary/comet) and contribute pleasantly to the conversation.
9696
97−Or, if you must, try an ERC-721 (NFT) exchange (Google or Twitter should help you with this). This will probably involve a purchase and a transfer to an Ethereum address that you own. We recommend using [Bridge](@/docs/glossary/bridge.md), available at [https://bridge.urbit.org](https://bridge.urbit.org), to access the address that the identity is transferred to.
97+Or, if you must, try an ERC-721 (NFT) exchange (Google or Twitter should help you with this). This will probably involve a purchase and a transfer to an Ethereum address that you own. We recommend using [Bridge](/docs/glossary/bridge), available at [https://bridge.urbit.org](https://bridge.urbit.org), to access the address that the identity is transferred to.
9898
9999### How do I transfer an identity to someone else? {#transfer-identity}
100100
@@ -108,7 +108,7 @@ Be careful about using online versions of Bridge not hosted on urbit.org. Since
108108
109109### Why aren't there more planets? {#more-planets}
110110
111−Urbit is designed to be as simple as possible. The sponsorship tree for Urbit ID simply expands by squaring the size of the last tier. That is, there are <span class="mono">2<sup>8</sup> (256)</span> [galaxies](@/docs/glossary/galaxy.md), <span class="mono">(2<sup>8</sup>)<sup>2</sup> = 2<sup>16</sup> (~65K)</span> [stars](@/docs/glossary/star.md), <span class="mono">(2<sup>16</sup>)<sup>2</sup> = 2<sup>32</sup> (~4B)</span> [planets](@/docs/glossary/planet.md). There are <span class="mono">2<sup>64</sup></span> [moons](@/docs/glossary/moon.md) — but moons are tethered to their planet, unlike stars and planets.
111+Urbit is designed to be as simple as possible. The sponsorship tree for Urbit ID simply expands by squaring the size of the last tier. That is, there are <span class="mono">2<sup>8</sup> (256)</span> [galaxies](/docs/glossary/galaxy), <span class="mono">(2<sup>8</sup>)<sup>2</sup> = 2<sup>16</sup> (~65K)</span> [stars](/docs/glossary/star), <span class="mono">(2<sup>16</sup>)<sup>2</sup> = 2<sup>32</sup> (~4B)</span> [planets](/docs/glossary/planet). There are <span class="mono">2<sup>64</sup></span> [moons](/docs/glossary/moon) — but moons are tethered to their planet, unlike stars and planets.
112112
113113This pattern exists because it’s a simple way to enforce the scarcity of addresses and build a friendly network. When a tier of the address space begins to be populated, we start populating the next tier down. When Urbit nears the limit of <span class="mono">2<sup>32</sup> (4B)</span> planets, we’ll figure out a way to populate the <span class="mono">2<sup>64</sup></span> moons. The galaxies that govern the Urbit ID contracts can always vote to upgrade them — and we expect that they will.
114114
@@ -124,38 +124,38 @@ It’s also worth noting that, while there are almost 8B people on Earth, there
124124
125125### What is the Urbit HD Wallet? {#urbit-hd-wallet}
126126
127−The [Urbit Hierarchical Deterministic (HD) Wallet](@/docs/glossary/hdwallet.md) is a custom Ethereum wallet based on BIP39 and BIP44 – the same underlying technology used by wallet providers like Ledger, Trezor, Metamask, and MyEtherWallet. You can think of the Urbit HD wallet as a wallet of wallets, which lets you keep a single passphrase for all of your Urbit ID keys. Urbit ID uses multiple keys with different capabilities – a bit like permissions – so that you can keep the more valuable keys in cold storage while keeping less valuable keys, used in day-to-day operation, more easily accessible. If you're only operating a planet, you shouldn't have to worry about this: you can simply think of your "master ticket" as the password to your Urbit ID. If you're operating a star or galaxy, the Urbit HD Wallet allows you to implement a multi-tier key custody scheme.
127+The [Urbit Hierarchical Deterministic (HD) Wallet](/docs/glossary/hdwallet) is a custom Ethereum wallet based on BIP39 and BIP44 – the same underlying technology used by wallet providers like Ledger, Trezor, Metamask, and MyEtherWallet. You can think of the Urbit HD wallet as a wallet of wallets, which lets you keep a single passphrase for all of your Urbit ID keys. Urbit ID uses multiple keys with different capabilities – a bit like permissions – so that you can keep the more valuable keys in cold storage while keeping less valuable keys, used in day-to-day operation, more easily accessible. If you're only operating a planet, you shouldn't have to worry about this: you can simply think of your "master ticket" as the password to your Urbit ID. If you're operating a star or galaxy, the Urbit HD Wallet allows you to implement a multi-tier key custody scheme.
128128
129129If you're interested, you can read the spec here: [Urbit HD Wallet Spec (UP 8)](https://github.com/urbit/proposals/blob/master/008-urbit-hd-wallet.md).
130130
131131### What is a master ticket? {#master-ticket}
132132
133−The "master ticket" is the entropy seed from which your other Urbit ID keys are derived. It should be treated like a master password: **you should never share it with anyone, and you must store it very securely (see our practices below).** This ticket is used to derive the Ethereum wallet that holds your ownership keys, your [Urbit OS](#what-is-arvo) key – used to boot your Urbit – and the other keys associated with your identity. You’ll have a master ticket if you used the Urbit Wallet Generator or claimed a [ship](@/docs/glossary/ship.md) on our hosted version of Bridge.
133+The "master ticket" is the entropy seed from which your other Urbit ID keys are derived. It should be treated like a master password: **you should never share it with anyone, and you must store it very securely (see our practices below).** This ticket is used to derive the Ethereum wallet that holds your ownership keys, your [Urbit OS](#what-is-arvo) key – used to boot your Urbit – and the other keys associated with your identity. You’ll have a master ticket if you used the Urbit Wallet Generator or claimed a [ship](/docs/glossary/ship) on our hosted version of Bridge.
134134
135135If you're operating a planet, you can use your master ticket to authenticate with Bridge.
136136
137137### What is an ownership address? {#ownership-address}
138138
139−An ownership address is an Ethereum address that owns one or more of your Urbit IDs. The Urbit Wallet Generator creates one [Urbit HD Wallet](@/docs/glossary/hdwallet.md) and associated addresses for each of your identities. Using the ownership key associated with your ownership address, you can transfer identities to other people, meaning that it’s very important to store securely.
139+An ownership address is an Ethereum address that owns one or more of your Urbit IDs. The Urbit Wallet Generator creates one [Urbit HD Wallet](/docs/glossary/hdwallet) and associated addresses for each of your identities. Using the ownership key associated with your ownership address, you can transfer identities to other people, meaning that it’s very important to store securely.
140140
141141### What are proxies? {#proxies}
142142
143−[Proxies](@/docs/glossary/proxies.md) are seeds derived from your master ticket used to generate sub-wallets, which in turn are used to generate keys that have the ability to execute different Urbit ID functions associated with your Urbit identity. Proxies generally have more restricted capabilities than your ownership seed. These capabilities include spawning child identities, voting, and setting networking keys.
143+[Proxies](/docs/glossary/proxies) are seeds derived from your master ticket used to generate sub-wallets, which in turn are used to generate keys that have the ability to execute different Urbit ID functions associated with your Urbit identity. Proxies generally have more restricted capabilities than your ownership seed. These capabilities include spawning child identities, voting, and setting networking keys.
144144
145145- Transfer proxy: Can transfer your identity to another Ethereum address.
146−- Spawn Proxy: For [stars](@/docs/glossary/star.md) and [galaxies](@/docs/glossary/galaxy.md) only. Can create new child identities.
146+- Spawn Proxy: For [stars](/docs/glossary/star) and [galaxies](/docs/glossary/galaxy) only. Can create new child identities.
147147- Management Proxy: Can configure or set networking keys and conduct sponsorship related operations.
148−- Voting Proxy: [Galaxies](@/docs/glossary/galaxy.md) only. Galaxies are the part of the [galactic senate](@/docs/glossary/senate.md), which means they can cast votes on new proposals including changes to the "[Ecliptic](@/docs/glossary/ecliptic.md)" contract, which defines the operations of [Azimuth](@/docs/glossary/azimuth.md).
148+- Voting Proxy: [Galaxies](/docs/glossary/galaxy) only. Galaxies are the part of the [galactic senate](/docs/glossary/senate), which means they can cast votes on new proposals including changes to the "[Ecliptic](/docs/glossary/ecliptic)" contract, which defines the operations of [Azimuth](/docs/glossary/azimuth).
149149
150150### What are seeds? {#seeds}
151151
152−All Ethereum key-pairs in the Urbit wallet system, including [proxies](@/docs/glossary/proxies.md), are produced by 128-bit cryptographically random values called seeds. These seeds are the equivalent of the BIP39 mnemonic of an Ethereum wallet and are yours alone. An ownership key pair is derived from an ownership seed and, likewise, the various proxy key pairs are generated from their respective proxy seeds.
152+All Ethereum key-pairs in the Urbit wallet system, including [proxies](/docs/glossary/proxies), are produced by 128-bit cryptographically random values called seeds. These seeds are the equivalent of the BIP39 mnemonic of an Ethereum wallet and are yours alone. An ownership key pair is derived from an ownership seed and, likewise, the various proxy key pairs are generated from their respective proxy seeds.
153153
154154For detailed information see the [Urbit HD Wallet Spec (UP 8)](https://github.com/urbit/proposals/blob/master/008-urbit-hd-wallet.md).
155155
156156### What does it mean to “set public keys”? {#set-public-keys}
157157
158−This means registering the public keys of your identity's encryption and authentication key pairs (together known as "networking keys") with Urbit ID / [Azimuth](@/docs/glossary/azimuth.md), so that others can discover them. The corresponding private keys can then be used to, for example, run a [ship](@/docs/glossary/ship.md) on the [Urbit OS](#what-is-arvo) network.
158+This means registering the public keys of your identity's encryption and authentication key pairs (together known as "networking keys") with Urbit ID / [Azimuth](/docs/glossary/azimuth), so that others can discover them. The corresponding private keys can then be used to, for example, run a [ship](/docs/glossary/ship) on the [Urbit OS](#what-is-arvo) network.
159159
160160You want to reset these keys if they are compromised, or if your ship has sunk. This is of little practical significance today, but resetting your networking keys resets your relationship with other ships on the network.
161161
@@ -212,25 +212,25 @@ There are two kinds of release schemes for locked up assets: linear and conditio
212212
213213In either scheme, you start out being able to take one star out of lockup, regardless of the terms set around the lockup as a whole. This way, you get to participate with a star right away. Go do something cool!
214214
215−If your lockup involved a [galaxy](@/docs/glossary/galaxy.md), all of its [stars](@/docs/glossary/star.md) will be locked up, but you will have immediate, lock-free control of the galaxy. You will likely need it to use that star.
215+If your lockup involved a [galaxy](/docs/glossary/galaxy), all of its [stars](/docs/glossary/star) will be locked up, but you will have immediate, lock-free control of the galaxy. You will likely need it to use that star.
216216
217217Note that the "releasing" of stars just means that they become available for you to claim. They don't automatically get transferred to you; you have to withdraw them from the appropriate lockup contract.
218218
219219Linear release is the simplest: your stars will be released linearly over a period of time. Most often this is a period of four years. If you have four stars in lockup, that means you will be able to withdraw one star per year. In many cases, there is also an initial windup period which has to pass before linear releasing begins, typically one year. Since Azimuth launched in January 2019, the linear release will begin in January 2020.
220220
221−Conditional release is a bit more complicated. If your stars are in conditional lockup, they're likely divided over three so-called tranches. Each of these unlocks only after a unique condition is met. Since it's difficult to verify things about the real world using smart contracts, the [Galactic Senate](@/docs/glossary/senate.md) verifies that they've been met. Once the Senate marks a condition for a tranche as cleared, it starts releasing linearly over the period of a year.
221+Conditional release is a bit more complicated. If your stars are in conditional lockup, they're likely divided over three so-called tranches. Each of these unlocks only after a unique condition is met. Since it's difficult to verify things about the real world using smart contracts, the [Galactic Senate](/docs/glossary/senate) verifies that they've been met. Once the Senate marks a condition for a tranche as cleared, it starts releasing linearly over the period of a year.
222222
223223## Urbit OS
224224
225225### What is Urbit OS? {#what-is-arvo}
226226
227−Urbit OS, also called [Arvo](@/docs/glossary/arvo.md), is our functional and deterministic software stack. Arvo is written in [Hoon](@/docs/glossary/hoon.md), our purely functional programming language, which compiles to [Nock](@/docs/glossary/nock.md), a compact bytecode language.
227+Urbit OS, also called [Arvo](/docs/glossary/arvo), is our functional and deterministic software stack. Arvo is written in [Hoon](/docs/glossary/hoon), our purely functional programming language, which compiles to [Nock](/docs/glossary/nock), a compact bytecode language.
228228
229−Instances of Urbit OS, called '[ships](@/docs/glossary/ship.md)', communicate as peers on what we refer to as “the [Ames](@/docs/glossary/ames.md) network.” Using Urbit ID, Urbit OS ships can prove their identities to one another.
229+Instances of Urbit OS, called '[ships](/docs/glossary/ship)', communicate as peers on what we refer to as “the [Ames](/docs/glossary/ames) network.” Using Urbit ID, Urbit OS ships can prove their identities to one another.
230230
231231### What is unique about Urbit OS / Arvo? {#what-is-unique-about-arvo}
232232
233−[Arvo](@/docs/glossary/arvo.md) is different from other operating systems in many ways. One notable way is that it is completely deterministic. Processing in the system happens in a unique way: when an event happens, a transition function takes that event and the old state of Arvo, and produces an effect and a new state of Arvo. To visualize:
233+[Arvo](/docs/glossary/arvo) is different from other operating systems in many ways. One notable way is that it is completely deterministic. Processing in the system happens in a unique way: when an event happens, a transition function takes that event and the old state of Arvo, and produces an effect and a new state of Arvo. To visualize:
234234
235235`[event, old state] -> [effects, new state]`
236236
@@ -238,21 +238,21 @@ All events are logged to disk, so you can always restore the system to a previou
238238
239239### How is Urbit OS / Arvo connected to Ethereum? {#arvo-ethereum}
240240
241−When an [Arvo](@/docs/glossary/arvo.md) ship (instance) is started for the first time you must use a "[keyfile](@/docs/glossary/keyfile.md)" containing the private keys for your identity's networking keys. Urbit ID uses the Ethereum blockchain as its decentralized ledger.
241+When an [Arvo](/docs/glossary/arvo) ship (instance) is started for the first time you must use a "[keyfile](/docs/glossary/keyfile)" containing the private keys for your identity's networking keys. Urbit ID uses the Ethereum blockchain as its decentralized ledger.
242242
243−See our [Getting Started](@/getting-started/planet.md) guide to learn how to get your ship onto the Urbit OS / [Ames](@/docs/glossary/ames.md) network.
243+See our [Getting Started](/getting-started/planet) guide to learn how to get your ship onto the Urbit OS / [Ames](/docs/glossary/ames) network.
244244
245245### Will the Urbit OS network survive if Ethereum dies? {#if-ethereum-dies}
246246
247−Yes. It would be annoying, but Urbit ID / [Azimuth](@/docs/glossary/azimuth.md) could be ported to another decentralized ledger, or hosted on Urbit OS / [Arvo](@/docs/glossary/arvo.md) itself.
247+Yes. It would be annoying, but Urbit ID / [Azimuth](/docs/glossary/azimuth) could be ported to another decentralized ledger, or hosted on Urbit OS / [Arvo](/docs/glossary/arvo) itself.
248248
249249### How do I install Urbit OS? {#install-urbit-os}
250250
251−Check out our guides [here](@/getting-started/_index.md).
251+Check out our guides [here](/getting-started/).
252252
253253### How do I use Urbit OS? {#use-urbit-os}
254254
255−The [Using](@/using/os/getting-started.md) section of the documentation will help you out.
255+The [Using](/using/os/getting-started) section of the documentation will help you out.
256256
257257### How do over-the-air updates work? {#over-the-air-updates}
258258
@@ -260,13 +260,13 @@ Your sponsor, a star or galaxy that your ship is connected to, may send you new
260260
261261### What is Landscape? {#what-is-landscape}
262262
263−[Landscape](@/docs/glossary/landscape.md) is an experimental Urbit OS web interface that includes social functions such as chat and publishing. You can access Landscape by navigating to `http://localhost:PORT`, where PORT is typically 80, 8080, or 8081 (check your boot messages).
263+[Landscape](/docs/glossary/landscape) is an experimental Urbit OS web interface that includes social functions such as chat and publishing. You can access Landscape by navigating to `http://localhost:PORT`, where PORT is typically 80, 8080, or 8081 (check your boot messages).
264264
265265### I have an Urbit ID, now what? {#now-what}
266266
267−Follow our guide on how to boot a ship [here](@/getting-started/planet.md).
267+Follow our guide on how to boot a ship [here](/getting-started/planet).
268268
269−Get on the [mailing list](https://urbit.us11.list-manage.com/subscribe/post?u=972a03db9e0c6c25bb58de8c8&amp;id=be143888d2). Learn [Hoon](@/docs/hoon/hoon-school/_index.md). Sign up for [Hooniversity](https://hooniversity.org/). [Make stuff](https://grants.urbit.org).
269+Get on the [mailing list](https://urbit.us11.list-manage.com/subscribe/post?u=972a03db9e0c6c25bb58de8c8&amp;id=be143888d2). Learn [Hoon](/docs/hoon/hoon-school/). Sign up for [Hooniversity](https://hooniversity.org/). [Make stuff](https://grants.urbit.org).
270270
271271
272272## Urbit Grants
@@ -378,7 +378,7 @@ One day we’d really like the Urbit ID registry to be hosted on [Urbit OS](#wha
378378
379379### Why is Hoon so weird? {#why-hoon}
380380
381−There are things about Urbit that are weird by design, and some that are weird because we haven’t gotten around to cleaning them up. [Hoon](@/docs/glossary/hoon.md), for the most part, is weird by design, but there are a few things about it we’d like to clean up. For a complete description of why we created Hoon, see the [Hoon overview](@/docs/hoon/overview.md).
381+There are things about Urbit that are weird by design, and some that are weird because we haven’t gotten around to cleaning them up. [Hoon](/docs/glossary/hoon), for the most part, is weird by design, but there are a few things about it we’d like to clean up. For a complete description of why we created Hoon, see the [Hoon overview](/docs/hoon/overview).
382382
383383The runes are, once you get the hang of them, pretty nice. Your mileage may vary, of course, but many talented engineers have spent many, many hours writing Hoon. It’s a simple, practical language. But the learning curve can be a bit high.
384384
@@ -386,16 +386,16 @@ The standard library and naming is something we’ve discussed changing, and it
386386
387387The right way to think about Hoon is as the ‘C of Urbit’. It’s a bare bones language that gets you pretty close to Nock. Eventually, we’ll probably implement more expressive languages that compile to Urbit. But for now, satisfy your curiosity and [sign up for Hooniversity](https://hooniversity.org/), a community led Hoon educational organization.
388388
389−Another option is to treat [Urbit as an API](@/docs/arvo/eyre/using-eyre.md), which allows one to use common languages such as Python and Javascript to build userspace programs. For now this option is not as powerful as Hoon, but there is still a lot that a developer without the time or inclination to learn Hoon can do.
389+Another option is to treat [Urbit as an API](/docs/arvo/eyre/using-eyre), which allows one to use common languages such as Python and Javascript to build userspace programs. For now this option is not as powerful as Hoon, but there is still a lot that a developer without the time or inclination to learn Hoon can do.
390390
391391### What is the point of Nock? {#why-nock}
392392
393−The primary technical reason it is difficult for the individual to run a personal server is that modern computing architectures are not deterministic. What solves a problem for one person is not guaranteed to work on another person's computer, even if they are using identical hardware. [Nock](@/docs/glossary/nock.md) solves this problem. It provides a single computing foundation for the whole network, so that difficult issues that arise when running a server need only to be solved once and the solution is guaranteed to work for everyone on the network.
393+The primary technical reason it is difficult for the individual to run a personal server is that modern computing architectures are not deterministic. What solves a problem for one person is not guaranteed to work on another person's computer, even if they are using identical hardware. [Nock](/docs/glossary/nock) solves this problem. It provides a single computing foundation for the whole network, so that difficult issues that arise when running a server need only to be solved once and the solution is guaranteed to work for everyone on the network.
394394
395−It’s true that Nock, without jets, is slow. With the ability to call out to a native function, it’s not so bad. This is done by our runtime, [Vere](@/docs/glossary/vere.md), a Nock interpreter written in C.
395+It’s true that Nock, without jets, is slow. With the ability to call out to a native function, it’s not so bad. This is done by our runtime, [Vere](/docs/glossary/vere), a Nock interpreter written in C.
396396
397397### Can I host my Urbit with someone else? {#why-hosting}
398398
399−Yes, [Tlon](@/blog/hosting-the-future.md) and [a few others](@/blog/providers.md) began [accepting signups](https://tlon.io) to provide hosting service in 2020. Under this arrangement, Tlon does all the work of setting up cloud infrastructure and getting your planet up and running, making getting started with Urbit as simple as signing up for an ordinary online service.
399+Yes, [Tlon](/blog/hosting-the-future) and [a few others](/blog/providers) began [accepting signups](https://tlon.io) to provide hosting service in 2020. Under this arrangement, Tlon does all the work of setting up cloud infrastructure and getting your planet up and running, making getting started with Urbit as simple as signing up for an ordinary online service.
400400
401−Should you one day wish to run your Urbit yourself, any hosting provider ought to offer you the ability to download your [ship](@/docs/glossary/ship.md)'s [pier](@/docs/glossary/pier.md) to your own device and do so. This is a very low friction process thanks to Urbit's deterministic design.
401+Should you one day wish to run your Urbit yourself, any hosting provider ought to offer you the ability to download your [ship](/docs/glossary/ship)'s [pier](/docs/glossary/pier) to your own device and do so. This is a very low friction process thanks to Urbit's deterministic design.
content/getting-started/_index.md+2−2
@@ -8,7 +8,7 @@ template = "getting-started/index.html"
88
99If you use Mac or Linux and just want to jump in, you can download **Port** and install it to run Urbit for you and get going right away. You can also set up Urbit using the command line.
1010
11−If you run Windows, or just want to give it a shot without worrying about the gritty bits, you may want to consider a [hosting provider](@/getting-started/planet.md#hosting-providers), though Windows instructions are provided [for power users](@/getting-started/cli.md).
11+If you run Windows, or just want to give it a shot without worrying about the gritty bits, you may want to consider a [hosting provider](/getting-started/planet#hosting-providers), though Windows instructions are provided [for power users](/getting-started/cli).
1212
1313### Get Port {#port}
1414
@@ -81,4 +81,4 @@ Or to install `snap` for your distribution, snapcraft provides [installation ins
8181}
8282</style>
8383
84−If you'd like to have more direct control over the Urbit virtual machine, or are setting up Urbit on a cloud droplet, try [installation using the command line](@/getting-started/cli.md).
84+If you'd like to have more direct control over the Urbit virtual machine, or are setting up Urbit on a cloud droplet, try [installation using the command line](/getting-started/cli).
content/getting-started/cli.md+5−5
@@ -74,9 +74,9 @@ There are five kinds of Urbit IDs but to get started you only need to know about
7474
7575A planet name looks like `~sampel-palnet`.
7676
77−[Follow this guide](@/getting-started/planet.md) if you have already acquired a planet.
77+[Follow this guide](/getting-started/planet) if you have already acquired a planet.
7878
79−[Find a planet to purchase](@/getting-started/planet.md#purchase)
79+[Find a planet to purchase](/getting-started/planet#purchase)
8080
8181***
8282
@@ -119,7 +119,7 @@ To start your comet up again, run the following from your `urbit` directory (not
119119
120120Urbit is an entirely new computer, so by default it drops you into the "dojo," which is its terminal. Like your current computer, it can be used to do just about anything if you know the right commands. You only need to know one command for now.
121121
122−At the moment, the most common way to use Urbit is through a web app named [Landscape](@/docs/glossary/landscape.md), which comes with Urbit. It runs in your browser and provides an interface to Urbit without using the terminal. You need to get the password, or `code`.
122+At the moment, the most common way to use Urbit is through a web app named [Landscape](/docs/glossary/landscape), which comes with Urbit. It runs in your browser and provides an interface to Urbit without using the terminal. You need to get the password, or `code`.
123123
1241241. With your Urbit running, 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. It will probably be 80, but we're just making sure. (Don't worry about the "insecure, public" part — that just means you can access it from your own web browser. It doesn't give anyone else access.)
1251252. 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`. You'll be met with a login prompt.
@@ -153,7 +153,7 @@ use |ota %disable or |ota ~sponsor %kids to reset it
153153
154154The dojo is Urbit's command line. You can use it to control your ship, or to execute arbitrary code. Check out the links below for more information.
155155
156−- [Basic Operations](@/using/os/getting-started.md)
156+- [Basic Operations](/using/os/getting-started)
157157- [Basic Hoon](/docs/tutorials/hoon/hoon-school/setup)
158158- [Glossary Entry](/docs/glossary/dojo)
159159
@@ -163,7 +163,7 @@ You can continue using this comet indefinitely. There are currently few differen
163163
164164A comet also comes with a long and fairly unmemorable name whereas a planet has a short name and a "sigil" (avatar) associated with it that makes it more identifiable on the network. You may notice all this within the first few minutes of using Urbit.
165165
166−[To read instructions on how to purchase and use a planet, visit this page](@/getting-started/planet.md).
166+[To read instructions on how to purchase and use a planet, visit this page](/getting-started/planet).
167167
168168
169169<style>
content/getting-started/planet.md+9−9
@@ -4,7 +4,7 @@ weight = 1
44description = "Getting started with a permanent Urbit identity."
55+++
66
7−A planet is a permanent Urbit identity. Like all Urbit identities, they can never be taken away from you. Unlike comets which are free, planets are designed for use well into the future. If you're not yet familiar with the Urbit network, please follow the [Getting Started guide](@/getting-started/_index.md), which will explain the basics and walk you through using a free identity. This guide explains the next steps.
7+A planet is a permanent Urbit identity. Like all Urbit identities, they can never be taken away from you. Unlike comets which are free, planets are designed for use well into the future. If you're not yet familiar with the Urbit network, please follow the [Getting Started guide](/getting-started/), which will explain the basics and walk you through using a free identity. This guide explains the next steps.
88
99### Purchase a planet {#purchase}
1010
@@ -14,7 +14,7 @@ There are a few ways to get your own planet:
1414- Purchasing a planet, including hosting, from a [hosting provider](#hosting-providers) such as [geturbitid.com](https://www.geturbitid.com/).
1515- Manually setting up and hosting a planet purchased from a third party such as [urbit.live](https://urbit.live), [OpenSea](https://opensea.io), [planet.market](https://planet.market/), [urbit.me](https://urbit.me), [urth systems](https://urth.systems/), or [Urbit Marketplace](https://urbitmarketplace.com/).
1616
17−Note that when you buy a planet, you should ensure with the provider that your parent star is operating. If you need to escape a non-operational star, see [Escaping A Sponsor](@/using/id/using-bridge.md#escaping-your-sponsor).
17+Note that when you buy a planet, you should ensure with the provider that your parent star is operating. If you need to escape a non-operational star, see [Escaping A Sponsor](/using/id/using-bridge#escaping-your-sponsor).
1818
1919### Hosting Providers {#hosting-providers}
2020
@@ -34,7 +34,7 @@ Current hosting providers are:
3434
3535Urbit must run on an existing computer somewhere. Most users run their planet on their personal computer, but we recommend eventually using a cloud service (Digital Ocean, Linode, etc) because it allows your planet to be accessed from anywhere on multiple devices. Hosting your planet in the cloud also allows it to always be online and ready for automatic updates. You are welcome to run from your personal computer and switch to the cloud later...all without losing any data!
3636
37−There is a guide for [hosting your planet on DigitalOcean](@/using/running/hosting.md) and [hosting your planet on Linode](https://jeremytunnell.com/2021/01/09/how-to-install-urbit-on-a-linode-vps), but any cloud hosting service should work.
37+There is a guide for [hosting your planet on DigitalOcean](/using/running/hosting) and [hosting your planet on Linode](https://jeremytunnell.com/2021/01/09/how-to-install-urbit-on-a-linode-vps), but any cloud hosting service should work.
3838
3939### Get your keyfile {#keyfile}
4040
@@ -73,7 +73,7 @@ Either command will create a directory called `sampel-palnet/` and begin booting
7373
7474When your planet is finished booting, you will see `~sampel-palnet:dojo>` (Dojo: the Urbit command line).
7575
76−To log into [Landscape](@/docs/glossary/landscape.md), check out the directions [here](/getting-started/#using-landscape).
76+To log into [Landscape](/docs/glossary/landscape), check out the directions [here](/getting-started/#using-landscape).
7777
7878To shut down your planet, use `Ctrl-D`.
7979
@@ -106,7 +106,7 @@ The first thing you generally want to do with a new planet is to **mount** it. A
106106
107107The `>=` output means that a command was successful. Now you can see your planet's files in its directory.
108108
109−To understand what happened with this command, read more about Urbit’s filesystem (called “clay”) [here](@/docs/arvo/clay/clay.md).
109+To understand what happened with this command, read more about Urbit’s filesystem (called “clay”) [here](/docs/arvo/clay/clay).
110110
111111## Updating {#updating}
112112
@@ -120,13 +120,13 @@ use |ota %disable or |ota ~sponsor %kids to reset it
120120>=
121121```
122122
123−If for some reason your sponsor (in this case, `~dopzod`) is not responding, read instructions on [escaping your sponsor](@/using/id/using-bridge.md#escaping-your-sponsor).
123+If for some reason your sponsor (in this case, `~dopzod`) is not responding, read instructions on [escaping your sponsor](/using/id/using-bridge#escaping-your-sponsor).
124124
125125
126126## Next Steps
127127
128128Now that you’re up and running, take some time to deepen your understanding by checking out some of our other guides:
129129
130−- [Host your Ship in the Cloud](@/using/running/hosting.md): Follow this guide to set your ship up to run as a cloud server, accessible from anywhere.
131−- [Read the Operations Manual](@/using/os/getting-started.md): Become an expert pilot by learning to use your ship.
132−- [Learn to Develop on Urbit](@/docs/development/develop.md): Learn how to contribute to or develop on Urbit.
130+- [Host your Ship in the Cloud](/using/running/hosting): Follow this guide to set your ship up to run as a cloud server, accessible from anywhere.
131+- [Read the Operations Manual](/using/os/getting-started): Become an expert pilot by learning to use your ship.
132+- [Learn to Develop on Urbit](/docs/development/develop): Learn how to contribute to or develop on Urbit.
content/reset.md+3−3
@@ -76,9 +76,9 @@ Yes, by following these steps (note that these steps **will not** back up your d
7676
77771. Download your [keyfile from Bridge](https://urbit.org/getting-started/#keyfile).
78782. Shut down your ship.
79−3. [Archive and move your old pier](@/using/os/getting-started.md#moving-your-pier) (this is the directory that contains your urbit event log).
80−4. [Download the latest version](@/getting-started/_index.md) of the urbit binary.
81−5. [Boot your ship with the new keyfile](@/getting-started/_index.md).
79+3. [Archive and move your old pier](/using/os/getting-started#moving-your-pier) (this is the directory that contains your urbit event log).
80+4. [Download the latest version](/getting-started/) of the urbit binary.
81+5. [Boot your ship with the new keyfile](/getting-started/).
8282
8383## I’m hosted by Tlon, or someone else—what do I need to do?
8484
content/understanding-urbit/interface.md+1−1
@@ -43,7 +43,7 @@ OS 1 is a minimal, multipurpose interface for bringing a group together to chat,
4343
4444We built OS 1 for ourselves. We were sick of using centralized, mainstream software. We didn’t want to be stuck switching between bloated, monolithic services in order to keep in touch and move our work forward. We were done relying on some third party to take care of our community—so we exited to Urbit, and it feels good.
4545
46−If you’re curious to get a complete overview of OS 1, check out [this post](https://urbit.org/blog/introducing-os1/), watch the [release event](https://www.youtube.com/watch?v=71ViyftPkGk&feature=youtu.be&t=3963) or feel free to [boot a node](@/getting-started/_index.md) to come talk to us.
46+If you’re curious to get a complete overview of OS 1, check out [this post](https://urbit.org/blog/introducing-os1/), watch the [release event](https://www.youtube.com/watch?v=71ViyftPkGk&feature=youtu.be&t=3963) or feel free to [boot a node](/getting-started/) to come talk to us.
4747
4848(Running Urbit still requires a little fiddling around in the command-line, so it’s not for everyone—but we do have [plans for that to improve](https://urbit.org/blog/providers/).)
4949
content/understanding-urbit/people-history.md+1−1
@@ -38,7 +38,7 @@ src="https://media.urbit.org/site/understanding-urbit/uu-people-history-2a.jpg"/
3838src="https://media.urbit.org/site/understanding-urbit/uu-people-history-2c.jpg"
3939/>
4040
41−Given how new and unusual Urbit is, it attracts a wide variety of interesting people — both technical and non-technical. The community is generally happy to talk to people about what Urbit is, what we’re up to, and where we’re going. The best way to get involved is to simply join the Urbit Community at `~bitbet-bolbel/urbit-community` — which our [setup instructions](@/using/os/getting-started.md) can help you do.
41+Given how new and unusual Urbit is, it attracts a wide variety of interesting people — both technical and non-technical. The community is generally happy to talk to people about what Urbit is, what we’re up to, and where we’re going. The best way to get involved is to simply join the Urbit Community at `~bitbet-bolbel/urbit-community` — which our [setup instructions](/using/os/getting-started) can help you do.
4242
4343For those interested in contributing there are some simple instructions on [GitHub](https://github.com/urbit/urbit/blob/master/CONTRIBUTING.md#contributing-to-urbit), but we also run a [grants program](https://grants.urbit.org/) where we reward contributors with Urbit ID address space. Grants aren’t solely for pre-determined projects, either. If you have something you’d like to propose, we’d love to hear from you.
4444
content/using/_index.md+6−6
@@ -11,23 +11,23 @@ contributions are welcome.
1111
1212This documentation provides a series of guides and reference material for
1313assisting you in the usage and operations of your ship. If you're looking for
14−documentation on how to *develop* on Urbit, see our [development docs](@/docs/_index.md).
14+documentation on how to *develop* on Urbit, see our [development docs](/docs/).
1515
16−### [Urbit OS](@/using/os/_index.md)
16+### [Urbit OS](/using/os/)
1717
1818This section describes how to interact with your running Urbit ship: this
1919includes working with the filesystem, command line (`dojo`), resolving common
2020issues, and more.
2121
22−### [Urbit ID](@/using/id/_index.md)
22+### [Urbit ID](/using/id/)
2323
24−Urbit ID is our [public-key infrastructure](@/using/id/overview.md), which is
24+Urbit ID is our [public-key infrastructure](/using/id/overview), which is
2525what allows you to truly own your identity. Here you'll find guides for
2626interacting with your Urbit ID via our [Bridge](https://bridge.urbit.org)
2727application.
2828
29−### [Running Urbit](@/using/running/_index.md)
29+### [Running Urbit](/using/running/)
3030
3131Urbit can be run in a variety of contexts. Our [Getting Started
32−Guide](@/getting-started/_index.md) covers how to run an Urbit locally on your
32+Guide](/getting-started/) covers how to run an Urbit locally on your
3333computer; this section covers alternative ways of running Urbit.
content/using/id/_index.md+7−7
@@ -6,28 +6,28 @@ description = "How to interact with Urbit ID."
66weight = 20
77+++
88
9−Urbit ID is our [public-key infrastructure](@/using/id/overview.md), which is
10−what allows you to truly own your identity.
9+Urbit ID is our [public-key infrastructure](/using/id/overview), which is
10+what allows you to truly own your identity.
1111
12−### [Overview](@/using/id/overview.md)
12+### [Overview](/using/id/overview)
1313
1414This document discusses what Urbit ID is, how it's built, and why it's been
1515built that way at a high level.
1616
17−### [Using Bridge](@/using/id/using-bridge.md)
17+### [Using Bridge](/using/id/using-bridge)
1818
1919A guide to using [Bridge](https://bridge.urbit.org), our tool for managing your
2020Urbit ID.
2121
22−### [Bridge Troubleshooting](@/using/id/bridge-troubleshooting.md)
22+### [Bridge Troubleshooting](/using/id/bridge-troubleshooting)
2323
2424How to resolve common issues in Bridge.
2525
26−### [Creating an Invite Pool](@/using/id/creating-an-invite-pool.md)
26+### [Creating an Invite Pool](/using/id/creating-an-invite-pool)
2727
2828If you own a star, invite pools allow your friends to invite others onto the
2929network.
3030
31−### [Guide to Breaches](@/using/id/guide-to-breaches.md)
31+### [Guide to Breaches](/using/id/guide-to-breaches)
3232
3333What to do when things go very wrong and you need to start over.
content/using/id/creating-an-invite-pool.md+2−2
@@ -11,7 +11,7 @@ pool and how to share it with your friends using our tool
1111[Bridge](https://bridge.urbit.org).
1212
1313For more general tips on using your star, check out the [Star and Galaxy
14−Operations page](@/using/_index.md).
14+Operations page](/using/).
1515
1616## Anatomy of an Invite Pool
1717
@@ -66,7 +66,7 @@ Once the transaction is complete, the planet will have access to the invite pool
6666
67671. Log into Bridge using the planet assigned an invite pool above using the
6868 planet's Master Ticket or ownership address.
69−
69+
70702. Under "Invite Group", click "Add Members" to unroll the invitation UI.
7171
72723. Select either "Email" or "URL".
content/using/id/guide-to-breaches.md+11−11
@@ -4,7 +4,7 @@ weight = 40
44template = "doc.html"
55+++
66
7−An important concept on the [Ames](@/docs/arvo/ames/ames.md) network is that of continuity. Continuity refers to how ships remember the order of their own network messages and the network messages of others -- these messages are numbered, starting from zero. A _breach_ is when ships on the network agree to forget about this sequence and treat one or more ships like they are brand new.
7+An important concept on the [Ames](/docs/arvo/ames/ames) network is that of continuity. Continuity refers to how ships remember the order of their own network messages and the network messages of others -- these messages are numbered, starting from zero. A _breach_ is when ships on the network agree to forget about this sequence and treat one or more ships like they are brand new.
88
99There are two kinds of breaches: (personal) **breaches** and **network breaches**.
1010
@@ -31,7 +31,7 @@ There are two separate sequences of actions you need to take in order to breach.
3131One flow is for when you wish to keep Ethereum ownership address of the ship the
3232same, and the other is for when you are transferring the ship to a new Ethereum
3333ownership address. We make the emphasis about the Ethereum _ownership_ address
34−as changing your [proxies](@/docs/glossary/proxies.md) does not require a
34+as changing your [proxies](/docs/glossary/proxies) does not require a
3535breach.
3636
3737If you will be keeping your ship at the same Ethereum ownership address and
@@ -41,9 +41,9 @@ would like to perform a breach, follow the steps below.
4141- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking Keys`.
4242- Check the `Breach Continuity` box. Click `Reset Networking Keys`, and then click `Send Transaction` and wait for the progress bar to appear.
4343- Download your new keyfile following these instructions: [Generate your
44− keyfile](@/using/id/using-bridge.md#generate-your-keyfile).
45−- Delete or archive your old [pier](@/docs/glossary/pier.md).
46−- Proceed to [boot your ship](@/getting-started/cli.md#boot-your-planet) with the new keyfile.
44+ keyfile](/using/id/using-bridge#generate-your-keyfile).
45+- Delete or archive your old [pier](/docs/glossary/pier).
46+- Proceed to [boot your ship](/getting-started/cli#boot-your-planet) with the new keyfile.
4747- Delete your keyfile after successfully booting.
4848- Rejoin your favorite chat channels and subscriptions.
4949
@@ -60,13 +60,13 @@ you are transferring to another address you own. The process here is slightly di
6060- Logout of your current session in Bridge by clicking `Logout` at the top, and
6161 then login to your new ownership address.
6262- From here, following the directions on how to [Accept your
63− transfer](@/using/id/using-bridge.md#accept-your-transfer), [Set your
64− networking keys](@/using/id/using-bridge.md#set-your-networking-keys),
63+ transfer](/using/id/using-bridge#accept-your-transfer), [Set your
64+ networking keys](/using/id/using-bridge#set-your-networking-keys),
6565 and [Generate your
66− keyfile](@/using/id/using-bridge.md#generate-your-keyfile). The option
66+ keyfile](/using/id/using-bridge#generate-your-keyfile). The option
6767 whether or not to breach is in the Accept your Transfer step.
68−- Delete or archive your old [pier](@/docs/glossary/pier.md).
69−- Proceed to [boot your ship](@/getting-started/cli.md#boot-your-planet) with the new keyfile.
68+- Delete or archive your old [pier](/docs/glossary/pier).
69+- Proceed to [boot your ship](/getting-started/cli#boot-your-planet) with the new keyfile.
7070- Delete your keyfile after successfully booting.
7171- Rejoin your favorite chat channels and subscriptions.
7272
@@ -75,7 +75,7 @@ you are transferring to another address you own. The process here is slightly di
7575Network breaches were events where all ships on the network were required to
7676update to a new continuity era. Network breaches happened when an Arvo update
7777was released that could not be implemented via an [OTA
78−update](@/docs/glossary/ota-updates.md). The continuity era is given by an
78+update](/docs/glossary/ota-updates). The continuity era is given by an
7979integer in Ames that is incremented when the network breaches. Only ships with
8080the same such value are able to communicate with one another. The most recent
8181network breach occurred in December 2020, and we expect it to have been the final one.
content/using/id/using-bridge.md+5−5
@@ -14,7 +14,7 @@ This guide assumes that you have an Urbit ID, or that you have found someone to
1414
1515To connect to Bridge, go to [https://bridge.urbit.org](https://bridge.urbit.org) into your browser, and enter your identity's credentials in the appropriate fields. If you were invited to claim an Urbit ID, 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.
1616
17−You'll arrive at a page and see two major choices: `ID` and `OS`. `OS` is the only option that you're interested in right now; click on it. On the `OS` page, click the `Download Arvo Keyfile` button. Once you have downloaded the keyfile, you can exit Bridge and proceed to [install the Urbit binary](@/getting-started/_index.md).
17+You'll arrive at a page and see two major choices: `ID` and `OS`. `OS` is the only option that you're interested in right now; click on it. On the `OS` page, click the `Download Arvo Keyfile` button. Once you have downloaded the keyfile, you can exit Bridge and proceed to [install the Urbit binary](/getting-started/).
1818
1919### Local Bridge
2020
@@ -23,7 +23,7 @@ Alternatively, Bridge can be run locally. It's more complicated, but we recommen
2323To use Bridge:
2424
2525- Unzip the .zip file that you downloaded (bridge-$version.zip).
26−- Open up your command line interface (Terminal on
26+- Open up your command line interface (Terminal on
2727X, Command Prompt on Windows).
2828- Navigate to the bridge-$version directory, where $version is the appropriate version number.
2929- Run this command: `python3 -m http.server 5000 --bind 127.0.0.1.`
@@ -44,7 +44,7 @@ After you access your Ethereum address, if a point was sent to that address, you
4444
4545Now you'll be on the management page of your point. The transfer isn't completed
4646yet, so click `Accept incoming transfer`. If you are transferring to yourself
47−and do not wish to [breach](@/docs/glossary/breach.md), check the box labeled
47+and do not wish to [breach](/docs/glossary/breach), check the box labeled
4848`Retain proxies and key configuration, in case of transferring to self`.
4949Otherwise leave the box unchecked, ensuring that your ship will be breached upon
5050transfer and thus no Azimuth data from the previous owner (namely proxies and
@@ -72,7 +72,7 @@ It should be noted that setting your network keys is an event on the Ethereum ne
7272From 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 it's not filled in or does not match, fill it in with the correct string.
7373Click `Generate ->`, which will download a keyfile onto your machine.
7474
75−With that keyfile in hand, you can now exit Bridge and continue to the guide to [install the Urbit binary](@/getting-started/_index.md).
75+With that keyfile in hand, you can now exit Bridge and continue to the guide to [install the Urbit binary](/getting-started/).
7676
7777### Escaping your sponsor {#escaping-your-sponsor}
7878
@@ -109,5 +109,5 @@ may check that your sponsor has successfully been altered by running
109109your new sponsor.
110110
111111Once you change your sponsor, you will likely want to change your source of
112−[OTAs](@/docs/glossary/ota-updates.md) to them as well. To accomplish this, enter `|ota
112+[OTAs](/docs/glossary/ota-updates) to them as well. To accomplish this, enter `|ota
113113~sponsor %kids` in dojo, where `~sponsor` is the `@p` of your new sponsor.
content/using/os/_index.md+6−6
@@ -10,27 +10,27 @@ This section describes how to interact with your running Urbit ship: this
1010includes working with the filesystem, command line (`dojo`), resolving common
1111issues, and more.
1212
13−### [Getting Started](@/using/os/getting-started.md)
13+### [Getting Started](/using/os/getting-started)
1414
1515An overview of common commands and useful general knowledge for operating your
1616ship.
1717
18−### [Messaging](@/using/os/messaging.md)
18+### [Messaging](/using/os/messaging)
1919
2020Using chat from its command-line interface.
2121
22−### [Configuring S3 Storage](@/using/os/s3.md)
22+### [Configuring S3 Storage](/using/os/s3)
2323
2424How to set up S3 storage so you can share files in Landscape.
2525
26−### [Shell](@/using/os/shell.md)
26+### [Shell](/using/os/shell)
2727
2828A comprehensive overview of `dojo` commands.
2929
30−### [Star and Galaxy Operations](@/using/os/stars-and-galaxies.md)
30+### [Star and Galaxy Operations](/using/os/stars-and-galaxies)
3131
3232How to run an infrastructure node.
3333
34−### [Ship Troubleshooting](@/using/os/ship-troubleshooting.md)
34+### [Ship Troubleshooting](/using/os/ship-troubleshooting)
3535
3636How to resolve common problems.
content/using/os/filesystem.md+4−4
@@ -10,8 +10,8 @@ referentially transparent namespace. An easy way to think about it is like typed
1010
1111The 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 pier directory.
1212
13−For more information on Clay, see the [Overview](@/docs/arvo/clay/clay.md), and
14−additional usage information at [Using Clay](@/docs/arvo/clay/using.md).
13+For more information on Clay, see the [Overview](/docs/arvo/clay/clay), and
14+additional usage information at [Using Clay](/docs/arvo/clay/using).
1515
1616### Quickstart
1717
@@ -19,7 +19,7 @@ This quick-start guide will walk you through some common commands. Follow along
1919using your Dojo. When you get a `>=` message after entering a command, this means
2020that the command was successful.
2121
22−A [`desk`](@/docs/glossary/desk.md) is something like an independently
22+A [`desk`](/docs/glossary/desk) is something like an independently
2323revision-controlled branch of your urbit's file-system. Your urbit's system
2424files live in the `%home` `desk`.
2525
@@ -291,7 +291,7 @@ Unmounts the Unix path `/generators`.
291291Merges a source `desk` into a target `desk`.
292292
293293This can optionally include a [merge
294−strategy](@/docs/arvo/clay/using.md#strategies):
294+strategy](/docs/arvo/clay/using#strategies):
295295
296296```
297297|merge %target-desk ~source-ship %source-desk, =gem %strategy
content/using/os/getting-started.md+5−5
@@ -109,7 +109,7 @@ Ctrl-y Yank from kill buffer
109109
110110### Updates
111111
112−By default, you will automatically receive updates ([OTAs](@/docs/glossary/ota-updates.md)) from your sponsor. To check your OTA source, run `|ota` in the [dojo](@/docs/glossary/dojo.md).
112+By default, you will automatically receive updates ([OTAs](/docs/glossary/ota-updates)) from your sponsor. To check your OTA source, run `|ota` in the [dojo](/docs/glossary/dojo).
113113
114114If for some reason (for example, if your sponsor is out of date), you can switch OTA sources by running `|ota ~otasrc %kids` in the dojo, where `~otasrc` is the ship from which you want to receive updates. It is a good idea to contact the source ship and ask permission to sync from them.
115115
@@ -117,7 +117,7 @@ If OTAs are not succeeding, or if you are on an version of Urbit before the `|ot
117117
118118#### Additional OTA Troubleshooting
119119Please check the Support Wiki for additional OTA troubleshooting, such as:
120−[OTA 1.0.71 failed](https://github.com/urbit/support/wiki/OTA-1.0.71-failed),
120+[OTA 1.0.71 failed](https://github.com/urbit/support/wiki/OTA-1.0.71-failed),
121121[Missing OTA](https://github.com/urbit/support/wiki/Missing-OTA),
122122[Stuck flow preventing planets from receiving
123123OTAs](https://github.com/urbit/support/wiki/Stuck-flow-preventing-planets-from-receiving-OTAs),
@@ -154,7 +154,7 @@ in this example.
154154
155155Put `<key>` in a file and that file becomes `<keyfile>`.
156156
157−You can use the resulting output in the same installation flow from the [Installing Urbit](@/getting-started/_index.md) guide, following the same scheme as for booting a planet. That scheme is:
157+You can use the resulting output in the same installation flow from the [Installing Urbit](/getting-started/) guide, following the same scheme as for booting a planet. That scheme is:
158158
159159```sh
160160$ ./urbit -w <moonname> -G <key> -c <piername>
@@ -202,7 +202,7 @@ To use the network as a planet or star, you must be sponsored by an active star
202202or galaxy, respectively. If your sponsor isn't suiting your needs, you can
203203escape to a different one. This can be done with
204204[Bridge](https://bridge.urbit.org/) following the instructions
205−[here](@/using/id/using-bridge.md#escaping-your-sponsor).
205+[here](/using/id/using-bridge#escaping-your-sponsor).
206206
207207### Continuity breaches
208208
@@ -216,7 +216,7 @@ When this happens, back up any files you'd like to save, shut down your urbit, a
216216
217217You can check your ship's _life_ and _rift_ number by running `+keys our` in
218218dojo. You can inspect another ship's life and rift number by running `+keys
219−~sampel-palnet`. For information on what life and rift are, see [Life and Rift](@/docs/azimuth/life-and-rift.md).
219+~sampel-palnet`. For information on what life and rift are, see [Life and Rift](/docs/azimuth/life-and-rift).
220220
221221## DNS proxying {#dns-proxying}
222222
content/using/os/shell.md+2−2
@@ -31,7 +31,7 @@ Tall-form Hoon may require multiple lines:
3131~your-urbit:dojo< 2
3232```
3333
34−Hoon uses something called [the subject](@/docs/hoon/hoon-school/the-subject-and-its-legs.md).
34+Hoon uses something called [the subject](/docs/hoon/hoon-school/the-subject-and-its-legs).
3535The Dojo has its own subject and that's where Hoon's equivalent of variables,
3636called faces, are stored.
3737
@@ -97,7 +97,7 @@ arguments.
9797```
9898
9999You can change your code to a new randomly generated one by entering `|code
100−%reset`. Please note that this will prevent [Bridge](@/docs/glossary/bridge.md)
100+%reset`. Please note that this will prevent [Bridge](/docs/glossary/bridge)
101101from being able to derive your code in the future.
102102
103103#### `+curl`
content/using/os/ship-troubleshooting.md+3−3
@@ -38,7 +38,7 @@ When you first start your ship, you should make sure you put it a place where yo
3838
3939### Keep up-to-date builds
4040
41−Check for latest Urbit version at https://github.com/urbit/urbit/releases. If you're behind, update using [this guide](@/getting-started/cli.md#updating).
41+Check for latest Urbit version at https://github.com/urbit/urbit/releases. If you're behind, update using [this guide](/getting-started/cli#updating).
4242
4343### `|hi` your star to see if you're connected
4444
@@ -70,7 +70,7 @@ A personal breach is when a ship tells the rest of the network to treat it as th
7070
7171Personal breaches often fix connectivity issues, but should only be used as a
7272last resort. To find out how to perform a personal breach, check out our [Guide
73−to Breaches](@/using/id/guide-to-breaches.md). Before taking such a drastic measure, try
73+to Breaches](/using/id/guide-to-breaches). Before taking such a drastic measure, try
7474other methods in this guide. You can also ask for help on
7575in the Help channel in the Urbit Community group at `~bitbet-bolbel/urbit-community` or, failing that, in the `#ship-starting-support`
7676channel in our [Discord server](https://discord.gg/n9xhMdz).
@@ -81,7 +81,7 @@ channel in our [Discord server](https://discord.gg/n9xhMdz).
8181You login to Landscape using the camel-case phrase obtained from dojo by
8282entering `+code`. For security reasons you may wish to change this code
8383regularly. You may do so by entering `|code %reset` into dojo. Doing this
84−will prevent [Bridge](@/docs/glossary/bridge.md) from being able to derive your code,
84+will prevent [Bridge](/docs/glossary/bridge) from being able to derive your code,
8585meaning you will only be able to check it from dojo in the future.
8686
8787## Operation Issues {#operation-issues}
content/using/os/stars-and-galaxies.md+3−3
@@ -6,7 +6,7 @@ aliases = ["/docs/using/operating-a-star/"]
66template = "doc.html"
77+++
88
9−To boot your galaxy or star, follow our [installation instructions](@/getting-started/_index.md).
9+To boot your galaxy or star, follow our [installation instructions](/getting-started/).
1010
1111### Hosting your star
1212
@@ -14,7 +14,7 @@ If you plan to distribute planets in any capacity, we ask that you keep your sta
1414running. If you fail to do so, those planets will become orphans that are unable
1515to communicate with the network unless they transfer to a new star.
1616
17−See our [cloud hosting instructions](@/using/running/hosting.md) for
17+See our [cloud hosting instructions](/using/running/hosting) for
1818instructions on settings up a Digital Ocean droplet.
1919
2020### Distributing planets
@@ -27,7 +27,7 @@ By default, your star accepts software updates from its galaxy and routes them t
2727
2828#### Breaches
2929
30−To ensure new planets can connect to your ship, users are expected to participate in network-wide breaches by [updating to the latest Urbit version](@/getting-started/_index.md), deleting (or archiving) your pier, and then booting your ship using the new binary. If you don’t participate, you won’t be able to communicate with anyone on the network who has updated to the new era.
30+To ensure new planets can connect to your ship, users are expected to participate in network-wide breaches by [updating to the latest Urbit version](/getting-started/), deleting (or archiving) your pier, and then booting your ship using the new binary. If you don’t participate, you won’t be able to communicate with anyone on the network who has updated to the new era.
3131
3232Network-wide breaches are distinct from personal breaches, wherein an individual ship cycles its personal network keys using Bridge, and then follows the same steps outlined above.
3333
content/using/running/_index.md+2−2
@@ -7,10 +7,10 @@ weight = 30
77+++
88
99Urbit can be run in a variety of contexts. Our [Getting Started
10−Guide](@/getting-started/_index.md) covers how to run an Urbit locally on your
10+Guide](/getting-started/) covers how to run an Urbit locally on your
1111computer; this section covers alternative ways of running Urbit.
1212
13−### [Cloud Hosting](@/using/running/hosting.md)
13+### [Cloud Hosting](/using/running/hosting)
1414
1515This guide covers the provisioning and setup of a cloud server in Digital Ocean
1616running your Urbit. This enables your Urbit to be accessed from anywhere.
content/using/running/hosting.md+10−10
@@ -11,7 +11,7 @@ The goal of this guide is to have clear and easy to follow best practices for de
1111
1212Most Urbit users start out running their ship locally on one machine in order to play with it, but this means when your machine is offline your Urbit node is offline too (and can't get updates). You can also only access your Urbit from that one machine.
1313
14−This guide uses Digital Ocean as the cloud provider, but others can be used.
14+This guide uses Digital Ocean as the cloud provider, but others can be used.
1515
1616## Create a Digital Ocean droplet
1717 - Create an account on [Digital Ocean][Digital Ocean].
@@ -30,7 +30,7 @@ This guide uses Digital Ocean as the cloud provider, but others can be used.
3030 - **Backups**: Optional (it costs a little extra, but I have it enabled for peace of mind).
3131
3232## Getting your own domain
33−Your own domain will make accessing your Urbit a lot easier (it'll also allow you to secure things with a Let's Encrypt cert). Domains are relatively inexpensive and since this guide is about best practices it's a required step.
33+Your own domain will make accessing your Urbit a lot easier (it'll also allow you to secure things with a Let's Encrypt cert). Domains are relatively inexpensive and since this guide is about best practices it's a required step.
3434
3535There are a lot of domain name registrars you can use, this guide suggests [gandi.net][Gandi]. From there you can search for and register a domain that you like.
3636
@@ -58,12 +58,12 @@ With our domain in place we're now ready to actually log into the box and start
5858 $ ssh root@your_server_ip
5959 ```
6060 - If you set a passphrase on your ssh key, you'll be asked for it. If not, you should automatically be logged in.
61− - Create a new user, in our example we'll use *sammy* (to match the DO docs), but you should use your own username:
61+ - Create a new user, in our example we'll use *sammy* (to match the DO docs), but you should use your own username:
6262 ```
6363 # adduser sammy
6464 ```
6565 - Enter a strong password for your user. The questions `adduser` asks you don't matter, hit enter to skip them.
66− - Give your new user sudo access:
66+ - Give your new user sudo access:
6767 ```
6868 # usermod -aG sudo sammy
6969 ```
@@ -82,7 +82,7 @@ Continuing to follow the DO docs we're going to configure the ufw firewall.
8282 ```
8383 $ sudo ufw app list
8484 ```
85−
85+
8686 - Next we'll configure ufw to allow connections via ssh and to allow Urbit to use the standard web port when the firewall is enabled,
8787 as well as opening a port that we'll later specify for your urbit to use to communicate directly with other ships.
8888 ```
@@ -92,7 +92,7 @@ Continuing to follow the DO docs we're going to configure the ufw firewall.
9292 $ sudo ufw allow 34543/udp
9393 ```
9494 Note that you can choose any port in place of 34543 for Ames. Just be sure to pass the same port via the `-p` option when starting your ship.
95−
95+
9696 - Next we'll turn on the firewall.
9797 ```
9898 $ sudo ufw enable
@@ -103,8 +103,8 @@ Continuing to follow the DO docs we're going to configure the ufw firewall.
103103 ```
104104
105105## Installing Urbit
106−Finally we're ready to install Urbit on your very own server. This part is actually pretty easy, if you haven't installed Urbit locally then the instructions are the exact same as the ones in the Urbit [install doc](@/getting-started/_index.md). If you have a local ship already, we're going to install Urbit on the server and then send your local ship up.
107− - **WARN**: Since Urbit is p2p you don't want to ever run two copies of your ship simultaneously. This is because other nodes that interact with each of your copies will be confused by which one is the most up to date. If you end up accidentally doing this you'll have to do a 'personal breach' described in the [guide to breaches](@/using/id/guide-to-breaches.md) to fix things.
106+Finally we're ready to install Urbit on your very own server. This part is actually pretty easy, if you haven't installed Urbit locally then the instructions are the exact same as the ones in the Urbit [install doc](/getting-started/). If you have a local ship already, we're going to install Urbit on the server and then send your local ship up.
107+ - **WARN**: Since Urbit is p2p you don't want to ever run two copies of your ship simultaneously. This is because other nodes that interact with each of your copies will be confused by which one is the most up to date. If you end up accidentally doing this you'll have to do a 'personal breach' described in the [guide to breaches](/using/id/guide-to-breaches) to fix things.
108108 - The first thing you're going to want to do is shut down your local ship, either with control-d or `|exit` in dojo.
109109 - Next we're going to install Urbit on the server and permit it to bind to the web ports:
110110 ```
@@ -139,7 +139,7 @@ Finally we're ready to install Urbit on your very own server. This part is actua
139139 - Log in with the code from `+code` in dojo like normal and you should see all of your applications.
140140
141141## Leaving your Urbit running in a Screen session
142−Finally, to leave your Urbit running after you disconnect we can leave it in a Screen session. This is just a way to leave applications running in the background and then reconnect to them later. Alternatively, the same can be done with tmux.
142+Finally, to leave your Urbit running after you disconnect we can leave it in a Screen session. This is just a way to leave applications running in the background and then reconnect to them later. Alternatively, the same can be done with tmux.
143143 - First start with your ship stopped, then run the following:
144144 ```
145145 $ screen -S urbit
@@ -166,7 +166,7 @@ On iOS you can save a website to your homescreen as an icon. If you do this for
166166 - [Digital Ocean Nginx Installation][DO Nginx Install]
167167 - [Digital Ocean Nginx Config][DO Nginx Config]
168168 - [Digital Ocean SSL Cert Setup][DO SSL Config]
169− - [Urbit Install Docs](@/getting-started/_index.md)
169+ - [Urbit Install Docs](/getting-started/)
170170 - [Urbit Basic Cloud Install][Urbit Basic Cloud Install]
171171
172172 [Gandi]: https://www.gandi.net/