git.iko.soy/urbit.org
on master help sign in
Merge branch 'update-clay-docs' of github.com:tinnus-napbus/docs into update-clay-docs
commit04c0c0fd74e543187c52a1df07e7532bd987bd4e authortinnus-napbus <admin@tinnus-napbus.xyz> dateSat 22 May 2021, 23:44 (5 years ago) parent803e3f609b3139
2 files changed+23−6
compare with master
unifiedsplit
glossary/comet.md+21−4 hoon/hoon-school/setup.md+2−2
glossary/comet.md+21−4
@@ -1,15 +1,32 @@
11+++
22title = "Comet"
3−
43template = "doc.html"
54[extra]
65category = "arvo"
76+++
87
9−A **comet** is a kind of [ship](../ship) on the [Arvo](../arvo) network. They are disposable identities that will not be initially trusted by others on the network. One use might be to run bots as comets.
8+A **comet** is a kind of [ship](../ship) on the [Ames](../ames) network which
9+may be quickly generated by anyone and which are virtually unlimited. They have
10+many uses, including but not limited to:
11+- free identities for new users to try things out before deciding to purchase a [planet](../planet).
12+- bots
13+- remaining anonymous
14+- testing software
15+
16+Comets have nearly all the same capabilities as a planet. The restrictions they
17+do possess are technical constraints of the system due primarily to the fact that they
18+have no presence on [Azimuth](../azimuth), rather than purposefully placed
19+blockades.
20+ - They may not [change their networking keys](../bridge).
21+ - They may not spawn [moons](../moon).
22+ - They must initiate all direct messages with other ships.
23+The last constraint has a workaround slated. If you wish to change your
24+networking keys, we suggest generating a new comet. Moons are impossible for
25+comets due to the structure of the address space.
26+
27+Some groups on [Landscape](../landscape) may not allow comet membership, but this is rare.
1028
11−Comets have no presence on [Azimuth](../azimuth) and thus have no associated Urbit identities.
1229
1330### Further reading
1431
15−- [Creating a Comet](@/getting-started/_index.md#comet): A guide to spinning up a comet of your own.
32+- [Creating a Comet](@/getting-started/_index.md): A guide to spinning up a comet of your own.
hoon/hoon-school/setup.md+2−2
@@ -17,7 +17,7 @@ These may not look like numbers, but they are. Each urbit name is written in a b
1717
1818You can install Urbit on any Mac or Unix machine; if you're just trying out Urbit or creating a development ship, you can follow the steps for creating a development ship [here](@/docs/development/environment.md). On Windows, make a virtual Linux machine using VirtualBox or a similar tool.
1919
20−Once you're finished, you can [boot your very own ship](@/getting-started/_index.md#comet). While you can develop in Hoon on your own ship on the live network, we strongly suggest developing on a development ship first.
20+Once you're finished, you can [boot your very own ship](@/getting-started/_index.md). While you can develop in Hoon on your own ship on the live network, we strongly suggest developing on a development ship first.
2121
2222## Getting started
2323
@@ -67,7 +67,7 @@ You asked Dojo to evaluate `17` and it echoed the number back at you. This value
6767
6868Generators are the most straightforward way to write Hoon programs. They are a concept in Arvo, and involve saving Hoon code in a `.hoon` text file. While they aren't strictly part of the Hoon language, we'll be dealing with generators throughout this tutorial.
6969
70−The simplest type of generator is the **naked generator**. All naked generators are `gates`: functions that take an argument and produce an output. Before creating a generator you need to [mount](@/getting-started/_index.md#the-dojo) your `desk` to Unix. To create a generator, all you need to do is write a `gate` and put it into a file in the `/home/gen/` directory of your ship as a `.hoon` file. (Assuming you've already mounted with `|mount /=home=`.) After this, you need to run `|commit %home` in Dojo and the new file will be recognized by your ship. To run a generator named `mygen.hoon`, you would type `+mygen <argument>` in your ship's Dojo.
70+The simplest type of generator is the **naked generator**. All naked generators are `gates`: functions that take an argument and produce an output. Before creating a generator you need to [mount](@/getting-started/_index.md) your `desk` to Unix. To create a generator, all you need to do is write a `gate` and put it into a file in the `/home/gen/` directory of your ship as a `.hoon` file. (Assuming you've already mounted with `|mount /=home=`.) After this, you need to run `|commit %home` in Dojo and the new file will be recognized by your ship. To run a generator named `mygen.hoon`, you would type `+mygen <argument>` in your ship's Dojo.
7171
7272If this doesn't make sense yet, that's okay. In the [next lesson](@/docs/hoon/hoon-school/list-of-numbers.md), we will walk you through an example `gate` that is run as a generator.
7373