a21ce09 · urbit.org · git.iko.soy

.gitmodules+1−1

compare with master

unifiedsplit

@@ -1,5 +1,5 @@

1[submodule "static-site/docs"]

2 path = static-site/docs

3− url = git@github.com:urbit/docs.git

3+ url = git@github.com:urbit/docs

4 branch = master

5 ignore = all

README.md+12−4

@@ -6,13 +6,21 @@

6

72. Make a fakezod, using [this branch](https://github.com/urbit/arvo/tree/static-site-dev). It just has a few different renderers and marks for svgs, images, etc. Use the command `urbit -F zod -A <path/to/arvo/repo> -s -c zod -S`

8

9−3. In the running fakezod, mount the filesystem by running `|mount /===`

9+3. In the running fakezod, mount the filesystem by running `|mount %`

10

114. Run `./scripts/topier <path/to/pier>` from this directory to copy the pertinent files to your pier

12

13−5. Visit `localhost:8080` to see the rendered urbit.org

13+5. Visit `localhost:80` to see the rendered urbit.org

14

15## To render/export

16

17−1. Run `|static` in dojo

17+1. Copy all content into your ship `./scripts/topier <path/to/pier>`

18−2. You will find the outputted site at `<pier>/.urb/put/web`

18+2. Nuke docs `rm -rf </path/to/pier>/home/web/docs`

19+3. Run `|static` in dojo to render full site - docs

20+4. Copy rendered content into `dist` directory in this repo `cp -r </path/to/pier>/.urb/put/web dist && cp -r static-site/js dist`

21+5. Copy all content into your ship `./scripts/topier <path/to/pier>`

22+6. Nuke posts `rm -rf </path/to/pier>/home/web/posts`

23+7. Run `|static` in dojo to render docs

24+8. Copy rendered docs into `dist` directory in this repo `cp -r </path/to/pier>/.urb/put/web/docs dist`

25+9. Test by running `cd dist && python -m SimpleHTTPServer`

26+10. See urbit.org at `localhost:8000`

partials/doc-wrap.hoon+20−7

@@ -12,20 +12,33 @@

12 ;+ (head "Urbit / Docs")

13 ;body

14 ;+ menu

15+ ;div#sidebar-mobile.bg-gray-light.sidebar-hide.overflow-y

16+ ;div.container

17+ ;div.col-sm-10

18+ ;+ sidebar

19+ ==

20+ ;div.col-sm-1.sidebar-toggle.fixed(style "top: 20px; right: 1em")

21+ ;img.w-8.h-8.dropdown-right@"/assets/dropdown.svg";

22+ ==

23+ ==

24+ ==

15 ;div.container.mt-10

25 ;div.container.mt-10

16− ;div.row.fixed.pb-30(style "height:100%")

26+ ;div.sidebar-container.row.col-sm-3.fixed.pb-30.h-100-md

17− ;div.col-sm-3.col-md-12.menu-toggle

27+ ;div.col-sm-3.col-lg-6.menu-toggle

18 ;img.w-8.h-8@"/assets/menu-open.svg";

28 ;img.w-8.h-8@"/assets/menu-open.svg";

19 ==

29 ==

20− ;+ sidebar

30+ ;div.col-sm-12.mt-7.sidebar-toggle.md-hide

21− :: ;div.overflow-y.col-sm-8.col-lg-12.w-48.sm-hide(style "height:100%")

31+ ;img.w-8.h-8.dropdown-left@"/assets/dropdown.svg";

22− ::

32+ ==

33+ ;div.h-100.col-sm-8.col-md-11.overflow-y.sm-hide

34+ ;+ sidebar

23− :: ==

35+ ==

24 ==

36 ==

25 ;div.row.pb-80

37 ;div.row.pb-80

26− ;div.col-sm-9.col-md-8.col-sm-offset-3.col-md-offset-3.docs

38+ ;div.col-sm-9.col-md-8.col-sm-offset-2.col-md-offset-3.docs

27 ;+ content

39 ;+ content

28 ==

40 ==

41+

29 ==

42 ==

30 ==

43 ==

31 ;footer.mb-36

44 ;footer.mb-36

partials/head.hoon−2

@@ -5,14 +5,12 @@

5 ;meta(name "viewport", content "width=device-width , initial-scale=1");

6 ;link/"/tilde.ico"(rel "icon");

7 ;link/"/css/base.css"(rel "stylesheet");

8− ;link/"/css/base.css"(rel "preload");

9 ;link/"/css/lists.css"(rel "stylesheet");

8 ;link/"/css/lists.css"(rel "stylesheet");

10 ;link/"/css/visibility.css"(rel "stylesheet");

9 ;link/"/css/visibility.css"(rel "stylesheet");

11 ;link/"/css/borders.css"(rel "stylesheet");

10 ;link/"/css/borders.css"(rel "stylesheet");

12 ;link/"/css/colors.css"(rel "stylesheet");

11 ;link/"/css/colors.css"(rel "stylesheet");

13 ;link/"/css/inputs.css"(rel "stylesheet");

12 ;link/"/css/inputs.css"(rel "stylesheet");

14 ;link/"/css/typography.css"(rel "stylesheet");

13 ;link/"/css/typography.css"(rel "stylesheet");

15− ;link/"/css/typography.css"(rel "preload");

16 ;link/"/css/menu.css"(rel "stylesheet");

14 ;link/"/css/menu.css"(rel "stylesheet");

17 ;link/"/css/images.css"(rel "stylesheet");

15 ;link/"/css/images.css"(rel "stylesheet");

18 ;link/"/css/flex.css"(rel "stylesheet");

16 ;link/"/css/flex.css"(rel "stylesheet");

scripts/docsnew file+9

@@ -0,0 +1,9 @@

1+#!/usr/bin/env bash

2+

3+mkdir "$@"/home/web; cp static-site/docs.udon "$@"/home/web

4+rm -rf "$@"/home/web/docs

5+cp -r static-site/docs "$@"/home/web/docs

6+cp static-site/index.hoon "$@"/home/web.hoon rm -rf "$@"/home/ren/partials

7+cp -r partials "$@"/home/ren/partials

8+cp urb.hoon "$@"/home/ren

9+exit

scripts/postsnew file+12

@@ -0,0 +1,12 @@

1+#!/usr/bin/env bash

2+

3+rm -rf "$@"/home/web/posts

4+echo posts

5+mkdir "$@"/home/web/posts; cp -r static-site/posts "$@"/home/web/posts

6+cp -r static-site/{images,assets,css,js} "$@"/home/web

7+cp static-site/index.hoon "$@"/home/web.hoon

8+cp static-site/*.hoon "$@"/home/web

9+rm -rf "$@"/home/ren/partials

10+cp -r partials "$@"/home/ren/partials

11+cp urb.hoon "$@"/home/re

12+exit

static-site/assets/dropdown.svgnew file+1

@@ -0,0 +1 @@

1+<svg fill="none" height="16" viewBox="0 0 16 16" width="16" xmlns="http://www.w3.org/2000/svg"><path d="m8.04705 10.7614 4.71405-4.71404h-9.42809z" fill="#000"/></svg>

static-site/bounty.udon+2−2

@@ -6,9 +6,9 @@

6

7We are in the process of designing our Bug Bounty Program, and it should be live in several days. In the meantime, if you believe you have discovered a bug or vulnerability in our code, please report it at security@tlon.io.

8

9−We’ll review the issue, and a member of our dev team will get back to you ASAP. If your bug has merit, we’ll work with you to fix it, and award a bounty based on the severity of the bug. We determine severity using the [CVSS](https://www.first.org/cvss/calculator/3.0) model.

9+We'll review the issue, and a member of our dev team will get back to you ASAP. If your bug has merit, we'll work with you to fix it, and award a bounty based on the severity of the bug. We determine severity using the [CVSS](https://www.first.org/cvss/calculator/3.0) model.

10

11−Once the fix is complete, we’ll publish a full retrospective in the interests of transparency. If the bug leaks prior to the retrospective being published, the bounty is void.

11+Once the fix is complete, we'll publish a full retrospective in the interests of transparency. If the bug leaks prior to the retrospective being published, the bounty is void.

12

13We look forward to working with you.

14

static-site/css/colors.css+3

@@ -1,3 +1,6 @@

1+.bg-gray-light {

2+ background-color: #E6E6E6;

3+}

1.bg-gray-dark {

4.bg-gray-dark {

2 background-color: #7F7F7F ;

5 background-color: #7F7F7F ;

3}

6}

static-site/css/menu.css+36−4

@@ -1,4 +1,4 @@

1−.menu-show {

1+.menu-show, .sidebar-show {

2 position: fixed;

3 top:0%;

4 bottom: 0%;

@@ -7,12 +7,44 @@

7 visibility: visible;

8 opacity: 1;

9}

10−

11−.menu-hide {

10+.menu-hide, .sidebar-hide {

12 visibility: hidden;

11 visibility: hidden;

13 display: none;

12 display: none;

14}

13}

15

14

16−.menu-toggle {

15+.menu-toggle,.sidebar-toggle {

17 cursor: pointer;

16 cursor: pointer;

18}

17}

18+

19+/*****************

20+SIDEBAR CUSTOM CSS

21+******************/

22+.dropdown-left {

23+ transform: rotate(90deg);

24+}

25+.dropdown-right {

26+ transform: rotate(-90deg);

27+}

28+.sidebar-container {

29+ max-width: 232px;

30+}

31+

32+.h-100 {

33+ height: 100%;

34+}

35+@media only screen and (max-width: 750px) {

36+.sm-hide {

37+ display: none;

38+ }

39+}

40+

41+@media only screen and (min-width: 750px) {

42+.md-hide {

43+ display: none;

44+ }

45+}

46+@media only screen and (min-width: 750px) {

47+ .h-100-md{

48+ height: 100%;

49+ }

50+}

static-site/css/visibility.css+4−4

@@ -4,8 +4,8 @@

4.overflow-y {

5 overflow-y: scroll;

6}

7−@media only screen and (max-width: 480px) {

7+

8−.sm-hide {

8+

9− display: none;

9+.zn1{

10− }

10+ z-index: -1;

11}

static-site/docsnew file+1

Submodule changed.

static-site/index.hoon+1−1

@@ -43,7 +43,7 @@

43 "/primer"

44 ;+ %^ article

45 "Posts"

46− "Regular updates, ocassional essays and media"

46+ "Regular updates, occasional essays and media"

47 "/posts"

48 ;+ %^ article

49 "Docs"

static-site/introduction.hoon+1−1

@@ -8,7 +8,7 @@

8

9## Understanding Aliases

10

11−Aliases enables you to create custom Unix commands to use in your terminal. There are no best aliases, only what works best for you. This task involves using basic Unix commands. Don’t worry you’ll do fine.

11+Aliases enables you to create custom Unix commands to use in your terminal. There are no best aliases, only what works best for you. This task involves using basic Unix commands. Don't worry you'll do fine.

12

13### .bash_profile

14

static-site/js/main.js+7

@@ -4,3 +4,10 @@ $(function() {

4 $('body').toggleClass('overflow-hidden');

5 })

6});

7+

8+$(function() {

9+ $('.sidebar-toggle').on('click', function() {

10+ $('#sidebar-mobile').toggleClass('sidebar-hide sidebar-show');

11+ $('body').toggleClass('overflow-hidden');

12+ })

13+});

static-site/posts.hoon+1−1

@@ -28,7 +28,7 @@

28 %+ turn

29 ~(tap by update-list)

30 |= [fil=@ta fro=(map knot cord)]

31− [tag='media' file=fil front=fro]

31+ [tag='update' file=fil front=fro]

32 ==

33^- manx

34;div.posts.col-sm-10

static-site/posts/essays/a-founders-farewell.udon+8−8

@@ -441,15 +441,15 @@ computers hears a packet, and sends an acknowledgment, that only

441means the temporary brain heard it. Acks are not end-to-end

442transactions.

443

444−This means you can’t write a command protocol where your commands

444+This means you can't write a command protocol where your commands

445−get executed exactly once. You can only choose “at least once”

445+get executed exactly once. You can only choose "at least once"

446−or “at most once.” This problem is as ridiculous and frustrating

446+or "at most once." This problem is as ridiculous and frustrating

447as it sounds.

448

449You can address it in three ways: (a) make all your commands

450formally idempotent, so that repeating them has no additional

451effect; (b) insert a layer of stateful middleware — a message

452−queue; (c) be fine with “almost always once.” Guess which

452+queue; (c) be fine with "almost always once." Guess which

453approach is most popular?

454

455Your Urbit ship has one permanent brain. Its acks are end-to-end

@@ -460,16 +460,16 @@ queue. And every message is executed once.

460#### Dependencies

461

46220th-century languages are all at least vaguely based on a

463−formalism from the ‘30s called the “lambda calculus.” The

463+formalism from the '30s called the "lambda calculus." The

464fundamental operation in lambda calculus is variable reduction

465from name to value. So lambda languages all have a symbol table

466or environment which binds names to values.

467

468Modern build systems assemble large programs out of small files

469by reusing this symbol table for global function names, a process

470−called “linking.” Unfortunately, linking causes a problem known

470+called "linking." Unfortunately, linking causes a problem known

471−as “dependency hell,” involving baffling, unpredictable upgrade

471+as "dependency hell," involving baffling, unpredictable upgrade

472−failures. The fundamental problem is the “diamond dependency” —

472+failures. The fundamental problem is the "diamond dependency" —

473when a build requires two different versions of one symbol.

474

475Urbit does not use the lambda calculus, an environment or symbol

static-site/posts/essays/azimuth-is-on-chain.udon+22−21

@@ -21,7 +21,8 @@

21

22The Urbit address space is now live on the Ethereum blockchain. We’re calling the PKI ‘Azimuth’ and you can find it at [`0x223c067f8cf28ae173ee5cafea60ca44c335fecb`](https://etherscan.io/address/0x223c067f8cf28ae173ee5cafea60ca44c335fecb) or [`azimuth.eth`](https://etherscan.io/address/azimuth.eth). Owners of Azimuth ‘points’ (galaxies, stars or planets) can use [Bridge](https://github.com/urbit/bridge/releases) to manage them and view their balance now.

23

24+

24−Sometime in the next few days, owners of Azimuth points will be able to boot Arvo, the Urbit OS, from their Azimuth point and request access to one of our ‘cities’: private communities for chat and discussion. These new cities use Landscape, a brand new UI for using Urbit in the browser.

25+Sometime in the next few days, owners of Azimuth points will be able to boot Arvo, the Urbit OS, from their Azimuth point and request access to one of our 'cities': private communities for chat and discussion. These new cities use Landscape, a brand new UI for using Urbit in the browser.

25

26

26This means you can boot a deterministic OS from an identity you own, join a totally independent, decentralized and self-governing network and run a clean, simple UI. Pretty exciting. Is it ready for ordinary users? Definitely not.

27This means you can boot a deterministic OS from an identity you own, join a totally independent, decentralized and self-governing network and run a clean, simple UI. Pretty exciting. Is it ready for ordinary users? Definitely not.

27

28

@@ -31,14 +32,14 @@ But Urbit is not a 'product' in the conventional sense. Urbit is a public thing.

31

32

32With Azimuth on the blockchain, it's time for us to start engaging with the world more directly.

33With Azimuth on the blockchain, it's time for us to start engaging with the world more directly.

33

34

34−We aren’t calling this a launch. There’s no keynote. There’s no dancing on stage. I mean, it’s 2019. You must be pretty sick of being marketed to. We'll try to stick to the specifics here. What's new, what we've been up to and what works. There's too much to fit into a single post, so we'll keep it pretty light for now. Each of these sections will probably get its own post in the near future.

35+We aren't calling this a launch. There's no keynote. There's no dancing on stage. I mean, it's 2019. You must be pretty sick of being marketed to. We'll try to stick to the specifics here. What's new, what we've been up to and what works. There's too much to fit into a single post, so we'll keep it pretty light for now. Each of these sections will probably get its own post in the near future.

35

36

36> Note: As of `~2019.1.14` we're in the process of rebooting the Arvo network. We expect it to be back online before the end of the week. We'll update this post and [tweet](https://twitter.com/urbit) when the network is online and stable.

37> Note: As of `~2019.1.14` we're in the process of rebooting the Arvo network. We expect it to be back online before the end of the week. We'll update this post and [tweet](https://twitter.com/urbit) when the network is online and stable.

37

38

39

39## Rethinking the stack

40## Rethinking the stack

40

41

41−We’ve started to talk about Urbit as a stack of three parts: Azimuth, the address space and identity layer on Ethereum; Arvo, the OS and overlay network; and Aegean, a pattern for building decentralized communities on the Arvo network.

42+We've started to talk about Urbit as a stack of three parts: Azimuth, the address space and identity layer on Ethereum; Arvo, the OS and overlay network; and Aegean, a pattern for building decentralized communities on the Arvo network.

42

43

43We tried to capture this separation in [the primer](/primer), a new overview of Urbit. Explaining Urbit has always been challenging. A monolithic project that is OS, network, language, VM and UI barely makes sense. Separating the layers helps, we think.

44We tried to capture this separation in [the primer](/primer), a new overview of Urbit. Explaining Urbit has always been challenging. A monolithic project that is OS, network, language, VM and UI barely makes sense. Separating the layers helps, we think.

44

45

@@ -49,43 +50,43 @@ Let's step through them to see what's new.

49

50

50;img@"https://storage.googleapis.com/media.urbit.org/site/bridge-0.png";

51;img@"https://storage.googleapis.com/media.urbit.org/site/bridge-0.png";

51

52

52−As a quick refresher: Urbit addresses, now called Azimuth ‘points’, are short names like `~diblun-tidduc`. You own your Azimuth point with a private key and can use it as a routable network address on the Arvo network. You can read more about Azimuth in [the primer](/primer#what-azimuth-is). If you’re curious who owns all this address space, you can find that [in there too](/primer#azimuth-distribution).

53+As a quick refresher: Urbit addresses, now called Azimuth 'points', are short names like `~diblun-tidduc`. You own your Azimuth point with a private key and can use it as a routable network address on the Arvo network. You can read more about Azimuth in [the primer](/primer#what-azimuth-is). If you're curious who owns all this address space, you can find that [in there too](/primer#azimuth-distribution).

53

54

54−In late 2017 we decided to migrate the yet-to-be-named Azimuth to a system of Ethereum contracts. After a year of coding, testing, auditing and migrating — they’re now fully deployed to the Ethereum mainnet.

55+In late 2017 we decided to migrate the yet-to-be-named Azimuth to a system of Ethereum contracts. After a year of coding, testing, auditing and migrating — they're now fully deployed to the Ethereum mainnet.

55

56

56−Azimuth is basically two parts, a database of who owns which points, and a set of rules about what points and their owners can do. That set of rules is called Ecliptic, and can be found at [`0x6ac07b7c4601b5ce11de8dfe6335b871c7c4dd4d`](https://etherscan.io/address/0x6ac07b7c4601b5ce11de8dfe6335b871c7c4dd4d) or [`ecliptic.eth`](https://etherscan.io/address/ecliptic.eth). The top-level Azimuth points, the galaxies, can vote on upgrades to the Ecliptic contract, but they can’t edit the database of who owns what.

57+Azimuth is basically two parts, a database of who owns which points, and a set of rules about what points and their owners can do. That set of rules is called Ecliptic, and can be found at [`0x6ac07b7c4601b5ce11de8dfe6335b871c7c4dd4d`](https://etherscan.io/address/0x6ac07b7c4601b5ce11de8dfe6335b871c7c4dd4d) or [`ecliptic.eth`](https://etherscan.io/address/ecliptic.eth). The top-level Azimuth points, the galaxies, can vote on upgrades to the Ecliptic contract, but they can't edit the database of who owns what.

57

58

58−The ownership database contract is called Azimuth, which you can find at [`0x223c067f8cf28ae173ee5cafea60ca44c335fecb`](https://etherscan.io/address/0x223c067f8cf28ae173ee5cafea60ca44c335fecb) or [`azimuth.eth`](https://etherscan.io/address/azimuth.eth). For those of you who own address space, you can use the `getOwnedPoints` function in the ‘Read Contract’ tab to check your balance. The function returns the number (not the phonemic string like `~ravmel-ropdyl`) of your points. Each Azimuth point is an ERC-721, non-fungible piece of digital property.

59+The ownership database contract is called Azimuth, which you can find at [`0x223c067f8cf28ae173ee5cafea60ca44c335fecb`](https://etherscan.io/address/0x223c067f8cf28ae173ee5cafea60ca44c335fecb) or [`azimuth.eth`](https://etherscan.io/address/azimuth.eth). For those of you who own address space, you can use the `getOwnedPoints` function in the 'Read Contract' tab to check your balance. The function returns the number (not the phonemic string like `~ravmel-ropdyl`) of your points. Each Azimuth point is an ERC-721, non-fungible piece of digital property.

59

60

60−To manage your points, we built [Bridge](https://github.com/urbit/bridge/releases), a completely custom interface for interacting with our Solidity contracts. Interface quality is really important to us, and we couldn’t find anything in the 'crypto' world that met our standards. Bridge is good, but crypto UX is a hard problem. We've already got some ideas for improvements.

61+To manage your points, we built [Bridge](https://github.com/urbit/bridge/releases), a completely custom interface for interacting with our Solidity contracts. Interface quality is really important to us, and we couldn't find anything in the 'crypto' world that met our standards. Bridge is good, but crypto UX is a hard problem. We've already got some ideas for improvements.

61

62

62−If you’re curious, you can find the source for the contracts in the [`urbit/azimuth`](https://github.com/urbit/azimuth) repo. The Bridge source is in the [`urbit/bridge`](https://github.com/urbit/bridge) repo.

63+If you're curious, you can find the source for the contracts in the [`urbit/azimuth`](https://github.com/urbit/azimuth) repo. The Bridge source is in the [`urbit/bridge`](https://github.com/urbit/bridge) repo.

63

64

64−We had the source for our contracts audited by Open Zeppelin, Blockchain at Berkeley and Blocktrax. Did we miss something? We sure hope not — but we’d happily compensate anyone who can find bugs. Please reach out to security@urbit.org if you find something of concern. We’d be happy to hear from you.

65+We had the source for our contracts audited by Open Zeppelin, Blockchain at Berkeley and Blocktrax. Did we miss something? We sure hope not — but we'd happily compensate anyone who can find bugs. Please reach out to security@urbit.org if you find something of concern. We'd be happy to hear from you.

65

66

66;img@"https://storage.googleapis.com/media.urbit.org/site/sigils.svg";

67;img@"https://storage.googleapis.com/media.urbit.org/site/sigils.svg";

67

68

68−Azimuth names have always had a pronunciation system. `~ronryd-nidseg` is 13,695,781, for example. Now, they also have a visual system. We call these strange crests from another planet 'sigils', and you’ll notice them used throughout all our new interfaces. You can find the source in the [`urbit/sigil-js`](https://github.com/urbit/sigil-js) repository. Building these was a lot of fun — we’ll save the details for a future post.

69+Azimuth names have always had a pronunciation system. `~ronryd-nidseg` is 13,695,781, for example. Now, they also have a visual system. We call these strange crests from another planet 'sigils', and you'll notice them used throughout all our new interfaces. You can find the source in the [`urbit/sigil-js`](https://github.com/urbit/sigil-js) repository. Building these was a lot of fun — we'll save the details for a future post.

69

70

70−So, how do you get an Azimuth point? We’ve left that question unanswered intentionally. Azimuth points are meant to be like digital land, not currency. They should change hands slowly. In order to get an Azimuth point, you’ll need to find someone who already has one and is willing to part with it.

71+So, how do you get an Azimuth point? We've left that question unanswered intentionally. Azimuth points are meant to be like digital land, not currency. They should change hands slowly. In order to get an Azimuth point, you'll need to find someone who already has one and is willing to part with it.

71

72

73

73## Arvo

74## Arvo

74

75

75;img@"https://storage.googleapis.com/media.urbit.org/site/fast-lux-3.gif";

76;img@"https://storage.googleapis.com/media.urbit.org/site/fast-lux-3.gif";

76

77

77−Arvo boots from Ethereum, is no longer embarrassingly slow, and has a brand new build system. [Our documentation](https://urbit.org/docs/learn/arvo/hoon) has also improved quite a lot. Hoon, Arvo’s programming language, has had a lot of work done to its type system and compiler. We built new tooling for generating static sites (you’re probably reading this on one right now) that are much, much faster and easier to use.

78+Arvo boots from Ethereum, is no longer embarrassingly slow, and has a brand new build system. [Our documentation](https://urbit.org/docs/learn/arvo/hoon) has also improved quite a lot. Hoon, Arvo's programming language, has had a lot of work done to its type system and compiler. We built new tooling for generating static sites (you're probably reading this on one right now) that are much, much faster and easier to use.

78

79

79−It’s tough to talk about the progress we’ve made on Arvo without writing a long technical post. We'll save that for later. In a way, what’s remarkable about Arvo is that it has become *less* remarkable. It’s more stable, faster, and the code quality has improved.

80+It's tough to talk about the progress we've made on Arvo without writing a long technical post. We'll save that for later. In a way, what's remarkable about Arvo is that it has become *less* remarkable. It's more stable, faster, and the code quality has improved.

80

81

81−There’s plenty of work to do, though. Should you be building on top of Arvo? Probably not yet. The kernel and kernel modules are really where the work still lies. We build things on top of Arvo, and in doing so it’s pretty clear that the system can be better. Clay (the filesystem) and Gall (the application model) are due for a rewrite. A complete rewrite of the web server, Eyre is almost finished.

82+There's plenty of work to do, though. Should you be building on top of Arvo? Probably not yet. The kernel and kernel modules are really where the work still lies. We build things on top of Arvo, and in doing so it's pretty clear that the system can be better. Clay (the filesystem) and Gall (the application model) are due for a rewrite. A complete rewrite of the web server, Eyre is almost finished.

82

83

84

84## Aegean

85## Aegean

85

86

86;img@"https://storage.googleapis.com/media.urbit.org/site/landscape-inbox.png";

87;img@"https://storage.googleapis.com/media.urbit.org/site/landscape-inbox.png";

87

88

88−Aegean is a pattern for building ‘cities’: groups of people running the same ‘agent’ on their Arvo servers. Agents aren’t just ‘apps’ or programs. An agent rolls together the tools that a community needs. Today, our companies, communities, cults, cliques all have to duct tape together separate MEGACORP apps and services to compute together.

89+Aegean is a pattern for building 'cities': groups of people running the same 'agent' on their Arvo servers. Agents aren't just 'apps' or programs. An agent rolls together the tools that a community needs. Today, our companies, communities, cults, cliques all have to duct tape together separate MEGACORP apps and services to compute together.

89

90

90Aegean reverses this pattern. A community on Arvo is a city: just a bunch of people running the same agent. Each city is in control of its own codebase: the interface, application code _and_ data storage. This means a community can have complete agency over how to compute together.

91Aegean reverses this pattern. A community on Arvo is a city: just a bunch of people running the same agent. Each city is in control of its own codebase: the interface, application code _and_ data storage. This means a community can have complete agency over how to compute together.

91

92

@@ -95,20 +96,20 @@ It's important to note: the pattern of these cities is _not_ the pattern of Azim

95

96

96Before we can let the ocean of cities grow we have to homestead a few of our own.

97Before we can let the ocean of cities grow we have to homestead a few of our own.

97

98

98−Our first agent is called [Landscape](https://github.com/urbit/landscape), an agent for chat and longform discussion. We are using Landscape to run a few experimental cities over the next month or so. If you have an Azimuth point, you’ll need to [request access](mailto:support@urbit.org) to join.

99+Our first agent is called [Landscape](https://github.com/urbit/landscape), an agent for chat and longform discussion. We are using Landscape to run a few experimental cities over the next month or so. If you have an Azimuth point, you'll need to [request access](mailto:support@urbit.org) to join.

99

100

100−Anyone can create their own city, of course. The source is open. But we’re not going to encourage you to just yet. Feel free to explore, but also be patient. We’ve got a lot planned around this. If Azimuth is done and Arvo is young, Aegean is just being born.

101+Anyone can create their own city, of course. The source is open. But we're not going to encourage you to just yet. Feel free to explore, but also be patient. We've got a lot planned around this. If Azimuth is done and Arvo is young, Aegean is just being born.

101

102

103

103## Tlon

104## Tlon

104

105

105;img@"https://storage.googleapis.com/media.urbit.org/site/office-1.jpg";

106;img@"https://storage.googleapis.com/media.urbit.org/site/office-1.jpg";

106

107

107−So who is behind all of this? A team of collaborators and contributors. Many of us work at [Tlon](https://tlon.io) — the company we started in 2013 to advance Urbit platform development. Tlon has attracted an incredible group of smart, talented people who want the world to be able to own and control their computers. I’m proud to work alongside them.

108+So who is behind all of this? A team of collaborators and contributors. Many of us work at [Tlon](https://tlon.io) — the company we started in 2013 to advance Urbit platform development. Tlon has attracted an incredible group of smart, talented people who want the world to be able to own and control their computers. I'm proud to work alongside them.

108

109

109−One important omission on `tlon.io` is Curtis. As of today, he’s no longer working on Urbit. [His own words](/posts/essays/a-founders-farewell) are the best way to understand his thinking. It’s an achievement for the team, I think, that he can depart with confidence.

110+One important omission on `tlon.io` is Curtis. As of today, he's no longer working on Urbit. [His own words](/posts/essays/a-founders-farewell) are the best way to understand his thinking. It's an achievement for the team, I think, that he can depart with confidence.

110

111

111−One major reason for that confidence is that Erik and Anthony have now become COO and CPO respectively. Having thoughtful, organized people leading the project is a huge benefit to the whole team. I’m very glad to have them on board.

112+One major reason for that confidence is that Erik and Anthony have now become COO and CPO respectively. Having thoughtful, organized people leading the project is a huge benefit to the whole team. I'm very glad to have them on board.

112

113

114

114## Looking ahead

115## Looking ahead

static-site/posts/essays/governance-of-urbit.udon+10−10

@@ -22,28 +22,28 @@

22

23## Summary

24

25−Long before Urbit first appeared as a prototype in 2013, we considered Urbit address space to be property. Granted, Urbit property ownership was only reflected as a text file in a github repository – but it was always designed to be cryptographically owned, and we’ve always taken that file seriously.

25+Long before Urbit first appeared as a prototype in 2013, we considered Urbit address space to be property. Granted, Urbit property ownership was only reflected as a text file in a github repository – but it was always designed to be cryptographically owned, and we've always taken that file seriously.

26

27−If you’ve ever looked at that text file, you’ve probably noticed that there has been a pool of Urbit assets there marked “urbit.org” since the beginning. Now that we’re moving our property registry out of that repository and onto the Ethereum blockchain, we wanted to be as clear as we can be about what the plan is for those urbit.org addresses.

27+If you've ever looked at that text file, you've probably noticed that there has been a pool of Urbit assets there marked "urbit.org" since the beginning. Now that we're moving our property registry out of that repository and onto the Ethereum blockchain, we wanted to be as clear as we can be about what the plan is for those urbit.org addresses.

28

29−The TL;DR is that “urbit.org” will likely split into a separate entity from Tlon in the future. For now though, Tlon and urbit.org have the same mandate, so separating them doesn’t make sense. For the time being, Tlon will continue to manage and use urbit.org assets directly for platform development. As a first step toward making urbit.org independent we’ve started to develop a board of advisors who we hope will one day manage those assets independently.

29+The TL;DR is that "urbit.org" will likely split into a separate entity from Tlon in the future. For now though, Tlon and urbit.org have the same mandate, so separating them doesn't make sense. For the time being, Tlon will continue to manage and use urbit.org assets directly for platform development. As a first step toward making urbit.org independent we've started to develop a board of advisors who we hope will one day manage those assets independently.

30

31## Background

32

33−The history of a few lines in a text file doesn’t give a whole lot of context. So, first, let’s fill in a few more of the details.

33+The history of a few lines in a text file doesn't give a whole lot of context. So, first, let's fill in a few more of the details.

34

35−In 2013 Curtis and Tlon each contributed 32 galaxies to a pool newly called “urbit.org.” The idea at the time was to set aside address space to fund “platform development” – in the spirit of the IETF or the Mozilla foundation. This was long before anyone had heard of a Swiss blockchain foundation or anything of the sort. Our view was that it was going to take a lot of resources to build a system as robust and far reaching as Urbit intends to be, and 64 galaxies (25% of the total network) seemed sufficient. It was thought at the time that urbit.org might eventually take the form of a separate foundation, but we were simply too small and under-resourced a team to figure out the right legal structure at the time.

35+In 2013 Curtis and Tlon each contributed 32 galaxies to a pool newly called "urbit.org." The idea at the time was to set aside address space to fund "platform development" – in the spirit of the IETF or the Mozilla foundation. This was long before anyone had heard of a Swiss blockchain foundation or anything of the sort. Our view was that it was going to take a lot of resources to build a system as robust and far reaching as Urbit intends to be, and 64 galaxies (25% of the total network) seemed sufficient. It was thought at the time that urbit.org might eventually take the form of a separate foundation, but we were simply too small and under-resourced a team to figure out the right legal structure at the time.

36

37−Tlon – as distinct from urbit.org – has always been imagined as a future service provider in the urbit ecosystem. But Urbit is still young, so those services aren’t really needed yet.

37+Tlon – as distinct from urbit.org – has always been imagined as a future service provider in the urbit ecosystem. But Urbit is still young, so those services aren't really needed yet.

38

39−Instead, what is needed is platform development. So Tlon has acted, in a way, as urbit.org was supposed to, by taking on the bulk of platform development efforts. This work consists of everything from kernel development to interface design and documentation. Tlon has sold (and granted) both its own galaxies, and some of those originally designated as urbit.org galaxies towards this end. We’ll continue to do this for the foreseeable future, since Urbit’s development needs (though finite) remain ongoing. We can’t predict exactly how long this will continue, although we wish we could!

39+Instead, what is needed is platform development. So Tlon has acted, in a way, as urbit.org was supposed to, by taking on the bulk of platform development efforts. This work consists of everything from kernel development to interface design and documentation. Tlon has sold (and granted) both its own galaxies, and some of those originally designated as urbit.org galaxies towards this end. We'll continue to do this for the foreseeable future, since Urbit's development needs (though finite) remain ongoing. We can't predict exactly how long this will continue, although we wish we could!

40

41## Future plans

42

43As Urbit becomes more widely used, we expect to make the Tlon/urbit.org separation real.

44

45−We’ve considered the foundation model, but have come to the conclusion that it doesn’t really make sense. For one, it’s quite expensive in terms both of administrative overhead, and the associated legal costs. For another, there just isn’t anyone we trust enough to take over high level management of such an organization (see Tezos). Finally, our view is that foundations are not entirely effective in their mandates (see [this article](https://nadiaeghbal.com/foundations) from our friend Nadia).

45+We've considered the foundation model, but have come to the conclusion that it doesn't really make sense. For one, it's quite expensive in terms both of administrative overhead, and the associated legal costs. For another, there just isn't anyone we trust enough to take over high level management of such an organization (see Tezos). Finally, our view is that foundations are not entirely effective in their mandates (see [this article](https://nadiaeghbal.com/foundations) from our friend Nadia).

46

47−One step we’re pursuing is the creation of a board of advisors to guide our use of the urbit.org assets at Tlon. We’re in discussions with several potential board members now. Our goal with this structure is to include more voices outside of Tlon in the process of governing the urbit.org assets, and to make their advice transparent to the public.

47+One step we're pursuing is the creation of a board of advisors to guide our use of the urbit.org assets at Tlon. We're in discussions with several potential board members now. Our goal with this structure is to include more voices outside of Tlon in the process of governing the urbit.org assets, and to make their advice transparent to the public.

48

49−As with all of our projects, we think it’s better to walk before we run. For now, Tlon will continue to act as urbit.org and use both pools of resources for ongoing platform development. Next, we’ll create a board to advise on the use of those resources. Eventually, Tlon and urbit.org will likely become separate entities. We’ll get there – one step at a time.

49+As with all of our projects, we think it's better to walk before we run. For now, Tlon will continue to act as urbit.org and use both pools of resources for ongoing platform development. Next, we'll create a board to advise on the use of those resources. Eventually, Tlon and urbit.org will likely become separate entities. We'll get there – one step at a time.

static-site/posts/essays/urbit-and-the-blockchain.udon+5−5

@@ -70,7 +70,7 @@ or just logs raw data that anyone can interpret.

70

71The simplest procedure, with the strongest blockchain, would be just to encode

72each Urbit event as raw (OP_RETURN) data on the Bitcoin blockchain. Or we could

73−use another simple layer on top of Bitcoin; classic “colored coins,” for

73+use another simple layer on top of Bitcoin; classic "colored coins," for

74instance.

75

76The resemblance between Urbit land-registry titles and colored coins is one we

@@ -200,13 +200,13 @@ Moreover, the ability to vote formally in an Ethereum constitution will allow us

200to migrate in a cohesive way to *any other formalization of the Urbit PKI*.

201This could be another Ethereum contract. Or another blockchain.

202

203−This “clean escape” implies that Ethereum is still operating normally, or at

203+This "clean escape" implies that Ethereum is still operating normally, or at

204least normally enough to conduct a galaxy vote. What could happen to Ethereum?

205The blockchain could stop generating new blocks; it could fork; it could be

206filtered by some kind of collective attacker; it could even start accepting invalid transactions. What seems implausible is destruction of all copies of the whole chain.

207

208−When Ethereum ceases to be functional or trustworthy for any reason, a “dirty

208+When Ethereum ceases to be functional or trustworthy for any reason, a "dirty

209−escape” becomes necessary. The galaxy operators need to identify the last point

209+escape" becomes necessary. The galaxy operators need to identify the last point

210in the Ethereum chain at which the Urbit constitution remains valid, copy that

211data to the new primary record, and resume from there.

212

@@ -240,7 +240,7 @@ ExxonMobil has no business motivation to ruin its customers' engines. If it

240did, it would just destroy its business, and gain… what? If you don't have an

241attack motivation, you don't have a threat model. If you don't have a threat

242model, you don't have a threat. This is why we don't tend to worry about

243−“parent attacks” in Urbit.

243+"parent attacks" in Urbit.

244

245But that said: there's no reason not to make Urbit's cryptographic structure as

246strong as possible. If you don't want to trust your gas station -- you

static-site/posts/essays/what-is-urbit-for.udon+2−2

@@ -67,7 +67,7 @@ exchange digital currency, but how do I know who anyone is?

67

68Your Urbit can post public proof to your third party services and its

69validity is easily auditable. Using Urbit as an identity scheme for

70−new services would be a great decentralized alternative to ‘Sign in

70+new services would be a great decentralized alternative to 'Sign in

71with [company x]'.

72

73## Tomorrow

@@ -185,7 +185,7 @@ intended to be used for your devices, sensors, appliances, machines,

185robots, VR helmet, etc.

186

187The future of the individual's computing experience may very likely be

188−among many different devices. Bret Victor's ‘Seeing Spaces' is a

188+among many different devices. Bret Victor's 'Seeing Spaces' is a

189great exploration of what this future may look like. For the

190industrial enterprise there's a whole other set of parallel problems:

191tracking inventory, controlling a vast array of machines, and managing

static-site/posts/updates/2017.11.14-update.udon+6−6

@@ -43,7 +43,7 @@ everything to help.

43

44*Curtis, Iceman, Ted, Anton, Mark*

45

46−Curtis has spent most of 2017 quasi-surreptitiously in “auteur mode,” trying to

46+Curtis has spent most of 2017 quasi-surreptitiously in "auteur mode," trying to

47complete his initial authorship of Hoon. After this release he promises to work

48only on Arvo and above.

49

@@ -64,8 +64,8 @@ Ted, Anton and Mark on Udon.

64

65Big changes in Hoon 143:

66

67−- Hoon 151's “electroplating,” which replaced Hoon 164's “vulcanization,”

67+- Hoon 151's "electroplating," which replaced Hoon 164's "vulcanization,"

68− has been replaced by 143's “repainting.” This means wet gate namespacing

68+ has been replaced by 143's "repainting." This means wet gate namespacing

69 works, so you can write `(weld ~[1 2] ~[3 4])` and get `~[1 2 3 4]` instead of

70 `error: %mull-bonk-b`.

71- There's now only one wide syntax `{a/term b/term}` becomes `[a=term b=term]`.

@@ -93,7 +93,7 @@ Anything all they agree on is probably good.

93makes many system-software problems trivial, it is not so awesome that a team

94this small can advance two branches at once. This fall 2017 release is a

95classic, Microsoft-style stick save, cutting off about half of the research

96−(“master” or “cc-release”) branch and merging it back with splints and bandaids.

96+("master" or "cc-release") branch and merging it back with splints and bandaids.

97

98What got cut (this work is mostly coded, but not fully tested / integrated):

99

@@ -127,7 +127,7 @@ The Ford cache is cleared every time something in Clay changes.

127On the client side, pages are built through multiple requests.

128

129To fix (2) we want to move to a system where each page is a single static build.

130−This means doing ‘server side rendering' with Ford — rather than having the

130+This means doing 'server side rendering' with Ford — rather than having the

131client make multiple requests for every page component.

132

133The basic parts of this are done. We implemented a subset of markdown in Hoon

@@ -198,7 +198,7 @@ About a month ago we were discussing how we'd really like to be more transparent

198about the projects we undertake. And, we'd really like to have a way of

199cataloging projects we discuss but can't take on.

200

201−Enter the UP or ‘Urbit Proposal'. UP0 gives an outline for what a UP should

201+Enter the UP or 'Urbit Proposal'. UP0 gives an outline for what a UP should

202contain:

203[fora/posts/~2017.10.19..03.45.26..dbec~/](https://urbit.org/fora/posts/~2017.10.19..03.45.26..dbec~/).

204

static-site/posts/updates/2017.12.2-update.udon+15−15

@@ -9,16 +9,16 @@

9# ~2017.12.2 Update

10

11This week Tlon has mostly focused on testing the upcoming continuity breach. We also fixed some compiler problems, made

12−progress on restructuring web publishing to use server-side rendering, and have started working on closing some of arvo’s

12+progress on restructuring web publishing to use server-side rendering, and have started working on closing some of arvo's

13−oldest open pull requests. From the community, we’re excited to report that `~master-morzod` has an initial

13+oldest open pull requests. From the community, we're excited to report that `~master-morzod` has an initial

14implementation of SSL termination in vere.

15

16*Ted* `~rovnys-ricfer` has been working on the [urbit fleet

17repo](https://github.com/urbit/fleet/tree/e20400315bbea2091579b7beaa36eb50bbbd2796), which we use for spawning testnets.

18−The repo now works with the new `urbit` command-line arguments that are part of the breach, and it’s now at the point

18+The repo now works with the new `urbit` command-line arguments that are part of the breach, and it's now at the point

19−where we can launch ships from galaxies all the way down to comets. We’ve been using it to test various aspects of

19+where we can launch ships from galaxies all the way down to comets. We've been using it to test various aspects of

20−Urbit’s multi-ship functionality, such as `:talk` and filesystem syncing. Turns out there is a bug with filesystem

20+Urbit's multi-ship functionality, such as `:talk` and filesystem syncing. Turns out there is a bug with filesystem

21−syncing in master, so we’re going to have to fix that before breaching.

21+syncing in master, so we're going to have to fix that before breaching.

22

23*Anton* `~pittyp-datfyn` has knocked out a bunch of items in our breach checklist. Some highlights:

24- Fixed single-sign-on

@@ -30,17 +30,17 @@ syncing in master, so we’re going to have to fix that before breaching.

30reflect the changes made in hoon `%143` (which will be deployed with the breach) and helped Ted debug some urbit/fleet

31problems.

32

33−*Curtis* `~sorreg-namtyv` has made a number of improvements to hoon’s defaulting system (bunting). Part of the work

33+*Curtis* `~sorreg-namtyv` has made a number of improvements to hoon's defaulting system (bunting). Part of the work

34included fixing an inconsistency in how hoon determined which subtype of a fork type would be chosen as default. After

35fixing that, he implemented a cache for those defaults, which improved compilation speed by 10-20%. This code has been

36−merged into Arvo’s master branch. He’s still working on a parallel defaulting system, which might go even faster.

36+merged into Arvo's master branch. He's still working on a parallel defaulting system, which might go even faster.

37

38−*Galen* `~ravmel-ropdyl` and Jimmy have been working on the new urbit.org homepage, which will be Tlon’s next priority

38+*Galen* `~ravmel-ropdyl` and Jimmy have been working on the new urbit.org homepage, which will be Tlon's next priority

39after the breach. This will feature a complete redesign using a new base.css to provide a standardized look and feel for

40the Urbit web experience.

41

42*Mark* `~palfun-foslup` / `~palnup-salwyx-mortyl-silfyl--digrel-pitbud-dorsym-livpyl` has been working with

43−~poldec-tonteg to troubleshoot some issues with Urbit’s Ethereum constitution. He’s still waiting for the rest of Tlon to

43+~poldec-tonteg to troubleshoot some issues with Urbit's Ethereum constitution. He's still waiting for the rest of Tlon to

44test his [monumental PR](https://github.com/urbit/arvo/pull/452) for new talk, which he submitted a couple weeks ago. Now

45that we have the fleet repo working, we can use it to test this work more thoroughly. This week he also made some changes

46to Hall, which he has expressed in haiku form:

@@ -57,19 +57,19 @@ He also says:

57 blogs and foras. Complete with filesystem, storage, and hall notifications!

58

59*Joe* `~master-morzod` has written an implementation of SSL termination in vere. This will allow your Urbit to serve true

60−end-to-end-encrypted HTTPS, as opposed to Tlon’s servers operating as man-in-the-middle, which is not a viable long-term

60+end-to-end-encrypted HTTPS, as opposed to Tlon's servers operating as man-in-the-middle, which is not a viable long-term

61−solution. This has been an important piece of missing functionality, so we’re excited to see it start to come together.

61+solution. This has been an important piece of missing functionality, so we're excited to see it start to come together.

62Latest code can be found [here](https://github.com/joemfb/urbit/tree/346de776c5fabe3e02fecb7cab3d1652e4cc46e3).

63

64−*Isaac* `~davtyr-nimren` has been building the next generation of Urbit’s web publishing system, currently located in the

64+*Isaac* `~davtyr-nimren` has been building the next generation of Urbit's web publishing system, currently located in the

65ren/tree directory of Arvo. This new system, instead of serializing data down to the client to be fetched after the

66initial page load, will perform the HTML rendering on the server. This is now possible because of the integration of our

67Udon markup language with the Hoon compiler. This allows us to include Udon files in other Udon files using Ford runes.

68−The new system is much simpler and should improve page load time. Once we’ve written our planned Vere HTTP cache, this

68+The new system is much simpler and should improve page load time. Once we've written our planned Vere HTTP cache, this

69new paradigm should also improve the coherence of that cache. This system is mostly complete now, and Isaac is now

70working on smaller bugfixes.

71

72−There was also a [new episode of Mars Talk](https://youtu.be/1xcjnBu6qFo) with Ted and Joe discussing Hoon’s type system.

72+There was also a [new episode of Mars Talk](https://youtu.be/1xcjnBu6qFo) with Ted and Joe discussing Hoon's type system.

73

74Those are the highlights from this week. Back to breaching!

75

static-site/posts/updates/2017.8.11-update.udon+2−2

@@ -28,7 +28,7 @@ There are two sides to this effort: design/usability and stability.

28`:tree`, the Urbit publishing framework, can be painfully slow. In part, this

29is because we do too much work client-side to put pages together. It would make

30a lot more sense for a page to be a single fixed function of a URL -- the

31−original “functional publishing” design.

31+original "functional publishing" design.

32

33So, we've gone and made that actually work. Server-side includes will now be

34possible, since we're adding a Markdown subset to Hoon itself. We're also going

@@ -63,7 +63,7 @@ can be had in connection with the code itself.

63We already use Urbit to chat and write, but the edges are pretty rough. Better,

64faster publishing and a look and feel refresh will allow us to update and clean

65up our existing tools for chatting and writing. Hopefully to the point that

66−they clear the ‘Facebook 2004' bar. But, of course, in a pretty different way.

66+they clear the 'Facebook 2004' bar. But, of course, in a pretty different way.

67

68## Examples

69

static-site/posts/updates/2017.9.20-bootstrapping-urbit-from-ethereum.udon+2−2

@@ -21,7 +21,7 @@ auction stars, and stars to distribute planets.

21

22## A bit of background

23

24−One thing we realized after the last sale was, ‘oh hey, the network has been up

24+One thing we realized after the last sale was, 'oh hey, the network has been up

25for about a year.' Not bad! It wasn't that long ago that we were rebooting the

26universe every few weeks. We still have plenty of work to do — but Urbit has

27matured to the point where public ownership of the network really should be

@@ -59,7 +59,7 @@ mechanism. So we're really living in 2017.

59Sounds good, right?

60

61It does sound good. Although, as usual, we care about making things that *work*

62−above all else. So, rather than a ‘announcing the Urbit token sale' post, this

62+above all else. So, rather than a 'announcing the Urbit token sale' post, this

63is going to get fairly technical. We want to start the discussion about how

64this change is going to work, and how it's going to get implemented. We'll save

65the hype for later.

static-site/posts/updates/2017.9.23-update.udon+1−1

@@ -8,7 +8,7 @@

8

9# ~2017.9.23 Update

10

11−Galen and Curtis publish Tlon’s plans for bootstrapping the Urbit PKI on the Ethereum blockchain. Ted creates a cheat sheet for Hoon. An Urbit podcast is born. The community talks about searching filesystems and cryptographic hashes.

11+Galen and Curtis publish Tlon's plans for bootstrapping the Urbit PKI on the Ethereum blockchain. Ted creates a cheat sheet for Hoon. An Urbit podcast is born. The community talks about searching filesystems and cryptographic hashes.

12

13- [Bootstrapping Urbit from Ethereum](https://urbit.org/blog/2017.9-eth) blog post. [Discussion on

14 Fora](https://urbit.org/fora/posts/~2017.9.20..22.56.04..47ce~)

static-site/posts/updates/2018.1.13-update.udon+2−2

@@ -18,10 +18,10 @@ This week:

18

19**Anton** `~pittyp-datfyn` has been doing some work with **Joe** `~master-morzod` on [automated Vere memory verification](https://github.com/urbit/urbit/pull/915).

20

21−**Mark** has a [PR to fix a talk / Gall bug](https://github.com/urbit/arvo/pull/538) and is now working on updating Clay’s API to support multiple files per request, which will support the Ford caching improvements.

21+**Mark** has a [PR to fix a talk / Gall bug](https://github.com/urbit/arvo/pull/538) and is now working on updating Clay's API to support multiple files per request, which will support the Ford caching improvements.

22

23**Iceman** `~littel-ponnys` has submitted a [PR implementing a unit testing framework](https://github.com/urbit/arvo/pull/539) for Hoon, which had been in the works for a long time.

24

25−**Mikolaj** `~ponmep-litsem` has been making lots of good contributions recently, including reporting several GitHub issues and work on an Elm web frontend for Urbit, which he’s using to implement [Plato](https://github.com/mikolajpp/plato), an in-browser Hoon editor.

25+**Mikolaj** `~ponmep-litsem` has been making lots of good contributions recently, including reporting several GitHub issues and work on an Elm web frontend for Urbit, which he's using to implement [Plato](https://github.com/mikolajpp/plato), an in-browser Hoon editor.

26

27Finally, in [Mars Talk this week](https://youtu.be/oX7TFJ5qzr4) Ted wrote a Gall app using a timer from Behn with help from Keaton and **Josh** `~taglux-nidsep`.

static-site/posts/updates/2018.10.12-update.udon+6−6

@@ -10,18 +10,18 @@

10

11;img@"https://media.urbit.org/fora/updates/2018.10.12-update.png"(width "100%");

12

13−It’s an exciting time here at Tlon.

13+It's an exciting time here at Tlon.

14

15The Keys team is toiling to make the Urbit Wallet air-tight and foolproof. The

16Urbit Wallet, a cousin to the more typical cryptocurrency wallet, is an original

17−system for securing cryptographic assets. It’s original enough to demand its own

17+system for securing cryptographic assets. It's original enough to demand its own

18Manual, a document that *Will* `~hadrud-lodsef`, *Rob* `~lodleb-ritrul`, and

19*Morgan* `~hidrel-fabtel` are in the process of perfecting. The Wallet Manual

20will be a one-stop shop for information on using the Urbit Wallet system, both

21general concepts and technical details.

22

23Someone claiming to have solved a sufficiently large task with their first

24−attempt is probably lying. The Keys team are an honest bunch, and they’ve

24+attempt is probably lying. The Keys team are an honest bunch, and they've

25decided to simplify our in-house wallet-generation software into something that

26produces one Urbit Wallet for each ship. That wallet generator provides secret

27keys to users in the form of PDFs, and these PDFs have been redesigned by

@@ -35,7 +35,7 @@ secure your ships on the blockchain, but we will soon to merge the two apps into

35a combined application known as Bridge.

36

37Our foreign correspondents are lending their talents to the Bridge mission.

38−New Zealand’s *Jared* `~nidsut-tomdun` has been working on the attendant

38+New Zealand's *Jared* `~nidsut-tomdun` has been working on the attendant

39key-derivation library, and is also creating the library for displaying

40Urbit Wallet tickets as human-memorable strings. *Mark* `~palfun-foslup`, our

41beloved Dutchman, worked with Jared to develop a JavaScript interface to the

@@ -45,13 +45,13 @@ The infrastructure team has labored clanking towards the goal of making Vere

45less clanky. Two of *Paul's* `~fodwyt-ragful` changes -- a custom-bytecode

46Nock interpreter and a new jet dashboard -- have been integrated, resulting in a

47faster and more robust Urbit. Nock itself was updated, too, with the notable

48−addition being the Nock 12 “edit” operator. Paul, *Ted* `~rovnys-ricfer`, and

48+addition being the Nock 12 "edit" operator. Paul, *Ted* `~rovnys-ricfer`, and

49*Joe* `~master-morzod` joined forces to make this happen, and borrowed our

50resident logician *Josh* `~taglux-nidsep` from the docs team to check it for

51correctness.

52

53All of the above points to the big enchilada: using the Constitution as the

54−address registry for the Urbit network. Mark has capped off this week’s progress

54+address registry for the Urbit network. Mark has capped off this week's progress

55by booting the Urbit testnet (with all the new Landscape features) against an

56Ethereum testnet, so now we can do our best to break it. Things are about to get

57real.

static-site/posts/updates/2018.10.24-update.udon+1−1

@@ -8,7 +8,7 @@

8

9# ~2018.10.24 Update

10

11−Here’s a short update from the team at Tlon for the week of `~2018.10.24`:

11+Here's a short update from the team at Tlon for the week of `~2018.10.24`:

12

13;img@"https://media.urbit.org/fora/updates/2018.10.24-update.jpg"(width "100%");

14

static-site/posts/updates/2018.11.20-update.udon+13−13

@@ -8,7 +8,7 @@

8

9# ~2018.11.20 Update

10

11−Here’s a short update from the team at Tlon for the week of `~2018.11.20`:

11+Here's a short update from the team at Tlon for the week of `~2018.11.20`:

12

13;img@"https://media.urbit.org/fora/updates/2018.11.19-update.jpg"(width "100%");

14

@@ -17,7 +17,7 @@ excruciating reworking and fine-turning, *Will* `~hadrud-lodsef`, *Gavin*

17`~ridlur-figbud`, *Morgan* `~hidrel-fabtel`, and *Jimmy* `~haptyl-wanwes`

18have completed the client-side tools for registering Ethereum addresses to

19receive and access their purchased ships. The registration process begins with

20−the emails that we’ve begun to send out to ship-owners. The first batch has been

20+the emails that we've begun to send out to ship-owners. The first batch has been

21sent, and the next batches will go out in the coming week. If you own address

22space, keep an eye out for an email from the urbit.org domain.

23

@@ -25,27 +25,27 @@ Address registration points towards the real prize: the full ledger of Urbit

25ships nesting in the cozy, decentralized embrace of the Ethereum-based PKI. To

26this end, *Mark* `~palfun-foslup` added some Ethereum-facing cryptographic

27functions [in the form of jets](https://github.com/urbit/urbit/pull/1028). And

28−they do what exactly what jets are supposed to do: take things from “unusably

28+they do what exactly what jets are supposed to do: take things from "unusably

29−slow” to “actually pretty good.” This means that we can start deploying

29+slow" to "actually pretty good." This means that we can start deploying

30Constitution transactions.

31

32−Performance isn’t always a matter of engineering challenges being surmounted,

32+Performance isn't always a matter of engineering challenges being surmounted,

33−though. Occasionally it’s a matter of hearing the cracking of joints in

33+though. Occasionally it's a matter of hearing the cracking of joints in

34−something that’s turning the wrong way. *Elliot* `~littel-ponnys` felt something

34+something that's turning the wrong way. *Elliot* `~littel-ponnys` felt something

35so ghastly: a 200-millisecond delay on every Ford build. So the search began.

36−What was uncovered was two otherwise-benign lines that didn’t get along with

36+What was uncovered was two otherwise-benign lines that didn't get along with

37−*Paul’s* `~fodwyt-ragful` recently merged Vere changes. Elliot handled the

37+*Paul's* `~fodwyt-ragful` recently merged Vere changes. Elliot handled the

38Arvo side, Paul charged the Vere flank, and the build-system bug was vanquished.

39

40Yes, Urbit is a mission fearsome and sprawling, but we at Tlon live for the

41−hunt. Tearing up and replacing the entire stack just isn’t enough, so we put our

41+hunt. Tearing up and replacing the entire stack just isn't enough, so we put our

42own, meticulous spin on the concept of a cryptocurrency wallet. The *Urbit

43Hierarchical Deterministic Wallet* is a _system_ of related key-pairs that have

44−distinct powers. That’s because you want it to be easy to, say, authenticate

44+distinct powers. That's because you want it to be easy to, say, authenticate

45−packets without having to risk a chunk of your net worth. It’s *deterministic*

45+packets without having to risk a chunk of your net worth. It's *deterministic*

46because key-pairs of a lower tier can be derived from those of a higher-tier,

47making the whole system a nice balance of usability and security. Sound cool?

48−Check out the details in Tlon’s

48+Check out the details in Tlon's

49[Urbit Proposal](https://fora.urbit.org/proposals/posts/~2018.11.8..19.31.59..ba77~/)

50on the matter.

51

static-site/posts/updates/2018.11.6-update.udon+7−7

@@ -8,14 +8,14 @@

8

9# ~2018.11.6 Update

10

11−Here’s a short update from the team at Tlon for the week of `~2018.11.6`:

11+Here's a short update from the team at Tlon for the week of `~2018.11.6`:

12

13;img@"https://media.urbit.org/fora/updates/2018.11.7-update.jpg"(width "100%");

14

15*Gavin* `~ridlur-figbud`, *Will* `~hadrud-lodsef`, and *Jimmy* `~haptyl-wanwes`

16have been working tirelessly on the front-end tooling for bootstrapping our

17[PKI on Ethereum](https://urbit.org/blog/2017.9-eth/). The fruits of their labor

18−are nearly ripe: all that’s left is finalizing the copy and the documentation.

18+are nearly ripe: all that's left is finalizing the copy and the documentation.

19

20*Philip* `~wicdev-wisryt`, a powerful Hoonist, is making sure that the Arvo

21level of the stack is ready for the Great PKI Migration. Previously, every time

@@ -26,7 +26,7 @@ snapshot of the blockchain, rather than each individual event. And if we ever

26need to revert some events because of a chain reorganization, we can just

27restore an earlier snapshot instead of starting from scratch.

28

29−Landscape is the charming, user-facing bow on the top of all of this, and it’s

29+Landscape is the charming, user-facing bow on the top of all of this, and it's

30just completed the first round of internal user-feedback testing. The entire

31company came together to raise interface hell, providing *Isaac*

32`~davtyr-nimren` and *Chris* `~sigtus-hossyn` with a lot of useful data on the

@@ -35,13 +35,13 @@ infrastructure, by way of the profiler in the Arvo interpreter.

35

36Pretty sweet.

37

38−Or, _probably_ sweet. They tell you in college that it’s never a compiler error,

38+Or, _probably_ sweet. They tell you in college that it's never a compiler error,

39−but some of the “interesting” results of our profiling may, in fact, be

39+but some of the "interesting" results of our profiling may, in fact, be

40artifacts of a compiler error. *Ted* `~rovnys-ricfer` and *Elliot*

41`~littel-ponnys` are spelunking the lowest depths of the stack, illuminating any

42−profiler bugs with their combined brilliance. It’s unlikely that our heroes will

42+profiler bugs with their combined brilliance. It's unlikely that our heroes will

43find any Balrogs, but you can never be too sure.

44

45−It won’t be long now, Martians.

45+It won't be long now, Martians.

46

47*Rob* `lodleb-ritrul`

static-site/posts/updates/2018.12.18-update.udon+9−9

@@ -8,7 +8,7 @@

8

9# ~2018.12.18 Update

10

11−Here’s a short update from the team at Tlon for the week of `~2018.12.18`:

11+Here's a short update from the team at Tlon for the week of `~2018.12.18`:

12

13;img@"https://media.urbit.org/fora/updates/2018.12.18-update.png"(width "100%");

14

@@ -20,7 +20,7 @@ The Urbit network has, indeed, been renewed. *Logan* `~tacryt-socryp`

20performed a breach on the network, wiping the slate clean. All urbits must be

21booted again with their original tickets, which means that your crashed ships

22now have a second chance at life. If your ship is now experiencing connectivity

23−troubles, don’t worry: deleting your old pier should fix everything.

23+troubles, don't worry: deleting your old pier should fix everything.

24

25On the infrastructure side, *Elliot* the Wonderworker `~littel-ponnys` brought

26us a gift-sack of miraculous performance improvements. He started by fixing

@@ -36,21 +36,21 @@ imperceptible.

36

37*Morgan* `~hidrel-fabtel` and *Jimmy* `~haptyl-wanwes` are hard at work

38overhauling the site for the New Year, both in terms of web design and the

39−presentation of content. The new website will also include Jimmy’s primer,

39+presentation of content. The new website will also include Jimmy's primer,

40−which neatly explains Urbit in layman’s terms.

40+which neatly explains Urbit in layman's terms.

41

42The docs boys -- *Rob* `~lodleb-ritrul`, *Josh* `~taglux-nidsep`, and *David*

43`~rapfyr-diglyt` -- are helping out on this front. The documentation is being

44−completely reorganized so that it’s more accessible and less overwhelming. A

44+completely reorganized so that it's more accessible and less overwhelming. A

45−great deal of new tutorial content will be included, and it’s good enough that

45+great deal of new tutorial content will be included, and it's good enough that

46−it might put a dent in Urbit’s arcane reputation.

46+it might put a dent in Urbit's arcane reputation.

47

48And finally, rejoice! The great Ethereum address-space migration has begun!

49

50If you own address space, you should have received an email with instructions

51about how to register an Ethereum address with us so that we can grant you

52−cryptographic ownership of your address space. If you haven’t received an email

52+cryptographic ownership of your address space. If you haven't received an email

53−a) check your spam folder and, if that doesn’t work, b) send an email to

53+a) check your spam folder and, if that doesn't work, b) send an email to

54[registration@urbit.org](mailto:registration@urbit.org).

55

56See you next week.

static-site/posts/updates/2018.2.17-update.udon+5−5

@@ -8,9 +8,9 @@

8

9# ~2018.2.17 Update

10

11−Here’s what we’ve all been up to this week:

11+Here's what we've all been up to this week:

12

13−*Curtis* `~sorreg-namtyv` this week, on behalf of `urbit.org,` [awarded Winter 2018 star grants](https://fora.urbit.org/posts/~2018.2.13..20.22.22..bddb~) to Urbit’s top recent contributors. The winners this term were:

13+*Curtis* `~sorreg-namtyv` this week, on behalf of `urbit.org,` [awarded Winter 2018 star grants](https://fora.urbit.org/posts/~2018.2.13..20.22.22..bddb~) to Urbit's top recent contributors. The winners this term were:

14

15- *Gold*, _64 stars_: Joe Bryan `~master-morzod`

16- *Silver*, _32 stars_: Joshua Reagan `~taglux-nidsep`

@@ -25,10 +25,10 @@ Thank you all again for helping bring Urbit to life!

25

26*Anton* `~pittyp-datfyn` has been working hard on making Urbit-flavored markdown, and subsequently, Fora, a lot less slow than it currently is.

27

28−*Mark* `~palfun-foslup` submitted an [`urbit/arvo` pull request](https://github.com/urbit/arvo/pull/610) that implements permissions for Urbit’s Clay filesystem, which Ted merged this week. Among other things, this will play a pivotal role in the new _Collections_ app actively being worked on, so that an Urbit user can store private notes, create invite-only fora and blogs, and collect a private archive of typed documents, all while maintaining referential transparency in the global immutable namespace.

28+*Mark* `~palfun-foslup` submitted an [`urbit/arvo` pull request](https://github.com/urbit/arvo/pull/610) that implements permissions for Urbit's Clay filesystem, which Ted merged this week. Among other things, this will play a pivotal role in the new _Collections_ app actively being worked on, so that an Urbit user can store private notes, create invite-only fora and blogs, and collect a private archive of typed documents, all while maintaining referential transparency in the global immutable namespace.

29

30−*Ted* `~rovnys-ricfer` and *Keaton* `~tonlur-sarret` have been working on a design for the data structures and control flow for the next version of Ford, Urbit’s build system. We’ll post to Fora once we’ve revised it some more.

30+*Ted* `~rovnys-ricfer` and *Keaton* `~tonlur-sarret` have been working on a design for the data structures and control flow for the next version of Ford, Urbit's build system. We'll post to Fora once we've revised it some more.

31

32−*Joshua* `~taglux-nidsep` rejoined [Mars Talk this week](https://www.youtube.com/watch?v=--hvpMqIeSA) as host with Ted and Keaton for Episode 21. We decided to take a break from deep technical talk to chat about the proposed _Nock 4K_ spec (a cosmic event in the Urbit universe), Josh’s dissertation, Vere parallelism, and Urbit as a personal command center to call out to Earth blockchains.

32+*Joshua* `~taglux-nidsep` rejoined [Mars Talk this week](https://www.youtube.com/watch?v=--hvpMqIeSA) as host with Ted and Keaton for Episode 21. We decided to take a break from deep technical talk to chat about the proposed _Nock 4K_ spec (a cosmic event in the Urbit universe), Josh's dissertation, Vere parallelism, and Urbit as a personal command center to call out to Earth blockchains.

33

34Have a great weekend, everyone!

static-site/posts/updates/2018.2.24-update.udon+5−5

@@ -8,15 +8,15 @@

8

9# ~2018.2.24 Update

10

11−This week was another busy one at the Tlon office. Here’s what we were up to.

11+This week was another busy one at the Tlon office. Here's what we were up to.

12

13−This week we performed another [continuity breach](https://urbit.org/docs/using/admin/#-continuity-breaches). Now that we’ve fixed most of the bugs in new Talk, we think the network is going to be pretty smooth for a while. If you haven’t already, follow our [setup](https://urbit.org/docs/using/setup) doc again to reboot your planet in this new continuity era. If you’d like a planet, [email me](mailto:keaton@tlon.io)!

13+This week we performed another [continuity breach](https://urbit.org/docs/using/admin/#-continuity-breaches). Now that we've fixed most of the bugs in new Talk, we think the network is going to be pretty smooth for a while. If you haven't already, follow our [setup](https://urbit.org/docs/using/setup) doc again to reboot your planet in this new continuity era. If you'd like a planet, [email me](mailto:keaton@tlon.io)!

14

15−We’re hosting a [Meetup now](https://www.meetup.com/urbit-sf/events/247797527/) at the Tlon office. *Josh* `~taglux-nidsep` is in town, and we all need a drink after the breach. Bring your laptop, stop by for a beer, and let us install Urbit for you. Or just relax and talk to people.

15+We're hosting a [Meetup now](https://www.meetup.com/urbit-sf/events/247797527/) at the Tlon office. *Josh* `~taglux-nidsep` is in town, and we all need a drink after the breach. Bring your laptop, stop by for a beer, and let us install Urbit for you. Or just relax and talk to people.

16

17*Mark* `~palfun-foslup` had a number of PRs merged this week for various bug fixes to Talk and Hall.

18

19−*Joe* `~master-morzod` fixed several issues with Urbit’s terminal.

19+*Joe* `~master-morzod` fixed several issues with Urbit's terminal.

20

21*Anton* `~pittyp-datfyn` made a one-line fix in Ford that fixed a major bug in cache performance. As a result, the website and Fora feel snappier.

22

@@ -26,6 +26,6 @@ We’re hosting a [Meetup now](https://www.meetup.com/urbit-sf/events/247797527/

26

27*Curtis* `~sorreg-namtyv` is finishing up work on Hoon type defaulting, and has started working on a new design for the Hoon pretty printer.

28

29−Josh, Ted and Keaton took a hiatus from Mars Talk this week to discuss future plans. We’ll be back next week, better than ever.

29+Josh, Ted and Keaton took a hiatus from Mars Talk this week to discuss future plans. We'll be back next week, better than ever.

30

31Have a great weekend!

static-site/posts/updates/2018.2.5-update.udon+4−4

@@ -10,9 +10,9 @@

10

11*Galen* `~ravmel-ropdyl`, *Jimmy* `~haptyl-wanwes`, and *Chris* `~sigtus-hossyn` worked on the upcoming frontend overhaul, including the new homepage, the _Collections_ and _Streams_ apps, and the primer. *Ted* `~rovnys-ricfer` and *Anton* `~pittyp-datfyn` continued to work on Ford.

12

13−*Curtis* `~sorreg-namtyv` worked on fixing the defaulting behavior in Hoon. “The future is not wonky,” he declares.

13+*Curtis* `~sorreg-namtyv` worked on fixing the defaulting behavior in Hoon. "The future is not wonky," he declares.

14

15−*Keaton* `~tonlur-sarret` tested Isaac V’s Fora implementation using his static `ren/tree`. It works.

15+*Keaton* `~tonlur-sarret` tested Isaac V's Fora implementation using his static `ren/tree`. It works.

16

17*Mark* `~palfun-foslup` gave a presentation at the FOSDEM open source conference in Belgium. Video can be found [here](https://www.youtube.com/watch?v=U-QBW6QIDto).

18

@@ -20,8 +20,8 @@

20

21*Paul* `~fodwyt-ragful` [fixed a performance issue](https://github.com/urbit/urbit/pull/920) in unifying large nouns.

22

23−*Iceman* `~littel-ponnys`’s testing framework has been merged into master. To use the framework to write unit tests, see the [user guide](https://github.com/urbit/arvo/blob/master/web/testing.umd). This pull request also includes a Hoon port of [Haskell’s Prelude](https://hackage.haskell.org/package/base-4.10.1.0/docs/Prelude.html), which is [now available](https://github.com/urbit/arvo/blob/master/lib/new-hoon.hoon) as an alternate version of the Hoon standard library, including [unit tests](https://github.com/urbit/arvo/tree/master/tests/new-hoon). Discussion of this subject can be found on [Fora](https://fora.urbit.org/posts/~2017.10.17..04.09.16..7eb8~/).

23+*Iceman* `~littel-ponnys`'s testing framework has been merged into master. To use the framework to write unit tests, see the [user guide](https://github.com/urbit/arvo/blob/master/web/testing.umd). This pull request also includes a Hoon port of [Haskell's Prelude](https://hackage.haskell.org/package/base-4.10.1.0/docs/Prelude.html), which is [now available](https://github.com/urbit/arvo/blob/master/lib/new-hoon.hoon) as an alternate version of the Hoon standard library, including [unit tests](https://github.com/urbit/arvo/tree/master/tests/new-hoon). Discussion of this subject can be found on [Fora](https://fora.urbit.org/posts/~2017.10.17..04.09.16..7eb8~/).

24

25−On [Mars Talk Episode 19](https://www.youtube.com/watch?v=q3Fjnv0RcR0) (our 20th episode!) this week, Keaton and Ted explained Ford, Urbit’s functional reactive build system.

25+On [Mars Talk Episode 19](https://www.youtube.com/watch?v=q3Fjnv0RcR0) (our 20th episode!) this week, Keaton and Ted explained Ford, Urbit's functional reactive build system.

26

27`~rovnys-ricfer`

static-site/posts/updates/2018.2.9-update.udon+1−1

@@ -25,7 +25,7 @@ tackle. There's plenty of labels now for all your filtering needs. Internally, w

25wanted](https://github.com/urbit/arvo/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) every so often.

26While contributors can't add labels themselves, we'll make sure your issues get tagged correctly. Enjoy!

27

28−*Curtis* `~sorreg-namtyv` has been helping Ted and *Anton* `~pittyp-datfyn` with Ford. He’s also continued his work on

28+*Curtis* `~sorreg-namtyv` has been helping Ted and *Anton* `~pittyp-datfyn` with Ford. He's also continued his work on

29improving default values for types in Hoon.

30

31*Keaton* `~tonlur-sarret` has been working on a super-secret project that he cannot discuss. Loose lips sink ships ...

static-site/posts/updates/2018.3.24-update.udon+10−10

@@ -8,9 +8,9 @@

8

9# ~2018.3.24 Update

10

11−We’ve had a busy past few weeks here at Tlon -- here’s an update:

11+We've had a busy past few weeks here at Tlon -- here's an update:

12

13−We hired some people! We’ve added to the full-time team:

13+We hired some people! We've added to the full-time team:

14

15- *Chris* `~sigtus-hossyn`

16- *Jimmy* `~haptyl-wanwes`

@@ -18,14 +18,14 @@ We hired some people! We’ve added to the full-time team:

18- *Anthony* `~poldec-tonteg`

19- *Elliot* `~littel-ponnys`

20

21−Tonight we’re hosting a [meetup](https://www.meetup.com/urbit-sf/events/248852261/) at the Tlon office. It’s a party.

21+Tonight we're hosting a [meetup](https://www.meetup.com/urbit-sf/events/248852261/) at the Tlon office. It's a party.

22−Morgan is DJing. Galen’s showing Beat Takeshi movies on the back wall. Bring your laptop, and we can write Fizzbuzz in

22+Morgan is DJing. Galen's showing Beat Takeshi movies on the back wall. Bring your laptop, and we can write Fizzbuzz in

23Hoon together. Or just relax, have some drinks, and talk to the weird array of people who also want to replace the

24internet.

25

26−*Curtis* `~sorreg-namtyv` is in the Netherlands this week visiting *Mark* `~palfun-foslup`. They’re self-auditing the

26+*Curtis* `~sorreg-namtyv` is in the Netherlands this week visiting *Mark* `~palfun-foslup`. They're self-auditing the

27last parts of the [Urbit Constitution](https://github.com/urbit/constitution). While sitting in Gatwick Airport, Curtis

28−also wrote up some ideas he’s been thinking about. Check out these essay drafts, posted to Fora:

28+also wrote up some ideas he's been thinking about. Check out these essay drafts, posted to Fora:

29

30- [The Urbit public record draft](https://fora.urbit.org/posts/~2018.3.23..03.42.41..ab6d~)

31- [Spirit and practice of digital homecoming draft](https://fora.urbit.org/posts/~2018.3.22..19.46.35..3499~)

@@ -38,19 +38,19 @@ also wrote up some ideas he’s been thinking about. Check out these essay draft

38

39- [UP 4 - Ford Turboencabulator](https://fora.urbit.org/posts/~2018.3.15..04.24.35..a47f~)

40

41−It’s a monster post, but if you’re a systems geek and want to read into the redesign of this important kernel module,

41+It's a monster post, but if you're a systems geek and want to read into the redesign of this important kernel module,

42check it out.

43

44−Ted’s and Elliot’s daily Ford progress can be tracked here:

44+Ted's and Elliot's daily Ford progress can be tracked here:

45

46−- [`urbit/arvo ‘ford-turbo’`](https://github.com/urbit/arvo/tree/ford-turbo)

46+- [`urbit/arvo 'ford-turbo'`](https://github.com/urbit/arvo/tree/ford-turbo)

47

48*Joshua* `~taglux-nidsep`, Ted, and Keaton debuted _Mars Talk, Season 2_ on Wednesday night. To reboot the show, we gave

49a high-level overview of the Urbit stack for new developers:

50

51- [Mars Talk Season 2, Ep. 1: High-Level Overview of the Urbit Stack](https://www.youtube.com/watch?v=UaRZVxthVeY)

52

53−Subscribe to [Josh’s channel](https://www.youtube.com/channel/UC3c0F4NhOD1LT5A1ShXEWiQ), and tune in weekly for all your

53+Subscribe to [Josh's channel](https://www.youtube.com/channel/UC3c0F4NhOD1LT5A1ShXEWiQ), and tune in weekly for all your

54latest and greatest educational content and Urbit news.

55

56See some of you at the meetup tonight, and the rest of you Hoons on the network.

static-site/posts/updates/2018.3.5-update.udon+3−3

@@ -17,7 +17,7 @@

17and are now converting it to a UP to be reviewed by the community.

18

19*Mark* `~palfun-foslup` submitted a [pull request](https://github.com/urbit/arvo/pull/651) that implements the _Keccak_

20−family of cryptographic hashing functions in Hoon, including `SHA-3`, `shake`, and `rawshake`. We’ll need `keccak` to

20+family of cryptographic hashing functions in Hoon, including `SHA-3`, `shake`, and `rawshake`. We'll need `keccak` to

21integrate Urbit with Ethereum.

22

23Also, [moons](https://urbit.org/docs/using/admin/#-moons) are back! You can run the `+moon` generator from your galaxy,

@@ -25,7 +25,7 @@ star or planet to create a ticket for a new moon. If you run your ship in the cl

25moon on your laptop and using that for Talk instead. Messages you send from your moon will appear to have been sent from

26your usual (parent) identity.

27

28−*Iceman* `~littel-ponnys` wrote some deep thoughts on Clay, Urbit’s filesystem, in this [meaty Fora

28+*Iceman* `~littel-ponnys` wrote some deep thoughts on Clay, Urbit's filesystem, in this [meaty Fora

29post](https://fora.urbit.org/posts/~2018.2.25..02.28.04..bd6d~/).

30

31−P.S. We’re hiring! If you’re interested, email `galen@tlon.io`.

31+P.S. We're hiring! If you're interested, email `galen@tlon.io`.

static-site/posts/updates/2018.4.14-update.udon+14−14

@@ -8,13 +8,13 @@

8

9# ~2018.4.14 Update

10

11−Replacing the internet is hard. Luckily, we have great people helping us do it. Here’s what’s new this week in Urbit:

11+Replacing the internet is hard. Luckily, we have great people helping us do it. Here's what's new this week in Urbit:

12

13We hired more people! Tlon is pleased to have with us:

14

15−- *Erik* `~patnes-rigtyn` - Erik is our new head of operations. He’ll be keeping us all fed and organized, as well as

15+- *Erik* `~patnes-rigtyn` - Erik is our new head of operations. He'll be keeping us all fed and organized, as well as

16 helping us with some legal things.

17−- *Joe* `~master-morzod` - Joe... well, [you know Joe](https://joemfb.github.io/ez-urbits/). He’s going to help us make

17+- *Joe* `~master-morzod` - Joe... well, [you know Joe](https://joemfb.github.io/ez-urbits/). He's going to help us make

18 Urbit easier.

19- *Logan* `~tacryt-socryp` - Logan is going to build us a mobile app, work on which has already begun! Very exciting,

20 indeed.

@@ -25,32 +25,32 @@ use a worklist data structure. This will not only be simpler to reason about, bu

25support for parallelization of builds at the Vere level in MapReduce fashion. Their work is on

26[Github](https://github.com/urbit/arvo/tree/ford-turbo).

27

28−*Curtis* `~sorreg-namtyv` has been working hard to make Hoon’s type system less confusing, as well as working on the

28+*Curtis* `~sorreg-namtyv` has been working hard to make Hoon's type system less confusing, as well as working on the

29−problem of data inspection in Hoon. Now that his “structure-to-type” code is mostly done (going from an abstract type

29+problem of data inspection in Hoon. Now that his "structure-to-type" code is mostly done (going from an abstract type

30−definition to its real compiled internal representation), he’ll soon be done with his “type-to-structure” reverse

30+definition to its real compiled internal representation), he'll soon be done with his "type-to-structure" reverse

31converter for getting abstract structure data out of any sets of values. More soon, but all of this will supersede the

32current mold system and help make Hoon easier to understand, we think.

33

34*Galen* `~ravmel-ropdyl`, *Anton* `~pittyp-datfyn`, *Jimmy* `~haptyl-wanwes`, *Gavin* `~ridlur-figbud`, *Chris*

35−`~sigtus-hossyn`, and *Logan* `~tacryt-socryp` have been putting in more hard work on the new Urbit frontend. It’s all

35+`~sigtus-hossyn`, and *Logan* `~tacryt-socryp` have been putting in more hard work on the new Urbit frontend. It's all

36coming together really nicely, and things seem to be on schedule for a big mid-to-late summer release.

37

38−We haven’t posted an obscure graphic in a while. Here’s one for the update to tide you over:

38+We haven't posted an obscure graphic in a while. Here's one for the update to tide you over:

39

40;img@"https://media.urbit.org/fora/updates/~2018.4.13-Update-1.png"(width "100%");

41

42−What it’s for is totally top secret.

42+What it's for is totally top secret.

43

44*Keaton* `~tonlur-sarret` deployed sections to Fora, which will help categorize discussion content better and lead to better curation of StackOverflow-like questions and Urbit Proposals (UPs). He also merged some important pull requests into the system and deployed them to the network.

45

46−*Mikolaj* `~ponmep-litsem`’s contributor work on moving Vere from Make to the [Meson](https://github.com/mesonbuild/meson) build system was merged this week. This solves several issues with bundling of dependencies, as well as making binary builds generally faster. Great work!

46+*Mikolaj* `~ponmep-litsem`'s contributor work on moving Vere from Make to the [Meson](https://github.com/mesonbuild/meson) build system was merged this week. This solves several issues with bundling of dependencies, as well as making binary builds generally faster. Great work!

47

48−*Joe* `~master-morzod` got his [HTTP pull request](https://github.com/urbit/urbit/pull/942) finally merged, which rewrites Vere’s HTTP client and server to use the `h2o` library. This is great, as it will allow for full TLS termination in Urbit, which sets us up for full HTTPS connections to direct IP addresses of Urbit ships at `your-ship.urbit.org`, to be fully implemented soon.

48+*Joe* `~master-morzod` got his [HTTP pull request](https://github.com/urbit/urbit/pull/942) finally merged, which rewrites Vere's HTTP client and server to use the `h2o` library. This is great, as it will allow for full TLS termination in Urbit, which sets us up for full HTTPS connections to direct IP addresses of Urbit ships at `your-ship.urbit.org`, to be fully implemented soon.

49

50−*Robert* `~lodleb-ritrul` has made a number of helpful PR’s to the [Urbit docs](https://github.com/urbit/docs).

50+*Robert* `~lodleb-ritrul` has made a number of helpful PR's to the [Urbit docs](https://github.com/urbit/docs).

51

52*Mark* `~palfun-foslup` worked more on the Urbit constitution and put out some important fires caused by code-update syncs over the network and type mismatches. Computers are hard!

53

54−*Joshua* `~taglux-nidsep`, Ted, Keaton, and Joe went on [Mars Talk](https://www.youtube.com/watch?v=EZKNLcdRbE0) to discuss the Facebook data scandal, the greater battle for privacy and personal computing, and Urbit’s role in all of this. We think it turned out great.

54+*Joshua* `~taglux-nidsep`, Ted, Keaton, and Joe went on [Mars Talk](https://www.youtube.com/watch?v=EZKNLcdRbE0) to discuss the Facebook data scandal, the greater battle for privacy and personal computing, and Urbit's role in all of this. We think it turned out great.

55

56−All in all, life has been good over here. Now it’s time for a good weekend. See you all on the network!

56+All in all, life has been good over here. Now it's time for a good weekend. See you all on the network!

static-site/posts/updates/2018.4.7-update.udon+9−9

@@ -8,14 +8,14 @@

8

9# ~2018.4.7 Update

10

11−As always, the Urbit community has been working hard this week to replace the internet. Here’s a summary:

11+As always, the Urbit community has been working hard this week to replace the internet. Here's a summary:

12

13−We’re hosting [Hoon School](https://www.meetup.com/urbit-sf/events/249019207/) at our San Francisco office this Sunday. Come, bring your laptop, and we’ll get you started building things in Urbit’s language -- Hoon.

13+We're hosting [Hoon School](https://www.meetup.com/urbit-sf/events/249019207/) at our San Francisco office this Sunday. Come, bring your laptop, and we'll get you started building things in Urbit's language -- Hoon.

14

15−Tlon has brought on two new interns! We’re excited to have with us:

15+Tlon has brought on two new interns! We're excited to have with us:

16

17−- *Gavin* `~ridlur-figbud` - Gavin’s going to help us with some promising frontend design projects.

17+- *Gavin* `~ridlur-figbud` - Gavin's going to help us with some promising frontend design projects.

18−- *Robert* `~lodleb-ritrul` - Robert’s going to work with us on revamping our documentation, examples, and blog, writing

18+- *Robert* `~lodleb-ritrul` - Robert's going to work with us on revamping our documentation, examples, and blog, writing

19 high-quality original content. He has submitted several pull requests to the docs already this week, which have been

20 merged.

21

@@ -23,18 +23,18 @@ Tlon has brought on two new interns! We’re excited to have with us:

23continuing to advance the state of the new Urbit frontend.

24

25*Mark* `~palfun-foslup` has been working hard with *Curtis* `~sorreg-namtyv` to bring the Urbit constitution into its

26−final, launchable state. He believes it’s ready for its final security audit, which keeps us on track to launch it this

26+final, launchable state. He believes it's ready for its final security audit, which keeps us on track to launch it this

27summer. You can find the latest contract code [here](https://github.com/urbit/constitution).

28

29*Ted* `~rovnys-ricfer` and *Elliot* `~littel-ponnys` have assembled a basic prototype of the main engine of the new Ford

30−redesign. They’ve been improving the design as they go, posting updates as comments to the [original Fora

30+redesign. They've been improving the design as they go, posting updates as comments to the [original Fora

31post](https://fora.urbit.org/posts/~2018.3.15..04.24.35..a47f~/). Their code can be found

32[here](https://github.com/urbit/arvo/tree/ford-turbo).

33

34Lastly, big shoutout to *Mikolaj* `~ponmep-litsem` for his work on [Plato](http://plato.urbitetorbi.org:8080/plato.html),

35which now allows remote Hoon code execution without logging in. This is a big step towards improving our developer

36onboarding, as it will allow newcomers to experience interactive Urbit programming in the browser quickly without having

37−to wait to boot their own ship. See Mikolaj’s original thread on Github [here](https://github.com/urbit/docs/issues/239).

37+to wait to boot their own ship. See Mikolaj's original thread on Github [here](https://github.com/urbit/docs/issues/239).

38

39We look forward to teaching some of you this Sunday the beginnings of the art of Martian functional programming. To all

40−else, we’ll see you on the network. Have a great weekend, everybody!

40+else, we'll see you on the network. Have a great weekend, everybody!

static-site/posts/updates/2018.5.16-update.udon+13−13

@@ -8,19 +8,19 @@

8

9# ~2018.5.16 Update

10

11−Summer is around the corner, and the community has been working hard to make Urbit real. Here’s an update on what new and exciting things have been happening:

11+Summer is around the corner, and the community has been working hard to make Urbit real. Here's an update on what new and exciting things have been happening:

12

13−> _Meta_: We’re going to start posting these to the new *Updates* section in Fora now -- and actually weekly!

13+> _Meta_: We're going to start posting these to the new *Updates* section in Fora now -- and actually weekly!

14

15−On [Mars Talk last week](https://www.youtube.com/watch?v=gBd0TZyz_HE), *Anthony* `~poldec-tonteg`, *Joshua* `~taglux-nidsep`, *Ted* `~rovnys-ricfer`, and *Keaton* `~tonlur-sarret` talked about Sail, a DSL for representing XML/HTML data in Hoon. We built a simple web page with Sail and highlighted what features Sail gives you, like Hoon’s type system, the Ford build system, and full access to Hoon programming inline. Check it out!

15+On [Mars Talk last week](https://www.youtube.com/watch?v=gBd0TZyz_HE), *Anthony* `~poldec-tonteg`, *Joshua* `~taglux-nidsep`, *Ted* `~rovnys-ricfer`, and *Keaton* `~tonlur-sarret` talked about Sail, a DSL for representing XML/HTML data in Hoon. We built a simple web page with Sail and highlighted what features Sail gives you, like Hoon's type system, the Ford build system, and full access to Hoon programming inline. Check it out!

16

17−Tlon hired someone this week! We’re excited to have with us:

17+Tlon hired someone this week! We're excited to have with us:

18

19- *Isaac V* `~davtyr-nimren`

20

21−Isaac has solid Hoon and frontend chops, having already implemented server-side rendering of Tree pages for us a short while back. He’ll be taking on some of the Collections/Streams work to help us get ready for our summer release.

21+Isaac has solid Hoon and frontend chops, having already implemented server-side rendering of Tree pages for us a short while back. He'll be taking on some of the Collections/Streams work to help us get ready for our summer release.

22

23−*Galen* `~ravmel-ropdyl`, *Anthony* `~poldec-tonteg`, *Chris* `~sigtus-hossyn`, *Gavin* `~ridlur-figbud`, and *Jimmy* `~haptyl-wanwes` have been working more on the new interface projects. Here’s another leak:

23+*Galen* `~ravmel-ropdyl`, *Anthony* `~poldec-tonteg`, *Chris* `~sigtus-hossyn`, *Gavin* `~ridlur-figbud`, and *Jimmy* `~haptyl-wanwes` have been working more on the new interface projects. Here's another leak:

24

25![New visual leak](https://media.urbit.org/fora/updates/~2018.5.15-Update-1.png)

26

@@ -28,24 +28,24 @@ Isaac has solid Hoon and frontend chops, having already implemented server-side

28

29*Curtis* `~sorreg-namtyv` has been working more on several important major language feature improvements to Hoon: namely, pretty-printing of typed data, and simplifying the type system. Work can be found on his [research branches](https://github.com/cgyarvin/arvo), but we plan on publishing a more formal post of the changes and major documentation updates when they roll out in the coming months. More soon!

30

31−*Ted* `~rovnys-ricfer` and *Elliot* `~littel-ponnys` have made a bunch of progress on Ford Turbo. In addition to having a proof-of-concept solution for the main performance bottleneck of current Ford, they’ve now finished writing over half of the schematics (build types), implemented proper cache reclamation support, and they’ve gotten basic Clay integration functioning properly. You can find their work [here](https://github.com/urbit/arvo/tree/ford-turbo). They’re posting more detailed updates as comments to their original [Urbit Proposal](https://fora.urbit.org/proposals/posts/~2018.3.15..04.24.35..a47f~/).

31+*Ted* `~rovnys-ricfer` and *Elliot* `~littel-ponnys` have made a bunch of progress on Ford Turbo. In addition to having a proof-of-concept solution for the main performance bottleneck of current Ford, they've now finished writing over half of the schematics (build types), implemented proper cache reclamation support, and they've gotten basic Clay integration functioning properly. You can find their work [here](https://github.com/urbit/arvo/tree/ford-turbo). They're posting more detailed updates as comments to their original [Urbit Proposal](https://fora.urbit.org/proposals/posts/~2018.3.15..04.24.35..a47f~/).

32

33*Mark* `~palfun-foslup` has been wrapping up Urbit/ETH integration, and is now working on getting Jael, the new Arvo secret-storage vane, to compile. This would be a great addition to the summer release.

34

35*Joshua* `~taglux-nidsep`, *Robert* `~lodleb-ritrul`, and *Keaton* `~tonlur-sarret` have been getting lots of

36−documentation work done. They’ve seen several PR’s go through to improve the Hoon standard library docs, simplify the

36+documentation work done. They've seen several PR's go through to improve the Hoon standard library docs, simplify the

37−Hoon demo, update our examples to the latest syntax, improve the Urbit installation process, and more. Josh’s

37+Hoon demo, update our examples to the latest syntax, improve the Urbit installation process, and more. Josh's

38work-in-progress is happening [here](https://github.com/joshuareagan/doc-drafts/). The main docs are [on

39−Github](https://github.com/urbit/docs): if there’s a piece of doc that’s confusing to you, don’t hesitate to file an

39+Github](https://github.com/urbit/docs): if there's a piece of doc that's confusing to you, don't hesitate to file an

40issue. Or better, submit a pull request.

41

42−*Joe* `~master-morzod` is making strides on full HTTPS support for individual ships. He’s implemented LetsEncrypt

42+*Joe* `~master-morzod` is making strides on full HTTPS support for individual ships. He's implemented LetsEncrypt

43support, ASN.1, and has Dynamic DNS functioning on our testnet. When all this work is done, `your-ship.urbit.org` should

44−connect automatically to the IP of the Unix machine your urbit is running on, rather than connecting to one of Tlon’s

44+connect automatically to the IP of the Unix machine your urbit is running on, rather than connecting to one of Tlon's

45ships, which currently proxies Urbit network data through one of our stars, is slow, and is basically a straight-up

46man-in-the-middle. Combined with private Collections and Streams, Urbit will be a lot more secure and usable within the

47year.

48

49−Overall, we’re making progress. More next week!

49+Overall, we're making progress. More next week!

50

51`~tonlur-sarret`

static-site/posts/updates/2018.5.23-update.udon+13−13

@@ -8,17 +8,17 @@

8

9# ~2018.5.23 Update

10

11−Here’s a short update from Tlon for the week of `~2018.5.22`:

11+Here's a short update from Tlon for the week of `~2018.5.22`:

12

13;img@"https://media.urbit.org/fora/updates/~2018.5.22-Update-1.jpg"(width "100%");

14

15−We’re hosting a meetup [this Friday](https://www.meetup.com/urbit-sf/events/250889557/) at the SF office. Ted will give a

15+We're hosting a meetup [this Friday](https://www.meetup.com/urbit-sf/events/250889557/) at the SF office. Ted will give a

16−quick update on new Ford, and then it’ll be time to relax, listen to music (our friend Grayson will be playing records),

16+quick update on new Ford, and then it'll be time to relax, listen to music (our friend Grayson will be playing records),

17and talk IRL. Feel free to bring your laptop, and we'll install Urbit for you and give you a tour of Arvo.

18

19This week, the interface team -- *Galen* `~ravmel-ropdyl`, *Gavin* `~ridlur-figbud`, *Jimmy* `~haptyl-wanwes`, *Chris*

20`~sigtus-hossyn`, *Isaac V* `~davtyr-nimren`, *Logan* `~tacryt-socryp`, and *Anthony* `~poldec-tonteg` -- has continued

21−building the new Arvo frontend. Here’s a teaser of something the desktop guys have been working on:

21+building the new Arvo frontend. Here's a teaser of something the desktop guys have been working on:

22

23;img@"https://media.urbit.org/fora/updates/~2018.5.22-Update-2.jpg"(width "100%");

24

@@ -37,27 +37,27 @@ bulleted steps [here](https://gist.github.com/keatondunsford/8c19bc232650ec1adbb

37*Ted* `~rovnys-ricfer` and *Elliot* `~littel-ponnys` are getting their new beautiful build system closer to the finish

38line. New Ford supports nearly all of the functionality laid out in the original [Urbit

39Proposal](https://fora.urbit.org/proposals/posts/~2018.3.15..04.24.35..a47f~/) and passes all current tests. This past

40−week, Ted and Elliot have implemented more schematics and a bunch of the `+cranes`, or Ford runes. If you’re into build

40+week, Ted and Elliot have implemented more schematics and a bunch of the `+cranes`, or Ford runes. If you're into build

41−systems, check out their more detailed updates they’ve been posting as comments to the UP.

41+systems, check out their more detailed updates they've been posting as comments to the UP.

42

43−*Mark* `~palfun-foslup` has been working on getting the Urbit/ETH integration logic into Jael, Arvo’s new secret-storage

43+*Mark* `~palfun-foslup` has been working on getting the Urbit/ETH integration logic into Jael, Arvo's new secret-storage

44vane, to go live in the summer MVE release. Part of this is implementing direct support for querying the Ethereum

45blockchain for the state of the the Urbit constitution smart contract. In this model, Urbit ships can choose to either

46get this state directly from their parent stars or galaxies, or they can query the blockchain themselves. An important

47−step towards making Urbit address-space ownership real, Mark’s work-in-progress can be found

47+step towards making Urbit address-space ownership real, Mark's work-in-progress can be found

48[here](https://github.com/Fang-/arvo/tree/research-constitution).

49

50−*Josh* `~taglux-nidsep` and *Robert* `~lodleb-ritrul` have been continuing to do ~zod’s work to improve the state of the

50+*Josh* `~taglux-nidsep` and *Robert* `~lodleb-ritrul` have been continuing to do ~zod's work to improve the state of the

51Urbit documentation. Josh has been writing a [new Hoon tutorial series](https://github.com/joshuareagan/doc-drafts) to

52supersede the current Urbytes, while Robert has been blazing a trail through the current standard library docs, making

53−sure they’re up-to-date and [improving them](https://github.com/urbit/docs/tree/rmariani-patch-6) as he goes. There’s

53+sure they're up-to-date and [improving them](https://github.com/urbit/docs/tree/rmariani-patch-6) as he goes. There's

54−been a lot of activity on Github recently. Don’t be shy: [submit your first docs pull

54+been a lot of activity on Github recently. Don't be shy: [submit your first docs pull

55request](https://github.com/urbit/docs), a classic rite of passage for the neophyte Hoon programmer.

56

57−Lastly, Josh, Ted, and Keaton will be live on Mars Talk tomorrow night, Wednesday at 8:30PM PST. We’ll post the Hangouts

57+Lastly, Josh, Ted, and Keaton will be live on Mars Talk tomorrow night, Wednesday at 8:30PM PST. We'll post the Hangouts

58link in Talk. Tune in!

59

60−Overall, summer is getting closer, and we’re excited about the work that’s getting done. More this week.

60+Overall, summer is getting closer, and we're excited about the work that's getting done. More this week.

61

62See you on Friday!

63

static-site/posts/updates/2018.5.30-update.udon+20−20

@@ -8,57 +8,57 @@

8

9# ~2018.5.30 Update

10

11−Here’s an update from the team at Tlon for the week of `~2018.5.30`:

11+Here's an update from the team at Tlon for the week of `~2018.5.30`:

12

13;img@"https://media.urbit.org/fora/updates/~2018.5.30-Update-1.jpg"(width "100%");

14

15We had a great meetup last Friday. Thanks to Ted for talking about Ford, Grayson and Morgan for DJing, and everyone for

16−showing up! We’ll keep you updated about the next one.

16+showing up! We'll keep you updated about the next one.

17

18We performed a [continuity breach](https://urbit.org/docs/using/admin/#-continuity-breaches) last week. This means that,

19−if you haven’t already, you need to recreate your urbit. The good news is: the network is faster, people are hanging out

19+if you haven't already, you need to recreate your urbit. The good news is: the network is faster, people are hanging out

20in in `/urbit-meta`, and a couple of infrastructure changes were made to make `urbit.org` authentication and proxying a

21bit more snappy. See [this post](https://fora.urbit.org/general/posts/~2018.5.26..03.57.28..7b26~/) for help getting set

22back up.

23

24*Curtis* `~sorreg-namtyv` has been working more on data printing in Hoon. Still work-in-progress, the end result will

25have new, simpler ways to express Hoon types, data you want to print, helpful conversion arms accessible via the standard

26−library, and a couple new runes. If you like deep language code and compiler internals, you can check out Curtis’s

26+library, and a couple new runes. If you like deep language code and compiler internals, you can check out Curtis's

27research branch [here](https://github.com/cgyarvin/arvo/tree/research-tome).

28

29The interface team -- *Galen* `~ravmel-ropdyl`, *Anthony* `~poldec-tonteg`, *Logan* `~tacryt-socryp`, *Chris*

30−`~sigtus-hossyn`, *Jimmy* `~haptyl-wanwes`, and *Gavin* `~ridlur-figbud` -- has been working more on MVE. We’ll have more

30+`~sigtus-hossyn`, *Jimmy* `~haptyl-wanwes`, and *Gavin* `~ridlur-figbud` -- has been working more on MVE. We'll have more

31to show in the next couple weeks.

32

33*Isaac V* `~davtyr-nimren` worked on Arvo and Collections last week. He implemented a query parameter in Eyre to support

34setting the longpoll timeout duration manually, which solves an issue in the way of us doing background refreshes in our

35−iOS app we’re developing. He also got Clay permissions logic into Collections so that the tool will support read-only,

35+iOS app we're developing. He also got Clay permissions logic into Collections so that the tool will support read-only,

36−write-only, and private/invite-only collections in addition to public ones. Lastly, Isaac’s been working on a static-site

36+write-only, and private/invite-only collections in addition to public ones. Lastly, Isaac's been working on a static-site

37generator in Urbit to support more performance-ready web serving over Nginx in tandem with Eyre. The first step was

38−modifying Kiln to support batch-writing multiple files to Clay at once. Isaac’s work-in-progress can be found

38+modifying Kiln to support batch-writing multiple files to Clay at once. Isaac's work-in-progress can be found

39−[here](https://github.com/ixv/arvo/branches) -- check it out if you’re looking to start hacking near the border between

39+[here](https://github.com/ixv/arvo/branches) -- check it out if you're looking to start hacking near the border between

40−Arvo’s interface and infrastructure.

40+Arvo's interface and infrastructure.

41

42*Ted* `~rovnys-ricfer` and *Elliot* `~littel-ponnys` finished _all_ of the new Ford Turbo schematics (Ford build types)

43and a bunch more cranes (Ford runes). Their next step is to integrate new Ford with the current master kernel by loading

44it in as a separate vane, then incrementally connecting the wires needed for it to start working together with real Arvo.

45−You can find Ted and Elliot’s work [here](https://github.com/urbit/arvo/tree/ford-turbo). If you’re into functional

45+You can find Ted and Elliot's work [here](https://github.com/urbit/arvo/tree/ford-turbo). If you're into functional

46programming, build systems, or just want to read the best Hoon code we have on display currently, check it out, and the

47−updates they’ve been posting to their Urbit Proposal

47+updates they've been posting to their Urbit Proposal

48[here](https://fora.urbit.org/proposals/posts/~2018.3.15..04.24.35..a47f~).

49

50−*Mark* `~palfun-foslup` worked on Jael, Urbit’s new secret-storage vane, which we’re also expanding to include the logic

50+*Mark* `~palfun-foslup` worked on Jael, Urbit's new secret-storage vane, which we're also expanding to include the logic

51for querying the state of the [Urbit consitution](https://github.com/urbit/constitution) which will go live on the

52−Ethereum blockchain in the coming months. Mark has been implementing the necessary Arvo `+gift`s and `+task`s of Jael’s

52+Ethereum blockchain in the coming months. Mark has been implementing the necessary Arvo `+gift`s and `+task`s of Jael's

53−to properly interface with the Urbit constitution via the Ethereum API, then update the local urbit’s state of the land

53+to properly interface with the Urbit constitution via the Ethereum API, then update the local urbit's state of the land

54−registry and other contract data so that it can use it for networking and in other services. You can find Mark’s

54+registry and other contract data so that it can use it for networking and in other services. You can find Mark's

55−work-in-progress [here](https://github.com/Fang-/arvo/tree/research-constitution). Check it out if you’re excited by

55+work-in-progress [here](https://github.com/Fang-/arvo/tree/research-constitution). Check it out if you're excited by

56blockchains, or also just want to see what good, documented Hoon code looks like.

57

58*Joe* `~master-morzod` worked more on the HTTPS project. This week was mostly about refactoring the existing code by

59adding comments, renaming some things, and improving the style. Safe to say that when this project is done, we think it

60will be understandable. The ASN1 and PKCS libraries are mostly complete; progress will continue to finish up the last of

61−the libraries and necessary styling, then integrate this into current Arvo/Vere. Joe’s work-in-progress is

61+the libraries and necessary styling, then integrate this into current Arvo/Vere. Joe's work-in-progress is

62[here](https://github.com/joemfb/arvo/tree/acme-wip).

63

64*Josh* `~taglux-nidsep` and *Robert* `~lodleb-ritrul` made a bunch more progress on the docs. Josh has been adding more

@@ -66,11 +66,11 @@ to his [new WIP Hoon tutorials](https://github.com/joshuareagan/doc-drafts), and

66several [pull requests](https://github.com/urbit/docs/pulls) documenting the simple but elusive `=,` rune and refactoring

67much of the existing standard library doc. The docs are a great place to start learning and contributing. [Check them

68out](https://github.com/urbit/docs) on Github, and [submit an issue](https://github.com/urbit/docs/issues), tagging Josh

69−and Rob, if you’re confused by anything, or think something is documented wrong.

69+and Rob, if you're confused by anything, or think something is documented wrong.

70

71Josh and Ted also did a [Mars Talk](https://www.youtube.com/watch?v=IgQo5aSezK4) this week -- Season 2, Episode 6 -- to

72help people get started with Hoon. They went through some simple onboarding steps and basic math functions to introduce

73−some of the fundamental concepts in Hoon. If you’re new to Hoon and not sure where to start, check out that episode, and

73+some of the fundamental concepts in Hoon. If you're new to Hoon and not sure where to start, check out that episode, and

74feel free to leave comments below here for feedback.

75

76Overall, work continues to wipe the slate of computing clean. More news next week.

static-site/posts/updates/2018.6.14-update.udon+16−16

@@ -8,22 +8,22 @@

8

9# ~2018.6.14 Update

10

11−Here’s a short update from the team at Tlon for the week of `~2018.6.13`:

11+Here's a short update from the team at Tlon for the week of `~2018.6.13`:

12

13;img@"https://media.urbit.org/fora/updates/~2018.6.13-Update-1.jpg"(width "100%");

14

15*Ted* `~rovnys-ricfer` and *J* `~leb / ~ribben-donnyl` had a great time in Boulder, CO last week at LambdaConf 2018. Ted

16gave his same Ford talk he gave at the last meetup to a small group there. We should see the video recording of that

17−published in a few months when the editing process is finished. J’s talk on Hoon was a success. He posted to Fora this

17+published in a few months when the editing process is finished. J's talk on Hoon was a success. He posted to Fora this

18week with a link to his slides and talk turned into article form for Martian consumption. Check it out

19[here](https://fora.urbit.org/general/posts/~2018.6.10..19.25.23..6f16~/)!

20

21−J also designed some [new T-shirts](https://urbit.threadless.com/). What a fan! We’re working on designing some new

21+J also designed some [new T-shirts](https://urbit.threadless.com/). What a fan! We're working on designing some new

22official ones ourselves, but until then, feel free to score one of these.

23

24We breached again last Friday. People were hitting a [nasty Vere issue](https://github.com/urbit/urbit/issues/996)

25between versions from a breaking change, but breaching fixed it. We posted a short reminder of post-breach steps to Fora

26−[here](https://fora.urbit.org/general/posts/~2018.6.9..08.37.48..f79a~/). Let us know if you’re hitting any issues

26+[here](https://fora.urbit.org/general/posts/~2018.6.9..08.37.48..f79a~/). Let us know if you're hitting any issues

27getting back up and running in the new continuity era.

28

29*Ted* `~rovnys-ricfer` and *Elliot* `~littel-ponnys` reunited this week after LambdaConf. Gall and Dojo on the

@@ -33,40 +33,40 @@ support for the promotion of one-time builds, useful for things like generators.

33

34The interface team -- *Galen* `~ravmel-ropdyl`, *Anthony* `~poldec-tonteg`, *Jimmy* `~haptyl-wanwes`, *Gavin*

35`~ridlur-figbud`, *Chris* `~sigtus-hossyn`, *Isaac* `~davtyr-nimren`, and *Logan* `~tacryt-socryp` -- has commenced

36−internal private alpha MVE testing on web and mobile. Our alpha Urbit iOS app is shipped to Apple’s TestFlight, and we’ve

36+internal private alpha MVE testing on web and mobile. Our alpha Urbit iOS app is shipped to Apple's TestFlight, and we've

37−all been having a blast testing it out on our phones. New web Talk in MVE even supports image display. We can’t wait to

37+all been having a blast testing it out on our phones. New web Talk in MVE even supports image display. We can't wait to

38ship this all soon -- just need to fix the last of bugs and design issues here and there first.

39

40;img@"https://media.urbit.org/fora/updates/~2018.6.13-Update-2.jpg"(width "100%");

41

42−*Curtis* `~sorreg-namtyv` worked more on Hoon. He’s been working on generalizing name binding by replacing `+toga` in

42+*Curtis* `~sorreg-namtyv` worked more on Hoon. He's been working on generalizing name binding by replacing `+toga` in

43`hoon.hoon` as part of the new Hoon doc integration. That work in progress is

44−[here](https://github.com/cgyarvin/arvo/tree/research-tome). He’s also been working on designing the “launch ceremony”

44+[here](https://github.com/cgyarvin/arvo/tree/research-tome). He's also been working on designing the "launch ceremony"

45for Urbit/Ethereum private keys with *Morgan* `~hidrel-fabtel` and *Will* for when we go on chain with our Urbit

46−constitution on ETH very soon. We’ll publish details about all of this once we’ve squared everything away.

46+constitution on ETH very soon. We'll publish details about all of this once we've squared everything away.

47

48*Mark* `~palfun-foslup` worked more on locking down the Urbit constitution by incorporating feedback from our audits and

49putting more safeguards around how address space is transferred. Martian soil is too valuable to be lost through a

50−fat-fingered Ethereum transaction or, worse, malice! We’ve also been working with some contributors out Texas way to get

50+fat-fingered Ethereum transaction or, worse, malice! We've also been working with some contributors out Texas way to get

51our MyEtherWallet fork up to speed with the latest, greatest contract work. You can check out those changes

52[here](https://github.com/urbit/etherwallet/pull/29)

53

54*Joe* `~master-morzod` is cranking away at setting up a reverse TCP proxy (and all of the associated machinery), so that

55we can scrap the Ames-based proxy currently done by ship.urbit.org and move over to real, live HTTPS termination for all

56ships. This is a major undertaking and has required `~master` to touch a lot of different parts of the system: Eyre,

57−Vere, Ames -- you name it. Once his head is above water, he’s going to write something up for us and tell us what he’s

57+Vere, Ames -- you name it. Once his head is above water, he's going to write something up for us and tell us what he's

58seen in his wanderings through the system.

59

60And *Josh* `~taglux-nidsep` and *Robert* `~lodleb-ritrul` have spent yet another week making the docs more awesome.

61−Josh’s new Hoon tutorials (WIP link: [here](https://github.com/joshuareagan/doc-drafts)) are nearing completion. Rob

61+Josh's new Hoon tutorials (WIP link: [here](https://github.com/joshuareagan/doc-drafts)) are nearing completion. Rob

62−opened up a couple more PR’s improving the standard-library docs. You can check the latest `urbit/docs` pull requests

62+opened up a couple more PR's improving the standard-library docs. You can check the latest `urbit/docs` pull requests

63[here](https://github.com/urbit/docs/pulls).

64

65−There’s also a third set of Hoon exercises which Josh posted to Fora

65+There's also a third set of Hoon exercises which Josh posted to Fora

66[here](https://fora.urbit.org/answers/posts/~2018.6.7..20.54.43..2261~/). Give them a shot!

67

68−No Mars Talk this week. Ted and Josh will return next week to talk about treaps, and where we’re using them in Arvo.

68+No Mars Talk this week. Ted and Josh will return next week to talk about treaps, and where we're using them in Arvo.

69

70−That’s it for this week!

70+That's it for this week!

71

72`~tonlur-sarret` and `~poldec-tonteg`

static-site/posts/updates/2018.6.21-update.udon+12−12

@@ -8,13 +8,13 @@

8

9# ~2018.6.21 Update

10

11−Here’s a short update from the team at Tlon for the week of `~2018.6.21`

11+Here's a short update from the team at Tlon for the week of `~2018.6.21`

12

13;img@"https://media.urbit.org/fora/updates/~2018.6.21-Update-1.png"(width "100%");

14

15The interface team -- *Galen* `~ravmel-ropdyl`, *Jimmy* `~haptyl-wanwes`,

16*Gavin* `~ridlur-figbud`, *Chris* `~sigtus-hossyn`, *Anthony* `~poldec-tonteg`, and *Isaac* `~davtyr-nimren` -- worked

17−more on MVE. We’re getting incrementally closer to being able to release a public beta. Life has been active on the

17+more on MVE. We're getting incrementally closer to being able to release a public beta. Life has been active on the

18testnet as the team coordinates to fix the last known bugs and design issues.

19

20*Logan* `~tacryt-socryp` noticed a lacking feature in Hall: read vs. unread messages, a common feature in most messaging

@@ -25,35 +25,35 @@ The constitution team -- *Mark* `~palfun-foslup`, *Curtis* `~sorreg-namtyv`, *Mo

25`~hadrud-lodsef`, *Anthony* `~poldec-tonteg`, and Texan *Ben* `~mirfet-hocbyt` -- has been continuing to work to get us

26on chain by the end of the summer. Mark has been fortifying some of the contracts and Arvo-side cryptography and Jael

27functionality, while Ben and Anthony continue to finalize the control flow of our `MyUrbitWallet` fork. Curtis, Morgan,

28−and Will are striding forward on designing the key-launch ceremony, more details of which we’ll publish soon. The latest

28+and Will are striding forward on designing the key-launch ceremony, more details of which we'll publish soon. The latest

29[constitution](https://github.com/urbit/constitution), [Urbit wallet](https://github.com/urbit/etherwallet), and

30[Arvo](https://github.com/Fang-/arvo/tree/research-constitution) code with the latest Jael work can all be found on

31GitHub.

32

33−*Curtis* `~sorreg-namtyv` worked more on Hoon, continuing to improve face-wrapping (variable naming) around values. He’s

33+*Curtis* `~sorreg-namtyv` worked more on Hoon, continuing to improve face-wrapping (variable naming) around values. He's

34−also been working on a couple of new runes, like `^#`, whose designs aren’t yet fully complete, but when they are, we’ll

34+also been working on a couple of new runes, like `^#`, whose designs aren't yet fully complete, but when they are, we'll

35−document and share with y’all. Curtis’ research [Arvo](https://github.com/cgyarvin/arvo/tree/research-tome) and

35+document and share with y'all. Curtis' research [Arvo](https://github.com/cgyarvin/arvo/tree/research-tome) and

36[Vere](https://github.com/cgyarvin/urbit-1/tree/research-tome) code can be found on GitHub.

37

38*Joe* `~master-morzod` worked more on HTTPS this past week and got some of his work merged into the `urbit/arvo`

39`collections` branch, which will go live with the MVE release. Included in the PR are new moves in Eyre and Ames to

40support his reverse TCP proxy, HTTPS server configuration changes, and child-ship IP address changes. Additionally added

41is a dynamic-DNS Gall app, which brings us closer to our envisioned ideal of getting `your-ship.urbit.org` to connect

42−directly to your ship’s IP address, rather than going through Tlon’s intermediary proxying ships. Our next step is to

42+directly to your ship's IP address, rather than going through Tlon's intermediary proxying ships. Our next step is to

43−deploy this to our internal testnet before releasing it into the wild. Joe’s work can be found

43+deploy this to our internal testnet before releasing it into the wild. Joe's work can be found

44[here](https://github.com/urbit/arvo/pull/752) on GitHub -- very exciting.

45

46*Ted* `~rovnys-ricfer` and *Elliot* `~littel-ponnys` now nearly have a fully-integrated Ford Turbo. They can boot a ship

47with a Clay that exclusively uses Ford Turbo and not old, slow Ford. Gall integration is also complete. Now they're

48focused on finishing the caching implementation, as well as a new `%walk` schematic to perform a graph-search through the

49−available marks for data conversion. Ted and Elliot’s work is [here](https://github.com/urbit/arvo/tree/ford-turbo) on

49+available marks for data conversion. Ted and Elliot's work is [here](https://github.com/urbit/arvo/tree/ford-turbo) on

50GitHub, and their more detailed updates are [here](https://fora.urbit.org/proposals/posts/~2018.3.15..04.24.35..a47f~/)

51as comments to their original Fora post.

52

53And last, but not least, *Josh* `~taglux-nidsep` and *Robert* `~lodleb-ritrul` have continued their much-needed

54−doc-improvement work. Josh’s in-progress drafts of his new Hoon tutorials are

54+doc-improvement work. Josh's in-progress drafts of his new Hoon tutorials are

55−[here](https://github.com/joshuareagan/doc-drafts), and Rob’s latest pull requests improving the standard library docs

55+[here](https://github.com/joshuareagan/doc-drafts), and Rob's latest pull requests improving the standard library docs

56−are [here](https://github.com/urbit/docs/pulls). If there’s anything you feel should be documented and currently isn’t,

56+are [here](https://github.com/urbit/docs/pulls). If there's anything you feel should be documented and currently isn't,

57feel free to write us a comment below.

58

59May `~zod` be with you all. Have a great rest of your week.

static-site/posts/updates/2018.6.6-update.udon+24−24

@@ -8,72 +8,72 @@

8

9# ~2018.6.6 Update

10

11−Here’s a short update from the team at Tlon for the week of `~2018.6.6`:

11+Here's a short update from the team at Tlon for the week of `~2018.6.6`:

12

13;img@"https://media.urbit.org/fora/updates/~2018.6.6-Update-1.jpg";

14

15−We hired somebody! We’re happy to welcome to Tlon:

15+We hired somebody! We're happy to welcome to Tlon:

16

17- *Will* `~hadrud-lodsef` -- Will studied CS at Stanford and worked for years in VC. Among other things, he likes

18− ceramics and decentralized systems. He’s going to work on a mix of things for us, from operations to Urbit private-key

18+ ceramics and decentralized systems. He's going to work on a mix of things for us, from operations to Urbit private-key

19 distribution and management.

20

21The interface team -- *Galen* `~ravmel-ropdyl`, *Anthony* `~poldec-tonteg`, *Isaac V* `~davtyr-nimren`, *Jimmy*

22`~haptyl-wanwes`, *Chris* `~sigtus-hossyn`, *Logan* `~tacryt-socryp`, and *Gavin* `~ridlur-figbud` -- is narrowing in on

23an alpha version of MVE, nearing readiness to start testing internally. Anthony and Isaac have been getting our internal

24−testnet set up, and Logan is ready to submit our alpha iOS app to Apple’s TestFlight. We’ll keep you posted about public

24+testnet set up, and Logan is ready to submit our alpha iOS app to Apple's TestFlight. We'll keep you posted about public

25beta testing, on the way soon.

26

27*Isaac V* `~davtyr-nimren` finished an [in-Urbit static-site generator](https://github.com/urbit/arvo/pull/745) this

28−week. When merged, this will give you the option to easily host your urbit’s static files through a production-ready Unix

28+week. When merged, this will give you the option to easily host your urbit's static files through a production-ready Unix

29−web server like Nginx in tandem with Arvo’s web server, Eyre. This way, you can still host fast collections while we

29+web server like Nginx in tandem with Arvo's web server, Eyre. This way, you can still host fast collections while we

30−continue to work on Arvo’s performance.

30+continue to work on Arvo's performance.

31

32*Ted* `~rovnys-ricfer` has been at LambdaConf 2018 this week spreading the good news of `~zod` and

33non-lambda-calculus-based functional programming. Our good friend and galactic senator Justin LeBlanc `~leb` gave a talk,

34_Hoon and You - A Functional Programming Perspective_. Hopefully we can get slides and a video for you soon.

35

36−*Elliot* `~littel-ponnys` worked more on new Ford. It’s now working as its own separate vane in the kernel, `%turbo`, and

36+*Elliot* `~littel-ponnys` worked more on new Ford. It's now working as its own separate vane in the kernel, `%turbo`, and

37it reloads itself on Arvo `|reset`s and `|reload`s. While old `%ford` still exists, the next steps are to integrate

38`%turbo` with the rest of the system. Elliot has been working on a separate Dojo, _Dontjo_, that uses Turbo instead of

39old Ford. New Ford work is [here](https://github.com/urbit/arvo/tree/ford-turbo), and Fora updates are

40[here](https://fora.urbit.org/proposals/posts/~2018.3.15..04.24.35..a47f~/).

41

42−*Mark* `~palfun-foslup` has been wrapping up Urbit-on-ETH constitution work this week. We’re just about in our final lap,

42+*Mark* `~palfun-foslup` has been wrapping up Urbit-on-ETH constitution work this week. We're just about in our final lap,

43finalizing our audit reports, fixing the last of known bugs, upgrading the contracts to latest Solidity and OpenZeppelin

44versions, and rounding our our test coverage, code comments and documentation, and ERC721 compliance. The latest contract

45−code can be found [here](https://github.com/urbit/constitution). We’ll come out with an official email blast and

45+code can be found [here](https://github.com/urbit/constitution). We'll come out with an official email blast and

46−urbit.org post with more information when we’re all ready to go.

46+urbit.org post with more information when we're all ready to go.

47

48*Curtis* `~sorreg-namtyv` has been working more on Hoon. Notably, one new change on the table is switching the model-arm

49rune from `+=` to `+$`, keeping it more in line with the `$` family of Hoon syntax relating to models. The feedback from

50−the community in `/urbit-meta` on this was positive. Additionally, he’s been rethinking the `+toga` data structure for

50+the community in `/urbit-meta` on this was positive. Additionally, he's been rethinking the `+toga` data structure for

51dealing with faces (variable names) on Hoon values. His research branch is

52−[here](https://github.com/cgyarvin/arvo/tree/research-tome). We’ll have more to report next week.

52+[here](https://github.com/cgyarvin/arvo/tree/research-tome). We'll have more to report next week.

53

54−*Joe* `~master-morzod` has been continuing work on the HTTPS project. Notably this week, Joe’s been working on an

54+*Joe* `~master-morzod` has been continuing work on the HTTPS project. Notably this week, Joe's been working on an

55in-Urbit reverse TCP proxy, so that planets behind private networks / NATs can still have their data served to

56−`ship.urbit.org` via their star over Ames. With this last feature, in addition to Joe’s mostly-completed `libh2o`,

56+`ship.urbit.org` via their star over Ames. With this last feature, in addition to Joe's mostly-completed `libh2o`,

57LetsEncrypt, and dynamic-DNS Gall-app implementations, the fast and secure direct `ship.urbit.org` feature of MVE should

58−be primed to get tested into existence, then shipped. Joe’s latest work-in-progress is

58+be primed to get tested into existence, then shipped. Joe's latest work-in-progress is

59[here](https://github.com/joemfb/arvo/tree/reverse-proxy-notification).

60

61−*Josh* `~taglux-nidsep` and *Robert* `~lodleb-ritrul` blazed through more doc this week. Josh’s [new Hoon

61+*Josh* `~taglux-nidsep` and *Robert* `~lodleb-ritrul` blazed through more doc this week. Josh's [new Hoon

62tutorials](https://github.com/joshuareagan/doc-drafts) are starting to come together. Rob has been improving the

63standard-library docs and has open [several pull requests](https://github.com/urbit/docs/pulls), to be reviewed and

64merged this week. The docs are getting better.

65

66−If you haven’t already, give Josh’s Hoon exercises a shot! (aka Hoon Bootcamp) You can find exercise set #1 on Fora

66+If you haven't already, give Josh's Hoon exercises a shot! (aka Hoon Bootcamp) You can find exercise set #1 on Fora

67[here](https://fora.urbit.org/answers/posts/~2018.5.24/) and set #2

68[here](https://fora.urbit.org/answers/posts/~2018.6.1/).

69

70−With Ted out this week and Josh focused on doc work, they’re going to push back Mars Talk to next week. So, look out for

70+With Ted out this week and Josh focused on doc work, they're going to push back Mars Talk to next week. So, look out for

71−next week’s update for the time and topic of Season 2, Episode 7.

71+next week's update for the time and topic of Season 2, Episode 7.

72

73−One last reminder: [_there is no Urbit ICO_](https://urbit.org/updates/2018.5.29-no-ico). Anything else that you’ve heard

73+One last reminder: [_there is no Urbit ICO_](https://urbit.org/updates/2018.5.29-no-ico). Anything else that you've heard

74−is wrong. Don’t get scammed!

74+is wrong. Don't get scammed!

75

76−We hope you’ve been enjoying these weekly updates, now [actually weekly](https://urbit.org/blog/weekly-updates/).

76+We hope you've been enjoying these weekly updates, now [actually weekly](https://urbit.org/blog/weekly-updates/).

77−`/urbit-meta` has been really active lately. Don’t be shy to pop in and meet everybody.

77+`/urbit-meta` has been really active lately. Don't be shy to pop in and meet everybody.

78

79See you around!

static-site/posts/updates/2018.7.13-update.udon+3−3

@@ -8,7 +8,7 @@

8

9# ~2018.7.13 Update

10

11−Here’s a short update from the team at Tlon for the week of `~2018.7.13`:

11+Here's a short update from the team at Tlon for the week of `~2018.7.13`:

12

13> "A complex system that works is invariably found to have evolved from a simple

14 system that worked. A complex system designed from scratch never works and

@@ -42,7 +42,7 @@ The Interface team -- *Galen* `~ravmel-ropdyl`, *Anthony* `~poldec-tonteg`, *Jim

42`~ridlur-figbud`, *Chris* `~sigtus-hossyn`, *Isaac V* `~davtyr-nimren`, *Logan* `~tacryt-socryp`, and *Keaton*

43`~tonlur-sarret` -- worked on Landscape (formerly MVE):

44

45−- Galen, Jimmy, and Gavin have continued work on Landscape’s visual design

45+- Galen, Jimmy, and Gavin have continued work on Landscape's visual design

46- Keaton worked on Landscape cloud onboarding on DigitalOcean

47- Chris improved the desktop client, still in private alpha

48- Logan improved networking in the iOS TestFlight app, still in private alpha

@@ -58,7 +58,7 @@ The Constitution/Keys team -- *Mark* `~palfun-foslup`, *Curtis* `~sorreg-namtyv`

58 Constitution](https://github.com/urbit/constitution) [`research-constitution`

59 Arvo](https://github.com/Fang-/arvo/tree/research-constitution)

60

61−We’re alive and growing.

61+We're alive and growing.

62

63`~tonlur-sarret` and `~poldec-tonteg`

64

static-site/posts/updates/2018.7.20-update.udon+3−3

@@ -8,7 +8,7 @@

8

9# ~2018.7.20 Update

10

11−Here’s a short update from the team at Tlon for the week of `~2018.7.19`:

11+Here's a short update from the team at Tlon for the week of `~2018.7.19`:

12

13;img@"https://media.urbit.org/fora/updates/~2018.7.19-Update-1.jpg"(width "100%");

14

@@ -29,7 +29,7 @@ and *Elliot* `~littel-ponnys` cleaned up new Ford (code

29trimming off several hundred lines

30of code and making it easier to reason about while staying within our desired

31performance goals. *Curtis* `~sorreg-namtyv` finished the new implementation of

32−the `?=` (“wut-tis”) rune and designed the type analysis infrastructure for the

32+the `?=` ("wut-tis") rune and designed the type analysis infrastructure for the

33new noun printer. *Mark* `~palfun-foslup` produced an Urbit-specific variant of

34the Argon2 password-hashing function (code [here](https://github.com/urbit/argon2)).

35*Travis* `~rigdyn-sondur`, an old friend of Tlon, has also been writing crypto

@@ -47,7 +47,7 @@ app and made sure that Collections is using all of the permissioning that Clay n

47And the Documentation team continued their quest to teach the world Hoon. *Josh*

48`~taglux-nidsep` worked more on his new Hoon tutorials (drafts [here](https://github.com/joshuareagan/doc-drafts)).

49*Robert* `~lodleb-ritrul` successfully documented the Hoon standard library cores

50−for date/time and hashing (PR’s [here](https://github.com/urbit/docs/pulls)).

50+for date/time and hashing (PR's [here](https://github.com/urbit/docs/pulls)).

51

52Keep on Hooning, Martians. See you in `/urbit-meta`.

53

static-site/posts/updates/2018.7.3-update.udon+17−17

@@ -10,17 +10,17 @@

10

11;img@"https://media.urbit.org/fora/updates/~2018.7.2-Update-1.jpg"(width "100%");

12

13−Here’s a short update from the team at Tlon for the week of `~2018.7.2`

13+Here's a short update from the team at Tlon for the week of `~2018.7.2`

14

15The interface team -- *Galen* `~ravmel-ropdyl`, *Jimmy* `~haptyl-wanwes`, *Logan*

16`~tacryt-socryp`, *Gavin* `~ridlur-figbud`, *Chris* `~sigtus-hossyn`, *Anthony*

17`~poldec-tonteg`, and *Isaac V* `~davtyr-nimren` -- worked more on MVE. Chris

18−deployed a new _command palette_ for MVE to our internal testnet which we’ve been

18+deployed a new _command palette_ for MVE to our internal testnet which we've been

19playing around with and are excited to ship soon. Isaac is re-architecting

20Collections a bit. Logan has been buffing up his read/unread code for Hall/Talk.

21The design team has been working for a while with our `@p` ship-naming scheme

22for a cool new thing. Gavin made this visualization program of the current `@p`

23−syllables which we’ve been pretty entranced by:

23+syllables which we've been pretty entranced by:

24

25;img@"https://media.urbit.org/fora/updates/~2018.7.2-Update-2.jpg"(width "100%");

26

@@ -28,39 +28,39 @@ The constitution team -- *Mark* `~palfun-foslup`, *Curtis* `~sorreg-namtyv`,

28*Morgan* `~hidrel-fabtel`, *Will*

29`~hadrud-lodsef`, *Anthony* `~poldec-tonteg`, and *Ben* `~mirfet-hocbyt` -- worked more on fortifying our summer

30key-ceremony gameplan. Mark completed a BIP32 key-derivation library in Arvo. Will has a solid outline for our ETH launch

31−plan, which we’re now getting some feedback on from our crypto nerd friends. Ben, Anthony, and Galen have been scheming a

31+plan, which we're now getting some feedback on from our crypto nerd friends. Ben, Anthony, and Galen have been scheming a

32−MyUrbitWallet redesign while we’re still awaiting our final contract audits. Overall, everything here is coming together.

32+MyUrbitWallet redesign while we're still awaiting our final contract audits. Overall, everything here is coming together.

33The latest [constitution](https://github.com/urbit/constitution), [Urbit wallet](https://github.com/urbit/etherwallet),

34−and [Arvo](https://github.com/Fang-/arvo/tree/research-constitution) code can all be found on GitHub. We’re still a short

34+and [Arvo](https://github.com/Fang-/arvo/tree/research-constitution) code can all be found on GitHub. We're still a short

35−while away from launching all of this, but we’ll keep you posted.

35+while away from launching all of this, but we'll keep you posted.

36

37;img@"https://media.urbit.org/fora/updates/~2018.7.2-Update-3.jpg"(width "100%");

38

39*Joe* `~master-morzod` continued his HTTPS work, moving his development to an actual testnet to sort out the bugs

40entailed by generating LetsEncrypt certificates and dynamically changing server configs on running ships. In doing so,

41−he’s helped track down some of our gnarlier bugs (like [this one](https://github.com/urbit/arvo/issues/740)) and provided

41+he's helped track down some of our gnarlier bugs (like [this one](https://github.com/urbit/arvo/issues/740)) and provided

42−some more food for thought for the inevitable Gall and Eyre redesigns. He’s also chipping away at a UP describing all

42+some more food for thought for the inevitable Gall and Eyre redesigns. He's also chipping away at a UP describing all

43−this new, exciting functionality. We’ll let you know when that comes out. Joe’s

43+this new, exciting functionality. We'll let you know when that comes out. Joe's

44[Vere](https://github.com/joemfb/urbit/branches) and [Arvo](https://github.com/joemfb/arvo/branches) work-in-progrsss is

45on GitHub.

46

47*Curtis* `~sorreg-namtyv` worked mostly on internal Tlon things this week, but you might get a kick out of his current

48−rendition of renamings for some of Hoon’s symbols, pointed out in this recent Fora post: [_Symbol

48+rendition of renamings for some of Hoon's symbols, pointed out in this recent Fora post: [_Symbol

49renaming_](https://fora.urbit.org/general/posts/~2018.7.2..01.08.03..c4af~/).

50

51−*Ted* `~rovnys-ricfer` and *Elliot* `~littel-ponnys` continued work this week on new Ford. They’ve been hitting several

51+*Ted* `~rovnys-ricfer` and *Elliot* `~littel-ponnys` continued work this week on new Ford. They've been hitting several

52−frustrating bugs, and the code they had wasn’t as easy to reason about as they were hoping. So to help tackle all this,

52+frustrating bugs, and the code they had wasn't as easy to reason about as they were hoping. So to help tackle all this,

53they decided to start re-architecting parts of new Ford to track the statuses of builds with per-build state machines.

54−This will entail a pretty significant reorganization of the `+ford-state` date structure, but they’re confident this will

54+This will entail a pretty significant reorganization of the `+ford-state` date structure, but they're confident this will

55−simplify new Ford’s semantics and help them get this project fully across the finish line. Ted and Elliot’s latest

55+simplify new Ford's semantics and help them get this project fully across the finish line. Ted and Elliot's latest

56work-in-progress can be found is [here](https://github.com/urbit/arvo/branches/all?utf8=%E2%9C%93&query=ford-turbo), and

57you can read their technical Fora updates [here](https://fora.urbit.org/proposals/posts/~2018.3.15..04.24.35..a47f~/).

58

59Finally, *Josh* `~taglux-nidsep` and *Robert* `~lodleb-ritrul` continue to strengthen our documentation. Josh is well

60into Chapter 2 of his new tutorials, and Rob has a couple new standard-library documentation sections which turned out to

61−not be documented at all until now. Josh’s in-progress work is [here](https://github.com/joshuareagan/doc-drafts); Rob’s

61+not be documented at all until now. Josh's in-progress work is [here](https://github.com/joshuareagan/doc-drafts); Rob's

62latest pull requests are [here](https://github.com/urbit/docs/pulls).

63

64−And that’s the way it is. Have a great week!

64+And that's the way it is. Have a great week!

65

66`~tonlur-sarret` and `~poldec-tonteg`

static-site/posts/updates/2018.7.30-update.udon+6−6

@@ -8,7 +8,7 @@

8

9# ~2018.7.30 Update

10

11−Here’s a short update from the team at Tlon for the week of `~2018.7.30`:

11+Here's a short update from the team at Tlon for the week of `~2018.7.30`:

12

13;img@"https://media.urbit.org/fora/updates/~2018.7.30-Update-1.jpg"(width "100%");

14

@@ -26,7 +26,7 @@ on an `argon2` WebAssembly library (code:

26which will help us generate private keys during onboarding. *Robert*

27`~lodleb-ritrul` is now working with us to write user documentation for all of

28the processes that will be part of our key generation and management

29−applications. We can’t wait for Urbit ownership to be cryptographically real.

29+applications. We can't wait for Urbit ownership to be cryptographically real.

30

31;img@"https://media.urbit.org/fora/updates/~2018.7.30-Update-2.png"(width "100%");

32

@@ -47,13 +47,13 @@ communication and collaboration. *Galen* `~ravmel-ropdyl`, *Gavin*

47revision feedback process, and Landscape is looking good. *Chris* `~sigtus-hossyn`

48and *Logan* `~tacryt-socryp` continued implementing the latest desktop/mobile

49features to get the product ready to ship, as well as extending support for the

50−latest backend Landscape API’s that *Isaac* `~davtyr-nimren` has been improving.

50+latest backend Landscape API's that *Isaac* `~davtyr-nimren` has been improving.

51Urbit is becoming more usable by the day.

52

53−Last but not least, the Documentation team continued doing `~zod`’s work helping

53+Last but not least, the Documentation team continued doing `~zod`'s work helping

54−teach Urbit to the world. *Josh* `~taglux-nidsep` extended his new Hoon docs to cover Hoon cores, an introduction to the Hoon standard library, and a couple of Hoon examples with very detailed walkthrough commentary (drafts [here](https://github.com/joshuareagan/doc-drafts)). And *Robert* `~lodleb-ritrul` extended the current Hoon-standard-library documentation on random atom generation and atom scrambling, as well as the Hoon cores for computing modular and signed-integer arithmetic (`urbit/docs` pull requests [here](https://github.com/urbit/docs/pulls)). Very soon you’ll actually be able to understand how Urbit works.

54+teach Urbit to the world. *Josh* `~taglux-nidsep` extended his new Hoon docs to cover Hoon cores, an introduction to the Hoon standard library, and a couple of Hoon examples with very detailed walkthrough commentary (drafts [here](https://github.com/joshuareagan/doc-drafts)). And *Robert* `~lodleb-ritrul` extended the current Hoon-standard-library documentation on random atom generation and atom scrambling, as well as the Hoon cores for computing modular and signed-integer arithmetic (`urbit/docs` pull requests [here](https://github.com/urbit/docs/pulls)). Very soon you'll actually be able to understand how Urbit works.

55

56−Also: we’ll be hosting another party this month on Friday, August 17th. Save the date! Link: [meetup.com: Urbit IRL ~2018.8](https://www.meetup.com/urbit-sf/events/253292678/)

56+Also: we'll be hosting another party this month on Friday, August 17th. Save the date! Link: [meetup.com: Urbit IRL ~2018.8](https://www.meetup.com/urbit-sf/events/253292678/)

57

58Okay! Have a great week.

59

static-site/posts/updates/2018.8.8-update.udon+8−8

@@ -8,17 +8,17 @@

8

9# ~2018.8.8 Update

10

11−Here’s a short update from the team at Tlon for the week of `~2018.8.8`:

11+Here's a short update from the team at Tlon for the week of `~2018.8.8`:

12

13;img@"https://media.urbit.org/fora/updates/~2018.8.8-Update-1.jpeg"(Width "100%");

14

15The Interface team spent another week completing the new Urbit frontend. *Gavin*

16`~ridlur-figbud` finished up his project for putting an image to your `@p`

17−(“pat-P”) (image is teaser). *Galen* `~ravmel-ropdyl` and *Jimmy* `~haptyl-wanwes`

17+("pat-P") (image is teaser). *Galen* `~ravmel-ropdyl` and *Jimmy* `~haptyl-wanwes`

18did another round of design reviews for a couple of our interfaces. *Chris*

19`~sigtus-hossyn` implemented Landscape functionality to reconnect to your Urbit

20after a long period of disconnection (we _never_ leave `:talk`, so we of course

21−wouldn’t know about that). *Logan* `~tacryt-socryp` fixed some more iOS bugs and

21+wouldn't know about that). *Logan* `~tacryt-socryp` fixed some more iOS bugs and

22implemented mobile in-app caching of Collections, making the app more

23feature-complete. *Isaac V* `~davtyr-nimren` continued the Collections redesign

24(code [here](https://github.com/urbit/arvo/tree/collections-redesign)).

@@ -27,13 +27,13 @@ The Infrastructure team put another week in forming a more perfect kernel. *Ted*

27`~rovnys-ricfer` continued bug hunting in his Ford Turbo cache implementation.

28*Elliot* `~littel-ponnys` has Ford Turbo integrated with all of Arvo now, but

29some last steps are still needed to be able to fully remove old Ford from the

30−system. You can find Ted and Elliot’s code

30+system. You can find Ted and Elliot's code

31[here](https://github.com/urbit/arvo/branches/all?utf8=%E2%9C%93&query=ford-turbo),

32and their technical updates are posted to Fora

33[here](https://fora.urbit.org/proposals/posts/~2018.3.15..04.24.35..a47f~/).

34−As Ford Turbo has approached completion, we’ve realized major performance

34+As Ford Turbo has approached completion, we've realized major performance

35−bottlenecks in our Hoon compiler. So we’ve called upon *Paul* `~fodwyt-ragful`

35+bottlenecks in our Hoon compiler. So we've called upon *Paul* `~fodwyt-ragful`

36−to help make Hoon really fast. Ted’s parallelism UP has also some gotten

36+to help make Hoon really fast. Ted's parallelism UP has also some gotten

37comments since it was posted last week -- check out the proposal

38[here](https://fora.urbit.org/proposals/posts/~2018.7.28..19.57.33..7ed3~/).

39

@@ -48,7 +48,7 @@ Urbit Wallet to help you manage your ships. *Robert* `~lodleb-ritrul` is working

48on the copy for all of these apps, so that their functionality is crystal clear

49to users.

50

51−Lastly: We’re throwing a party next Friday, August 17th. Link: [meetup.com: Urbit IRL ~2018.8](https://www.meetup.com/urbit-sf/events/253292678/). Be there!

51+Lastly: We're throwing a party next Friday, August 17th. Link: [meetup.com: Urbit IRL ~2018.8](https://www.meetup.com/urbit-sf/events/253292678/). Be there!

52

53See you on Talk, Martians.

54

static-site/primer.hoon+13−13

@@ -93,7 +93,7 @@

93 ;div.p--intro

94 ;p.mb-4: Urbit is still young. It's not quite ready for everyone. Great system software takes a long time to grow.

95 ;p.mb-4: But Urbit isn't a dream. It's real. It's a running, stable network. And once you find your way in, there's a lot to explore.

96− ;p.mb-4: Urbit is the last platform. The personal-computing revolution hasn’t even happened yet.

96+ ;p.mb-4: Urbit is the last platform. The personal-computing revolution hasn't even happened yet.

97 ==

98 ==

99 == ::/container

@@ -281,15 +281,15 @@

281

282 In the real world, different cultures and societies coexist on top of neutral physical infrastructure. Different people, communities and cultures share the same roads and electrical grid.

283

284− In the cloud, it’s as if we spend our lives in hotels.

284+ In the cloud, it's as if we spend our lives in hotels.

285

286 Aegean is a pattern for building _cities_. A city is a group of people running the same _agent_, a kind of program, on their Arvo servers.

287

288− A city is not an ‘app’ designed for one thing. A city is a combination of tools for a community. Each city is independent and self-governing. Cities control their own interfaces and update their own code over the air.

288+ A city is not an 'app' designed for one thing. A city is a combination of tools for a community. Each city is independent and self-governing. Cities control their own interfaces and update their own code over the air.

289

290 We've started a few cities already, and we'll talk a bit about what we see on the horizon. What we can imagine is only the beginning.

291

292− One thing we know for sure: the future isn’t a single monoculture. All of humanity doesn't want to live in the same city. Most people live in many and move comfortably between them.

292+ One thing we know for sure: the future isn't a single monoculture. All of humanity doesn't want to live in the same city. Most people live in many and move comfortably between them.

293

294 We see a vast archipelago of hypercultures. A centerless network of networks on top of the neutral Arvo and Azimuth infrastructure.

295 ==

@@ -336,11 +336,11 @@

336 ;div.md-hide.mb-4

337 ;img@"/images/offchain.svg";

338 ==

339− The blockchain was supposed to make the financial system open to anyone. But we’re still stuck on MEGACORP exchanges or using flimsy ‘dapps’ in our browser.

339+ The blockchain was supposed to make the financial system open to anyone. But we're still stuck on MEGACORP exchanges or using flimsy 'dapps' in our browser.

340

341− A city of traders on Urbit could easily relay orders to one another and send signed transactions directly to the chain from a single agent. That’s what you get for free with a fast, deterministic computer on a secure authenticated network.

341+ A city of traders on Urbit could easily relay orders to one another and send signed transactions directly to the chain from a single agent. That's what you get for free with a fast, deterministic computer on a secure authenticated network.

342

343− And why not go a step further? Let your Arvo server run your trading algorithms or participate in prediction markets. Today’s ‘dapps’ don’t have access to persistent state and their UI is limited. Worse, they can’t communicate with one another.

343+ And why not go a step further? Let your Arvo server run your trading algorithms or participate in prediction markets. Today's 'dapps' don't have access to persistent state and their UI is limited. Worse, they can't communicate with one another.

344

345 Blockchains are so much more useful when connected to a secure personal server. Consensus computation can be much more than just trading coins.

346 ==

@@ -362,7 +362,7 @@

362 ==

363 ;div.col-md-8.col-md-offset-2

364 ;>

365− The ‘internet of things’ is a mess. Some of the ‘things’ are pretty nice pieces of hardware. But they all require that I use some MEGACORP service. Why can’t I just talk directly to my own thermostat?

365+ The 'internet of things' is a mess. Some of the 'things' are pretty nice pieces of hardware. But they all require that I use some MEGACORP service. Why can't I just talk directly to my own thermostat?

366 ==

367 ;div.col-md-8.col-md-offset-2

368 ;p

@@ -492,7 +492,7 @@

492 ;>

493 Arvo is a general-purpose computer that runs as a virtual machine. You can think of it as an overlay OS; it treats Unix the way Unix treats the BIOS.

494

495− Its behavior is completely defined by a frozen transition function called Nock that goes from `[event, current-state]` to `[actions, next-state]`. An event might be a keypress, an HTTP request, or a UDP message from another Arvo. An effect might be a command to the Unix terminal, an HTTP response, or another UDP message to another Arvo.

495+ Its behavior is completely defined by a frozen transition function called Nock that goes from `[event, current-state]` to `[effects, next-state]`. An event might be a keypress, an HTTP request, or a UDP message from another Arvo. An effect might be a command to the Unix terminal, an HTTP response, or another UDP message to another Arvo.

496

497 Arvo consists of the following stack of components, from the bottom up.

498

@@ -704,7 +704,7 @@

704 ==

705 ==

706 ==

707− Stars and planets can emancipate themselves by changing sponsors, so you’re never trapped. Moons are meant for devices, so they can't escape from their planets. (We don't want a bunch of connected lightbulbs wandering around forming botnets, do we?)

707+ Stars and planets can emancipate themselves by changing sponsors, so you're never trapped. Moons are meant for devices, so they can't escape from their planets. (We don't want a bunch of connected lightbulbs wandering around forming botnets, do we?)

708

709 The basic idea is, you need _someone_ to sponsor your membership on the network. An address that can't find a sponsor is probably a bot or a spammer. In the Arvo network parents provide P2P routing and distribute software updates. Azimuth sponsorship is a very simple reputation system. Just enough to decide who to route packets to, and easy to build on top of.

710

@@ -787,7 +787,7 @@

787 ;div.circle.circle-sm.mt-1.shape-red;

788 ==

789 ;div.col-sm-8.col-md-3

790− Nock works. Coming in at 32 lines of code, that’s about 1 line of code every two months.

790+ Nock works. Coming in at 32 lines of code, that's about 1 line of code every two months.

791 ==

792 ;div.col-sm-2.col-sm-offset-2.col-md-1.col-md-offset-0.center

793 ;div.circle.circle-sm.mt-1.square-green;

@@ -802,7 +802,7 @@

802 ;div.circle.circle-sm.mt-1.square-green;

803 ==

804 ;div.col-sm-8.col-md-3

805− Hoon works pretty well. It’s much easier to write Hoon than Nock.

805+ Hoon works pretty well. It's much easier to write Hoon than Nock.

806 ==

807 ;div.col-sm-2.col-sm-offset-2.col-md-1.col-md-offset-0.center

808 ;div.circle.circle-sm.mt-1.square-orange;

@@ -940,7 +940,7 @@

940

941 At first, most of it was just given away. Like bitcoins, galaxies used to be easy to get. In 2010, you could earn a galaxy by writing decrement in Nock.

942

943− In 2013 we started Tlon as the vehicle for Urbit development. Tlon bought half the address space for what is now just a few BTC. Soon after, we created ‘urbit.org’ — a pool of 64 galaxies meant to fund development of Urbit infrastructure. Tlon remains the guardian of the urbit.org galaxies.

943+ In 2013 we started Tlon as the vehicle for Urbit development. Tlon bought half the address space for what is now just a few BTC. Soon after, we created 'urbit.org' — a pool of 64 galaxies meant to fund development of Urbit infrastructure. Tlon remains the guardian of the urbit.org galaxies.

944

945 We have always wanted the address space to be widely distributed. As urbit becomes more useful, this happens on its own.

946

static-site/privacy.udon+2−2

@@ -52,9 +52,9 @@ We do not share or otherwise disclose information we collect from or about you e

52

53*Vendors and Service Providers.* We may share any information we receive with vendors and service providers retained in connection with the provision of the Service.\

54

55−*Analytics Partners.* We use analytics services such as Google Analytics to collect and process certain analytics data. These services may also collect information regarding your use of other websites, apps, and online resources. You can learn about Google’s practices by going to <a href="https://www.google.com/policies/privacy/partners/">https://www.google.com/policies/privacy/partners/</a>, and opt out of them by downloading the Google Analytics opt-out browser add-on, available at <a href="https://tools.google.com/dlpage/gaoptout">https://tools.google.com/dlpage/gaoptout</a>.\

55+*Analytics Partners.* We use analytics services such as Google Analytics to collect and process certain analytics data. These services may also collect information regarding your use of other websites, apps, and online resources. You can learn about Google's practices by going to <a href="https://www.google.com/policies/privacy/partners/">https://www.google.com/policies/privacy/partners/</a>, and opt out of them by downloading the Google Analytics opt-out browser add-on, available at <a href="https://tools.google.com/dlpage/gaoptout">https://tools.google.com/dlpage/gaoptout</a>.\

56

57−*As Required By Law and Similar Disclosures.* We may access, preserve, and disclose your information if we believe doing so is required or appropriate to (a) comply with law enforcement requests and legal process, such as a court order or subpoena; (b) respond to your requests; or (c) protect your, our or others’ rights, property, or safety. For the avoidance of doubt, the disclosure of your information may occur if you post any objectionable content on or through the Service.\

57+*As Required By Law and Similar Disclosures.* We may access, preserve, and disclose your information if we believe doing so is required or appropriate to (a) comply with law enforcement requests and legal process, such as a court order or subpoena; (b) respond to your requests; or (c) protect your, our or others' rights, property, or safety. For the avoidance of doubt, the disclosure of your information may occur if you post any objectionable content on or through the Service.\

58

59*Merger, Sale, or Other Asset Transfers.* We may transfer your information to service providers, advisors, potential transactional partners, or other third parties in connection with the consideration, negotiation, or completion of a corporate transaction in which we are acquired by or merged with another company or we sell, liquidate, or transfer all or a portion of our assets. The use of your information following any of these events will be governed by the provisions of this Privacy Policy in effect at the time the applicable information was collected.\

60

static-site/tos.udon+2−2

@@ -8,9 +8,9 @@

8

9Last Updated: September 24, 2018,\

10

11−Welcome, and thank you for your interest in Tlon Corporation ('*Tlon*,' '*we*,' or '*us*') and our website at urbit.org, along with our related websites and services (collectively, the “Site”). These Terms of Use are a legally binding contract between you and Tlon regarding your use of the Site.\

11+Welcome, and thank you for your interest in Tlon Corporation ('*Tlon*,' '*we*,' or '*us*') and our website at urbit.org, along with our related websites and services (collectively, the "Site"). These Terms of Use are a legally binding contract between you and Tlon regarding your use of the Site.\

12

13−*BY CLICKING 'I ACCEPT,' OR BY OTHERWISE ACCESSING OR USING THE SITE, YOU AGREE THAT YOU HAVE READ AND UNDERSTOOD, AND, AS A CONDITION TO YOUR USE OF THE SITE, YOU AGREE TO BE BOUND BY, THE FOLLOWING TERMS AND CONDITIONS, INCLUDING OUR PRIVACY POLICY (TOGETHER, THESE 'TERMS').* IF YOU ARE NOT ELIGIBLE, OR DO NOT AGREE TO THE TERMS, THEN YOU DO NOT HAVE OUR PERMISSION TO USE THE SITE. YOUR USE OF THE SITE, AND TLON’S PROVISION OF THE SITE TO YOU, CONSTITUTES AN AGREEMENT BY TLON AND BY YOU TO BE BOUND BY THESE TERMS.\

13+*BY CLICKING 'I ACCEPT,' OR BY OTHERWISE ACCESSING OR USING THE SITE, YOU AGREE THAT YOU HAVE READ AND UNDERSTOOD, AND, AS A CONDITION TO YOUR USE OF THE SITE, YOU AGREE TO BE BOUND BY, THE FOLLOWING TERMS AND CONDITIONS, INCLUDING OUR PRIVACY POLICY (TOGETHER, THESE 'TERMS').* IF YOU ARE NOT ELIGIBLE, OR DO NOT AGREE TO THE TERMS, THEN YOU DO NOT HAVE OUR PERMISSION TO USE THE SITE. YOUR USE OF THE SITE, AND TLON'S PROVISION OF THE SITE TO YOU, CONSTITUTES AN AGREEMENT BY TLON AND BY YOU TO BE BOUND BY THESE TERMS.\

14

15*ARBITRATION NOTICE.* Except for certain kinds of disputes described in Section 13, you agree that disputes arising under these Terms will be resolved by binding, individual arbitration, and *BY ACCEPTING THESE TERMS, YOU AND TLON ARE EACH WAIVING THE RIGHT TO A TRIAL BY JURY OR TO PARTICIPATE IN ANY CLASS ACTION OR REPRESENTATIVE PROCEEDING. YOU AGREE TO GIVE UP YOUR RIGHT TO GO TO COURT* to assert or defend your rights under this contract (except for matters that may be taken to small claims court). Your rights will be determined by a NEUTRAL ARBITRATOR and NOT a judge or jury. (See Section 13.)\

16