on master help sign in
add planet guide and blog post
commit62cf44621fa8ad2003a22e58546ad53db078cd2d authorJames Acklin <james@tlon.io> dateFri 11 Feb 2022, 13:26 (5 years ago) parentec1e494
6 files changed+304−29
content/blog/layer-2-guides.md+52 content/getting-started/_index.md+1−1 content/getting-started/cli.md+1−1 content/getting-started/layer-2-for-planets.md+104 content/getting-started/planet.md+1−1 public/rss.xml+145−26
content/blog/layer-2-guides.mdnew file+52
@@ -0,0 +1,52 @@
1++++
2+title = "Layer 2 Guides"
3+date = "2022-02-14"
4+description = "Urbit’s Layer 2 system is live and operational."
5+[extra]
6+author = "Reid Scoggin"
7+ship = "~sitful-hatred"
8+image = "https://storage.googleapis.com/media.urbit.org/site/posts/essays/romi%20creators%20blog.jpeg"
9++++
10+
11+Urbit’s [Layer 2](https://urbit.org/docs/azimuth/l2/layer2) system, naive rollups, allows planets to be spawned at substantially lower cost. This system operates in parallel to Layer 1 Azimuth, but introduces some new concepts and differences that are important to understand. Read on for a high-level survey, and check the star and planet guides linked at the bottom for details and instructions.
12+
13+After a year of development and testing, **Urbit’s Layer 2 system is live and operational**. Star and planet operators can now take advantage of subsidized Azimuth operations. If you operate a star, you can distribute planets cheaply or for free; if you’ve been waiting to buy an ID due to transaction fees, you will find planets are available much more cheaply.
14+
15+Layer 2 (“L2”) introduces some changes that are important to understand, whether you’re new to the network or not. Stars and planet operators that are considering migrating to L2 have different **trade-offs to weigh** before they make a decision.
16+
17+### Background
18+
19+Urbit can be broadly divided into two parts: an operating system, Arvo, and the identity layer, Azimuth. These two systems are interlocked. Arvo uses Azimuth to verify that you own an address, which maps to your name on the network. [Azimuth](https://urbit.org/docs/glossary/azimuth) is a public key infrastructure, implemented as contracts on the Ethereum blockchain. Modifications to the ownership or properties of an identity’s keys are recorded on Ethereum. Azimuth faithfully serves its purpose as an authoritative, trustless registry of ownership, but it inherits both the strengths and disadvantages of the ETH ecosystem.
20+Due to ETH’s value and popularity, performing transactions directly on the Ethereum blockchain (‘Layer 1’) has become prohibitively expensive for many simple operations. The Ethereum smart contracts that control the logic of Azimuth were developed in a time when ETH was not worth as much. The soaring value of ETH means that the gas fee to spawn or modify a planet routinely costs more than the planet itself. Azimuth is not unique in this regard. All projects built on Ethereum have had to deal with this issue in one form or another. Fortunately, Urbit engineers have come up with a solution for those seeking to get onto the network, albeit with several important trade-offs.
21+
22+### Naive rollups
23+
24+‘Layer 2’ refers to technologies built on top of blockchains to enable scaling. [Rollups](https://vitalik.ca/general/2021/01/05/rollup.html) are an Ethereum ecosystem Layer 2 innovation that reduces costs by moving computation off-chain. _Naive rollups_ are a bespoke technology developed for Urbit that augment the original Azimuth contracts. For technical details, you can review the [excellent summary](https://urbit.org/blog/rollups) by `~datnut-pollen`, or the [original proposal](https://groups.google.com/a/urbit.org/g/dev/c/p6rP_WsxLS0) by `~wicdev-wisryt`. In brief: rather than using the Ethereum network to perform the computation associated with PKI modifications (Layer 1), the computation is performed on the Urbit network itself, with the results published to the blockchain by nodes called rollers. Signed data resulting from the combined transactions is posted on a regular basis to the main blockchain by the rollers. Due to this batched, off-chain computation, fees are roughly **65-100x cheaper** than Layer 1 operations.
25+
26+### What everyone should know
27+
28+Whether you’re new to the network or a longtime participant, you should gain familiarity with the new changes. There are a few things that everyone should know:
29+
30+- All ships spawned before now have been on Layer 1 – those ships have the option of migrating to Layer 2, or remaining on Layer 1.
31+- **You don’t have to do anything**. Migrating is opt-in, and a Layer 1 ship will continue to have full functionality on the network.
32+- Layer 2 lets you perform **Azimuth transactions cheaply or for free**. If you operate a star, you can spawn planets for free with Tlon’s roller. Planets can make use of Tlon’s roller for actions like factory resets and transferring ownership and proxy addresses for free.
33+- **Migrating is one-way**. If you migrate to Layer 2, there is not currently an option to reverse your decision.
34+- **Migrating does not change which address owns a point**. After migrating, you will still log into Bridge with the same keys.
35+
36+### Layer 2 guides
37+
38+There’s lots more to learn about the new solution. These updates apply to the software on your ship, the Azimuth PKI, and new features and major updates to Bridge. You can learn more in the following guides, with in-depth background and illustrated walkthroughs for common tasks:
39+
40+[Layer 2 for stars](placeholder) – It’s particularly important for star operators to understand the pros and cons of migrating. This guide will explain the technical background, trade-offs, and how to use Layer 2 on Bridge.
41+
42+- Stars can migrate their spawn proxy to Layer 2 to spawn up to six planets per week for free using Tlon’s roller.
43+- Stars can migrate their ownership key to Layer 2 to perform all Azimuth operations on Layer 2, including planet spawning, factory resets, and point adoption.
44+- Migrating is currently a one-way process and cannot be reversed.
45+- Layer 2 stars cannot be wrapped as $WSTR tokens, or interact with any other Layer 1 tools or contracts (e.g. MetaMask, OpenSea).
46+
47+[Layer 2 for planets](placeholder) – Just bought a planet and want to know what all of this means for you? Wondering whether you should migrate your Layer 1 planet? Look here for guidance.
48+
49+- Planets spawned by a Layer 2 star will spawn on Layer 2.
50+- Migration is one-way; if your planet is on Layer 2, there is no way to migrate it to Layer 1.
51+- Planets on Layer 2 can take advantage of subsidized, free Azimuth transactions using Tlon’s roller.
52+- Planets on Layer 2 cannot currently interact with Layer 1 tools or contracts like MetaMask or OpenSea.
content/getting-started/_index.md+1−1
@@ -1,6 +1,6 @@
11+++
22title = "Getting Started"
3−weight = 1
3+weight = 0
44description = "How to install Urbit."
55page_template = "page_indiced.html"
66template = "getting-started/index.html"
content/getting-started/cli.md+1−1
@@ -1,6 +1,6 @@
11+++
22title = "Command line install"
3−weight = 2
3+weight = 4
44description = "Installation instructions for power users."
55+++
66
content/getting-started/layer-2-for-planets.mdnew file+104
@@ -0,0 +1,104 @@
1++++
2+title = "Layer 2 for planets"
3+weight = 3
4+description = "Getting started with a permanent Urbit identity."
5++++
6+
7+What does Layer 2 mean for planets? Cheap transaction fees which make it inexpensive to get on the network and stay on the network.
8+
9+Performing transactions directly on the Ethereum blockchain, ‘Layer 1’, has become prohibitively expensive over the past year due to ETH’s value and network congestion. As a result, spawning a planet or performing simple operations in Bridge can be very costly. Urbit’s [Layer 2](https://urbit.org/docs/azimuth/l2/layer2) solution, called [naive rollups](https://urbit.org/blog/rollups), makes performing these transactions cheap or free. Planets can take advantage of this in the form of cheaper planet prices, as well as cheap or free Azimuth transactions.
10+
11+### What to know
12+
13+- Migration is currently **one-way**.<br />You cannot move a Layer 2 ID back to Layer 1. This includes planets that are spawned on Layer 2.
14+- You cannot interact with Layer 2 IDs using Layer 1 tools like OpenSea or Metamask.<br />You will not be able to use your ID with smart contracts, or ‘see’ it using wallets other than Bridge. **Bridge is currently the only software that can see or interact with Layer 2 IDs.**
15+- Layer 2 does not have anything to do with networking between ships.<br>Operating your ship on the network will not be influenced by which layer it is on. You will be fully capable of communicating with ships on either layer.
16+- You can perform Layer 2 transactions for free with Tlon’s roller.<br>A public roller operated by Tlon is connected to Bridge by default, but anyone can operate a roller. Tlon’s roller offers free subsidized transactions up to a weekly limit of 25 operations.
17+- You will need to pay for the migration to L2.<br>Migrating is a one-time process that takes place on Layer 1. You will need to fund it in the same way as a traditional Layer 1 Azimuth transaction.
18+- Your star sponsor can be on either layer.<br>The layer that a star is on has no bearing on who it can sponsor.
19+
20+If you already had a planet before the launch of L2, you don’t have to do anything. Your ship will continue to function normally and you will still be able to communicate with the entire network without any additional intervention. However, you have the option of migrating your planet to Layer 2 in order to take advantage of the reduced costs and subsidized transactions available through Tlon’s roller.
21+
22+### Should I move?
23+
24+If you have a planet on Layer 1, migrating is entirely optional. The **benefits** of migrating a planet to Layer 2 are free or cheap Azimuth transactions. Ships on Layer 2 can use Tlon’s roller to perform operations in Bridge for free up to a weekly limit. These operations might be resetting networking keys, or changing sponsors.
25+
26+The **trade-offs** for migrating a planet to Layer 2 include:
27+
28+- The migration process is currently irreversible. If you migrate to Layer 2, you cannot go back to Layer 1.
29+- Ships on Layer 2 are not visible to Layer 1 tools like wallets or chain explorers; Bridge is currently the only software that can ‘see’ Layer 2 IDs.
30+
31+### Which Layer am I on?
32+
33+You can tell at a glance which layer your asset occupies in Bridge:
34+
35+1. Log into Bridge.
36+2. Click the ownership address modal at the top left of the main menu.
37+3. A square icon with ‘L1’ or ‘L2’ will show up next to each asset that belongs to your address.
38+
39+A single ownership address can own ships on both Layer 1 and Layer 2.
40+
41+### Migrating
42+
43+![placeholder -- image]()
44+
45+To migrate:
46+
47+1. Log into Bridge.
48+2. Click the ownership address modal menu at the top left corner.
49+3. Select ‘Migrate’, and ‘Proceed’ after reading the information presented.
50+4. You will need to pay a one-time fee to fund the transaction; make sure your L1 address has funds available.
51+
52+Migrating to Layer 2 does not change the address that owns a point. **You will still use the same wallet or key to log into Bridge after migration**. A single ownership address might have ships on both Layer 1 and Layer 2.
53+
54+The migration itself does not need to be submitted to a roller – it should complete within a few minutes. Once it has, you can submit planets and transactions to the roller’s queue immediately.
55+
56+### Activating a Layer 2 planet
57+
58+![placeholder -- image]()
59+
60+**Planet codes** are one-time passphrases used to claim a master ticket through Bridge. These can be standalone text phrases, or embedded in a URL that begins with `bridge.urbit.org`. **Master tickets** are passphrases used to log into Bridge to manage an ID that has already been claimed.
61+
62+If you’ve been given a planet code invitation URL to claim a planet:
63+
64+1. Open the link.
65+2. Click ‘Claim’.
66+3. Reveal the master ticket code. Write this down somewhere safe.
67+4. Confirm you’ve written the code down by typing it back into the prompt.
68+5. Click to download your passport, which contains the keyfile you will use for your ship’s first boot.
69+
70+If you’ve been given a four-word text activation code, go to [Bridge](https://bridge.urbit.org/) and click ‘Activate a planet’ at the bottom. Enter your planet code, and follow the instructions above.
71+
72+In the future, you can log into Bridge using the master ticket you wrote down in order to manage your ship’s keys. Knowing the master ticket is equivalent to owning the ID, so keep it somewhere secure.
73+
74+An important consideration for new users with regard to Layer 2 planets: your ownership key is technically exposed to the star that issued your planet for up to 24 hours, until the next batch is processed by your roller. During this window, it's technically possible for the issuer to take back the planet or decrypt packets meant for it. This is the reason that the keyfile you use to boot your ship actually has two halves – one for your initial boot, and a second one that belongs solely to you.
75+
76+The first time you boot, the key from the first half of the keyfile is used; but when the next roll batch is processed, the ID will be modified with a second key. This key is kept secret from the star that spawned you, and once this transaction clears, your planet is definitively and cryptographically yours. All of this is **taken care of in the background and requires no intervention**. You don’t even need to restart your planet after the ownership transfer has been finalized.
77+
78+### Running your planet
79+
80+Once you’ve activated your planet and downloaded your keyfile, you can use it to boot your ship immediately.
81+
82+If you’re running your planet on a local PC:
83+
84+1. Extract the zipped file you downloaded from Bridge.
85+2. Download [Port](https://urbit.org/getting-started#port) and run the installer.
86+3. Click ‘Boot menu’, and select ‘Planet’.
87+4. Enter a friendly name, the `@p` of your planet, and click ‘Browse’ to navigate to the keyfile you downloaded.
88+5. Click ‘Continue’ to boot your planet.
89+
90+Treat your planet like the precious object it is. Do not share your landscape login code or master key with anybody. Never run it in two places at the same time. This will knock it out of sequence with the network, and cause it to become ‘brain damaged’, unable to communicate with the outside world. Don’t delete the directory that contains your asset’s data. If you are shutting down your ship for a while, keep the data folder somewhere safe, and you can pick up where you left off in the future.
91+
92+You may also opt to [host your planet](https://urbit.org/getting-started#hosting-providers) with a provider. Ships hosted by providers are always-on and come with support. After you’ve activated your planet code, but before you’ve booted with your keyfile, you can create an account with a hosting provider like [UrbitHost](https://urbithost.com/) and use your keyfile to boot your ship with their service – known as ‘bring your own planet’.
93+
94+In addition to importing a fresh planet, UrbitHost allows you to migrate an existing pier to your hosted account. If you’ve booted a planet on your PC but want to make the switch to hosting, you can upload it and hit the ground running without having to reset your networking keys.
95+
96+### Transaction history
97+
98+![placeholder -- image]()
99+
100+A new feature in Bridge is the ability to see the transaction history of your asset. This is particularly important because with Layer 2, much of the Azimuth state is no longer visible on the Ethereum blockchain, but is maintained by the Urbit network. This means you might not be able to directly observe “who owns what” by looking at the Azimuth contracts with something like a [blockchain explorer](https://etherscan.io/address/azimuth.eth). Activities like setting networking keys, issuing planets, or moving your proxy keys will show up in this log. Note that the transaction history menu in Bridge is currently the only way to examine Azimuth operations that take place on Layer 2.
101+
102+If you submit an operation to your roller, you’ll see a timer counting down to the next batch and a history of completed operations. Bridge does not currently allow you to cancel a transaction once it has been submitted.
103+
104+Incoming transfers of new assets will also show up in your transaction history. If your ownership address owns more than one asset, you can use the modal to select from among them.
content/getting-started/planet.md+1−1
@@ -1,6 +1,6 @@
11+++
22title = "Setting up your urbit"
3−weight = 1
3+weight = 2
44description = "Getting started with a permanent Urbit identity."
55+++
66
public/rss.xml+145−26
@@ -4,10 +4,105 @@
44 <title>Urbit</title>
55 <link>https://urbit.org</link>
66 <description>Urbit is a personal server built from scratch</description>
7− <lastBuildDate>Wed, 08 Dec 2021 19:13:57 GMT</lastBuildDate>
7+ <lastBuildDate>Fri, 11 Feb 2022 18:17:26 GMT</lastBuildDate>
88 <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
99 <generator>https://github.com/jpmonette/feed</generator>
1010 <language>en</language>
11+ <item>
12+ <title><![CDATA[Layer 2 Guides]]></title>
13+ <link>https://urbit.org/blog/layer-2-guides</link>
14+ <guid>https://urbit.org/blog/layer-2-guides</guid>
15+ <pubDate>Mon, 14 Feb 2022 05:00:00 GMT</pubDate>
16+ <content:encoded><![CDATA[
17+Urbit’s [Layer 2](https://urbit.org/docs/azimuth/l2/layer2) system, naive rollups, allows planets to be spawned at substantially lower cost. This system operates in parallel to Layer 1 Azimuth, but introduces some new concepts and differences that are important to understand. Read on for a high-level survey, and check the star and planet guides linked at the bottom for details and instructions.
18+
19+After a year of development and testing, **Urbit’s Layer 2 system is live and operational**. Star and planet operators can now take advantage of subsidized Azimuth operations. If you operate a star, you can distribute planets cheaply or for free; if you’ve been waiting to buy an ID due to transaction fees, you will find planets are available much more cheaply.
20+
21+Layer 2 (“L2”) introduces some changes that are important to understand, whether you’re new to the network or not. Stars and planet operators that are considering migrating to L2 have different **trade-offs to weigh** before they make a decision.
22+
23+### Background
24+
25+Urbit can be broadly divided into two parts: an operating system, Arvo, and the identity layer, Azimuth. These two systems are interlocked. Arvo uses Azimuth to verify that you own an address, which maps to your name on the network. [Azimuth](https://urbit.org/docs/glossary/azimuth) is a public key infrastructure, implemented as contracts on the Ethereum blockchain. Modifications to the ownership or properties of an identity’s keys are recorded on Ethereum. Azimuth faithfully serves its purpose as an authoritative, trustless registry of ownership, but it inherits both the strengths and disadvantages of the ETH ecosystem.
26+Due to ETH’s value and popularity, performing transactions directly on the Ethereum blockchain (‘Layer 1’) has become prohibitively expensive for many simple operations. The Ethereum smart contracts that control the logic of Azimuth were developed in a time when ETH was not worth as much. The soaring value of ETH means that the gas fee to spawn or modify a planet routinely costs more than the planet itself. Azimuth is not unique in this regard. All projects built on Ethereum have had to deal with this issue in one form or another. Fortunately, Urbit engineers have come up with a solution for those seeking to get onto the network, albeit with several important trade-offs.
27+
28+### Naive rollups
29+
30+‘Layer 2’ refers to technologies built on top of blockchains to enable scaling. [Rollups](https://vitalik.ca/general/2021/01/05/rollup.html) are an Ethereum ecosystem Layer 2 innovation that reduces costs by moving computation off-chain. _Naive rollups_ are a bespoke technology developed for Urbit that augment the original Azimuth contracts. For technical details, you can review the [excellent summary](https://urbit.org/blog/rollups) by `~datnut-pollen`, or the [original proposal](https://groups.google.com/a/urbit.org/g/dev/c/p6rP_WsxLS0) by `~wicdev-wisryt`. In brief: rather than using the Ethereum network to perform the computation associated with PKI modifications (Layer 1), the computation is performed on the Urbit network itself, with the results published to the blockchain by nodes called rollers. Signed data resulting from the combined transactions is posted on a regular basis to the main blockchain by the rollers. Due to this batched, off-chain computation, fees are roughly **65-100x cheaper** than Layer 1 operations.
31+
32+### What everyone should know
33+
34+Whether you’re new to the network or a longtime participant, you should gain familiarity with the new changes. There are a few things that everyone should know:
35+
36+- All ships spawned before now have been on Layer 1 – those ships have the option of migrating to Layer 2, or remaining on Layer 1.
37+- **You don’t have to do anything**. Migrating is opt-in, and a Layer 1 ship will continue to have full functionality on the network.
38+- Layer 2 lets you perform **Azimuth transactions cheaply or for free**. If you operate a star, you can spawn planets for free with Tlon’s roller. Planets can make use of Tlon’s roller for actions like factory resets and transferring ownership and proxy addresses for free.
39+- **Migrating is one-way**. If you migrate to Layer 2, there is not currently an option to reverse your decision.
40+- **Migrating does not change which address owns a point**. After migrating, you will still log into Bridge with the same keys.
41+
42+### Layer 2 guides
43+
44+There’s lots more to learn about the new solution. These updates apply to the software on your ship, the Azimuth PKI, and new features and major updates to Bridge. You can learn more in the following guides, with in-depth background and illustrated walkthroughs for common tasks:
45+
46+[Layer 2 for stars](placeholder) – It’s particularly important for star operators to understand the pros and cons of migrating. This guide will explain the technical background, trade-offs, and how to use Layer 2 on Bridge.
47+
48+- Stars can migrate their spawn proxy to Layer 2 to spawn up to six planets per week for free using Tlon’s roller.
49+- Stars can migrate their ownership key to Layer 2 to perform all Azimuth operations on Layer 2, including planet spawning, factory resets, and point adoption.
50+- Migrating is currently a one-way process and cannot be reversed.
51+- Layer 2 stars cannot be wrapped as $WSTR tokens, or interact with any other Layer 1 tools or contracts (e.g. MetaMask, OpenSea).
52+
53+[Layer 2 for planets](placeholder) – Just bought a planet and want to know what all of this means for you? Wondering whether you should migrate your Layer 1 planet? Look here for guidance.
54+
55+- Planets spawned by a Layer 2 star will spawn on Layer 2.
56+- Migration is one-way; if your planet is on Layer 2, there is no way to migrate it to Layer 1.
57+- Planets on Layer 2 can take advantage of subsidized, free Azimuth transactions using Tlon’s roller.
58+- Planets on Layer 2 cannot currently interact with Layer 1 tools or contracts like MetaMask or OpenSea.
59+]]></content:encoded>
60+ </item>
61+ <item>
62+ <title><![CDATA[Urbit Is for Creators]]></title>
63+ <link>https://urbit.org/blog/urbit-for-creators</link>
64+ <guid>https://urbit.org/blog/urbit-for-creators</guid>
65+ <pubDate>Thu, 09 Dec 2021 00:00:00 GMT</pubDate>
66+ <content:encoded><![CDATA[
67+![](https://storage.googleapis.com/media.urbit.org/site/posts/essays/romi%20creators%20blog.jpeg)
68+
69+It’s no secret that there are huge problems with the way content is distributed on the internet today. Even five years ago these issues hadn’t quite hit the mainstream: the ability of platforms to capriciously alter their terms of service, the corrosive effects of algorithms designed to siphon off as much of our attention as possible, the uncanny effects of a world where tech companies arbitrate truth with behind-the-scenes moderation policies. Although they’re now discussed pretty openly, the horrid effects of this system actually tend to be _understated._ “If you’re not paying for it, you’re not the customer, you’re the product” has become a truism. And yet, as _You Are Not a Gadget_ author Jaron Lanier puts it, it’s not quite specific enough to say that _you_ are the product. Rather, “it’s the gradual, slight, imperceptible change in your own behavior and perception that is the product.”
70+
71+This product is selling very well, and it has seeped its way fully into the world of content creation, or what might once have been called the arts. Although it’s not so widely publicized, [Tik Tok basically runs the popular music industry at this point](https://www.browndailyherald.com/article/2021/09/for-better-or-worse-tiktok-is-driving-the-music-industry). Meanwhile, platforms like Spotify or YouTube filter what we see by deprecating the “long tails” of content. That is, if you’re searching for a tune on Spotify, it brings Spotify more profit, on average, to design a search feature that will automatically bring you to the most popular songs, even if you were really looking for less popular ones. The same goes for books, which are now purchased mostly according to the algorithm, and not according to what a person might stumble upon in a bookshop. (The upshot: expect more [cookbooks from Snoop Dogg](https://www.nytimes.com/2021/04/18/books/book-sales-publishing-pandemic-coronavirus.html), and fewer titles from authors who are not already celebrities.) Products such as Tik Tok, Spotify, YouTube, and Amazon like for you to think that they’re mere distributors of content. But actually they’re _producers_, and they’re producing the smarmy, anodyne style that has homogenized the globe.
72+
73+Urbit is for creators who are ready to wake up from this bad dream.
74+
75+The vibe of today’s internet applications—manipulative, erratic, overcomplicated, overbearing, and highly detrimental to society—is in contrast to the mechanics of the creator economy itself, which can actually be blissfully simple. In 2008 Kevin Kelley made famous the concept of “[1000 true fans](https://kk.org/thetechnium/1000-true-fans/).” That is, to make a living as a creator, you only need 1,000 fans who are interested enough to buy whatever you produce. Even $6.00 or $7.00 a month from such true fans is a boon for a creator—assuming not too much of that cash gets taken away by middlemen, and that fans can discover work from outside the corporate monoculture in the first place.
76+
77+In a limited sense, this 1,000 true fans model is already working. Creators with fanbases of the size Kelly imagined are able to use Patreon or YouTube or what-have-you to monetize their content. But the problem is, those platforms are not really peer-to-peer. Your fans aren’t your own: they belong to the platform. And with the big tech platforms running the show, we end up with the problems described above.
78+
79+To those of us who are interested in seeing a thriving culture of artists, musicians, podcasters and writers which is human-centered via a p2p network, rather than being brokered, managed, and manipulated, by the most venal and tasteless of data collectors and profiteers, it likely seems like the world of the arts has gone bottom-up. Urbit is for any creators who are ready to put it back on its feet again.
80+
81+Urbit is a peer-to-peer network designed to serve as simple, durable neutral infrastructure for whoever wants to build something on it. Like everything else on Urbit, creator content goes directly to the people it’s supposed to go to. No middlemen, no MEGACORP data mining, no capricious terms of service, no obscure algorithms determining what gets seen and what doesn’t. This is the zero-to-one shift that makes Urbit the natural destination for creators who want to both _own_ their work and share it.
82+
83+Urbit has already seen several communities get excited about the ways Urbit could help them fulfill their goals. Here are just a few examples:
84+
85+[HOLDERSLAND](https://twitter.com/holdersland), founded by Haleek Maul, a musician, music label owner, and NFT creator based in Barbados. Maul recently [sold](https://urbit.holders.land) a set of customized Urbit NFT artwork, which came bundled with actual Urbit IDs.
86+
87+[Other Life](https://www.otherlife.co), a community of philosophers and creators founded by the entrepreneurial Justin Murphy.
88+
89+[The Stack](https://orbisledger.news/), an entertaining and informative podcast with a decidedly Urbit flavor, hosted by Josh and Andy.
90+
91+[door.link](https://www.door.link), a vibey and idiosyncratic music collective.
92+
93+[Wet Brain](https://www.patreon.com/wetbrain), a numinous, post-everything New York podcast, hosted by Honor and Walt.
94+
95+Internet Weirdness Task Force, which has no legacy internet site to link to, so you’ll just have to get on Urbit to scope it out.
96+
97+Over the last ten years, we’ve already had a taste of what blockchains can do: they’re great so far for distributing a financial ledger so that payments are no longer centralized. But for online communities to go truly peer-to-peer and escape the grip of corporations, they’re going to need something like Urbit. As HOLDERSLAND founder Haleek Maul [puts it](https://urbit.org/blog/haleek-maul-interview) in a recent Q&A, decentralized technologies like blockchain or Urbit “allow . . . new financial relationships and funding structures to emerge. Rather than have a few people contribute $20k, you can have hundreds of people contribute $100.” In such a system, recording artists no longer need to hunt for a deal from sharky impresarios; their communities can comprise both the talent _and_ the executives. They no longer need to pay fealty to streaming services; they can sell their wares peer-to-peer, with the old-fashioned connoisseurship of a cool record shop, except that this record shop is available to anyone across the globe.
98+
99+Urbit makes this dream a real possibility. In an Urbit future, utilizing your own personalized payments system, which could take either fiat or crypto, should be as easy as sending or receiving money on apps like Venmo or Cash App is today. If _anyone_ can make a direct peer-to-peer payment to anyone else on the network, if _anyone_ can send a piece of writing or audio or video clip in a peer-to-peer way to anyone else on the network, then you’ve truly laid the groundwork for autonomous organizations of creators.
100+
101+Beyond that, Urbit is one of the very few platforms looking, with seriousness and deep technical consideration, into the distant future. Whereas no one can say whether a mainstream platform like Facebook or Twitter will even _exist_ in ten years (think just how much writing will disappear if those servers do shut down), Urbit is built with maximum durability in mind: one way to think of your urbit computer is as a [100-year computer](https://urbit.org/blog/the-100-year-computer). Whereas most software today is designed to break quickly and be replaced quickly, due to the instability of all of modern computing’s complex interlocking parts, Urbit was built as an overlay operating system, so that it can work no matter what’s running underneath, and thus serve as a resilient, permanent home for your digital world.
102+
103+Computers can still be used as magical tools for creative individuals, instead of as attention-draining machines—if that is indeed the future we want. For creators, the solution to the ever-growing problems of the internet is not in the hands of any national government, or some new application that mimics the architecture of old applications, or through some impracticable system of reduced screen time. The solution to these problems is, and always has been, to build a whole new system that works _for_ the people instead of against them. That’s what Urbit is here to do.
104+]]></content:encoded>
105+ </item>
11106 <item>
12107 <title><![CDATA[Report from the field: Assembly 2021]]></title>
13108 <link>https://urbit.org/blog/2021-11-18-report-from-the-field</link>
@@ -17667,6 +17762,29 @@ We'll meet at the Sibley Staging Area at 3:00PM, and leave for a casual walk to
1766717762Hiking shoes, snacks, water, and picnic blankets/chairs are encouraged! There are restrooms and water at the Staging Area.
1766817763
1766917764Please join the channel 'Urbit Outside ~[masked]' in ~bitbet-bolbel/urbit-community to get in touch with the gang.
17765+]]></content:encoded>
17766+ </item>
17767+ <item>
17768+ <title><![CDATA[Developer Call: Urbit Visor - Transforming the Web Browser Into an Urbit Client]]></title>
17769+ <link>https://urbit.org/events/2021-10-07-developer-call-visor</link>
17770+ <guid>https://urbit.org/events/2021-10-07-developer-call-visor</guid>
17771+ <pubDate>Invalid Date</pubDate>
17772+ <content:encoded><![CDATA[
17773+Please join us for a deep dive into Urbit Visor, a brand new web extension which transforms your browser into a first class Urbit client. Robert Kornacki from dcSpark will be taking viewers step-by-step through the history of how Urbit Visor came to be, starting off with his initial work on the Rust airlock implementation, moving into Login With Urbit, and finally arriving at the final product of Urbit Visor that we have today.
17774+
17775+From there Robert will hit on many topics including:
17776+
17777+- Live demonstration of how Urbit Visor works
17778+- How Urbit Visor improves and increases the security of the Landscape login experience
17779+- An overview of the first Urbit Web App: Urbit Dashboard
17780+- Ship hot-swapping
17781+- Streamlining the developer experience for any JS/TS dev to jump into the ecosystem and start building immediately
17782+- UV Extensions and how they will allow Urbit and the current web to integrate seamlessly
17783+- The long term goals and vision of Urbit Visor
17784+
17785+Robert Kornacki (~mocrux-nomdep) is CSO at dcSpark and has been in the Urbit ecosystem since 2019. Robert has significant experience working in the crypto industry over the past several years, developing tooling and smart contract protocols which hold millions of dollars of assets to this day.
17786+
17787+Hosted by Josh Lehman, the Director of the Urbit Foundation.
1767017788]]></content:encoded>
1767117789 </item>
1767217790 <item>
@@ -17707,6 +17825,21 @@ Join us for the Assembly 2021 introduction, keynote and demos on Saturday, Octob
1770717825 <pubDate>Invalid Date</pubDate>
1770817826 <content:encoded><![CDATA[
1770917827We wish we could get everyone together at once for Assembly, but travel still isn't as easy as we wish it was. For those that can't make it to Assembly, join Urbit Foundation Director and Tlon CPO Josh Lehman for an online-only AMA about Urbit's new software distribution capabilities.
17828+]]></content:encoded>
17829+ </item>
17830+ <item>
17831+ <title><![CDATA[Developer Call: Running a Hosting Provider]]></title>
17832+ <link>https://urbit.org/events/2021-10-28-developer-call-hosting</link>
17833+ <guid>https://urbit.org/events/2021-10-28-developer-call-hosting</guid>
17834+ <pubDate>Invalid Date</pubDate>
17835+ <content:encoded><![CDATA[
17836+As many of you know, Urbit runs best when hosted, seeing that it's a server and all. The problem of course is that hosting an Urbit ship isn't the easiest of things to do for most people. Hosting Urbit ships in production is actually pretty tough though—doing it right requires wrangling the complexity of traditional "Earth" infrastructure in addition to a strong sense of how Urbit works.
17837+
17838+In this call we're joined by Brendan Hay, the lead behind Tlon Hosting, and Lukas Bühler of UrbitHost, in what's sure to be an entertaining and informative conversation. Bren and Lukas have both been the masterminds behind their respective hosting architectures, and were somewhat surprised to learn that they'd independently settled on highly similar architectures.
17839+
17840+This will be an unscripted conversation that's sure to span a gamut of topics including, but not limited to: the unique technical challenges of hosting Urbit ships, the upcoming %khan vane, Kubernetes operators, product roadmaps, custodianship of (or plans to do away with) private keys, and probably a ton more.
17841+
17842+Hosted by Josh Lehman, the Director of the Urbit Foundation.
1771017843]]></content:encoded>
1771117844 </item>
1771217845 <item>
@@ -17729,41 +17862,27 @@ Come along and learn about the Urbit with us. You will gain access to an eldritc
1772917862]]></content:encoded>
1773017863 </item>
1773117864 <item>
17732− <title><![CDATA[Developer Call: Urbit Visor - Transforming the Web Browser Into an Urbit Client]]></title>
17733− <link>https://urbit.org/events/20211007-developer-call-visor</link>
17734− <guid>https://urbit.org/events/20211007-developer-call-visor</guid>
17865+ <title><![CDATA[Meetup: Austin]]></title>
17866+ <link>https://urbit.org/events/2022-01-21-meetup-austin</link>
17867+ <guid>https://urbit.org/events/2022-01-21-meetup-austin</guid>
1773517868 <pubDate>Invalid Date</pubDate>
1773617869 <content:encoded><![CDATA[
17737−Please join us for a deep dive into Urbit Visor, a brand new web extension which transforms your browser into a first class Urbit client. Robert Kornacki from dcSpark will be taking viewers step-by-step through the history of how Urbit Visor came to be, starting off with his initial work on the Rust airlock implementation, moving into Login With Urbit, and finally arriving at the final product of Urbit Visor that we have today.
17738−
17739−From there Robert will hit on many topics including:
17740−
17741−- Live demonstration of how Urbit Visor works
17742−- How Urbit Visor improves and increases the security of the Landscape login experience
17743−- An overview of the first Urbit Web App: Urbit Dashboard
17744−- Ship hot-swapping
17745−- Streamlining the developer experience for any JS/TS dev to jump into the ecosystem and start building immediately
17746−- UV Extensions and how they will allow Urbit and the current web to integrate seamlessly
17747−- The long term goals and vision of Urbit Visor
17870+Austin, Texas martians - come hangout and talk Urbit Friday, January 21st at 6:30 pm at Distribution Hall. We will be joined by ~poldec-tonteg, the director of The Combine (the-combine.org), which is the Urbit Foundation's incubator that invests in teams building on Urbit. He will give a presentation around 8pm on The Combine, its purpose and how to get involved as an entrepreneur. It will be followed by a more technical presentation by Edward Amsden (~ritpub-sipsyl), an Urbit kernel developer who is currently rewriting Vere, the Nock run-time environment and Urbit's virtual machine. Team members from many Urbit companies will be in attendance including ~Tirrel, dcSpark, Tlon.io, Urbit Live, Wexpert Systems, Native Planet, and Holium. Hosted by Assembly Capital and the Urbit Foundation.
1774817871
17749−Robert Kornacki (~mocrux-nomdep) is CSO at dcSpark and has been in the Urbit ecosystem since 2019. Robert has significant experience working in the crypto industry over the past several years, developing tooling and smart contract protocols which hold millions of dollars of assets to this day.
17750−
17751−Hosted by Josh Lehman, the Director of the Urbit Foundation.
17872+If you haven't joined the network yet, bring a computer and we will help you get set up. Other than that we'll have some food, beverages and a fire, but be sure to bring a jacket too. See you there!
1775217873]]></content:encoded>
1775317874 </item>
1775417875 <item>
17755− <title><![CDATA[Developer Call: Running a Hosting Provider]]></title>
17756− <link>https://urbit.org/events/20211028-developer-call-hosting</link>
17757− <guid>https://urbit.org/events/20211028-developer-call-hosting</guid>
17876+ <title><![CDATA[Developer Call: Building the Next Developers on Mars]]></title>
17877+ <link>https://urbit.org/events/2022-02-17-developer-call-building-developers</link>
17878+ <guid>https://urbit.org/events/2022-02-17-developer-call-building-developers</guid>
1775817879 <pubDate>Invalid Date</pubDate>
1775917880 <content:encoded><![CDATA[
17760−As many of you know, Urbit runs best when hosted, seeing that it's a server and all. The problem of course is that hosting an Urbit ship isn't the easiest of things to do for most people. Hosting Urbit ships in production is actually pretty tough though—doing it right requires wrangling the complexity of traditional "Earth" infrastructure in addition to a strong sense of how Urbit works.
17761−
17762−In this call we're joined by Brendan Hay, the lead behind Tlon Hosting, and Lukas Bühler of UrbitHost, in what's sure to be an entertaining and informative conversation. Bren and Lukas have both been the masterminds behind their respective hosting architectures, and were somewhat surprised to learn that they'd independently settled on highly similar architectures.
17881+We'll discuss mapping out the current Urbit technology complex, how to promote ongoing developer engagement and cultivation, and the upcoming Hoon School Live reboot.
1776317882
17764−This will be an unscripted conversation that's sure to span a gamut of topics including, but not limited to: the unique technical challenges of hosting Urbit ships, the upcoming %khan vane, Kubernetes operators, product roadmaps, custodianship of (or plans to do away with) private keys, and probably a ton more.
17883+Neal Davis has taught computer science at the University of Illinois since 2015. Trained as a nuclear engineer, he moved through high-performance computing into training engineers to use computers well. He has joined the Urbit Foundation to work on all aspects of our developer experience.
1776517884
17766−Hosted by Josh Lehman, the Director of the Urbit Foundation.
17885+[Sign up for Hoon School Live here](https://hooniversity.org/enroll/).
1776717886]]></content:encoded>
1776817887 </item>
1776917888 </channel>