@@ -21,8 +21,7 @@ worry, it's a good one.
21In [this amusing
21In [this amusing
22talk](http://www.themacro.com/articles/2016/09/chad-rigetti-on-building-quantum-computers/),
22talk](http://www.themacro.com/articles/2016/09/chad-rigetti-on-building-quantum-computers/),
23Chad Rigetti defines "hard tech" as "solving problems you don't
23Chad Rigetti defines "hard tech" as "solving problems you don't
24−even know are solvable." Rigetti (who is not only named "Chad",
24+even know are solvable." Rigetti is building a quantum
25−but looks like he should be named "Chad") is building a quantum
26computer, which is definitely "hard tech." More power to him!
25computer, which is definitely "hard tech." More power to him!
28But software can be "hard," too. Is Urbit "hard tech"?
27But software can be "hard," too. Is Urbit "hard tech"?
@@ -89,15 +88,15 @@ and the all-new `%jael` PKI, are now at code complete. (Code
89complete means "compiling but not tested," which is actually
88complete means "compiling but not tested," which is actually
90saying a lot in a typed functional language.) They've been
89saying a lot in a typed functional language.) They've been
91checked in to a new `cc-release` branch on
90checked in to a new `cc-release` branch on
92−`github.com/urbit/arvo`.
91+[`github.com/urbit/arvo`](https://github.com/urbit/arvo).
94I think these two vanes are definitely the best code in Urbit.
93I think these two vanes are definitely the best code in Urbit.
95There's still a bit of fundamental work in Arvo (implementing the
94There's still a bit of fundamental work in Arvo (implementing the
96boot sequence and event security mechanisms described in the
95boot sequence and event security mechanisms described in the
97−whitepaper), but this is not "hard tech" -- the designs are
96+whitepaper), but this is not "hard tech" -- the designs are
98clear and surprises seem unlikely.
97clear and surprises seem unlikely.
100−## %xmas: the new network
99+## `%xmas`: the new network
102New `%ames` (currently `arvo/xmas.hoon`, since old `%ames` is still in
101New `%ames` (currently `arvo/xmas.hoon`, since old `%ames` is still in
103the build) has had all the key management stripped out; it's just
102the build) has had all the key management stripped out; it's just
@@ -117,7 +116,7 @@ Don't look at new `%ames` just yet. It was done in July and
117August. It needs a few touchups to fit the `%jael` interface.
116August. It needs a few touchups to fit the `%jael` interface.
118And it needs to be brought up to `%jael`'s quality standards.
117And it needs to be brought up to `%jael`'s quality standards.
120−## %jael: reference code, PKI, and personal ledger
119+## `%jael`: reference code, PKI, and personal ledger
122`%jael` (`/arvo/jael.hoon`), the PKI, is what I'm really excited
121`%jael` (`/arvo/jael.hoon`), the PKI, is what I'm really excited
123about. It's what you should take a look at if you know any Hoon
122about. It's what you should take a look at if you know any Hoon
@@ -156,7 +155,7 @@ single-homed urbit model, where one pier is one ship. In the new
156world, to boot your planet, you use your ticket to generate a
155world, to boot your planet, you use your ticket to generate a
157symmetric key that authenticates you to your parent. When you
156symmetric key that authenticates you to your parent. When you
158share your public key with your parent, over that initial secure
157share your public key with your parent, over that initial secure
159−channel, it notices that it hasn't signed it yet and shares its
158+channel, it notices that it hasn't signed it yet and shares its
160signature back to you.
159signature back to you.
162Third, `%jael` isn't just a PKI -- it's a generalized system for
161Third, `%jael` isn't just a PKI -- it's a generalized system for
@@ -237,7 +236,7 @@ their sequence numbers -- and forget you know anything they told
237you, treating you as a new stranger.
236you, treating you as a new stranger.
239At the application level, all your subscriptions get closed.
238At the application level, all your subscriptions get closed.
240−Apps already have to deal with this. Forward messages shouldn't
239+Apps already have to deal with this. Forward messages shouldn't
241involve any state coupling; that's what subscriptions are for.
240involve any state coupling; that's what subscriptions are for.
242In case there is some coupling anyway, you'll get an event that
241In case there is some coupling anyway, you'll get an event that
243"ship X lost his mind, forget anything you know about him."
242"ship X lost his mind, forget anything you know about him."
@@ -262,7 +261,9 @@ have to hack something up to make this work.
262`:talk` is always a great place to come and ask questions.
261`:talk` is always a great place to come and ask questions.
263Someone from Tlon will be available in `:talk` from 12PM - 3PM
262Someone from Tlon will be available in `:talk` from 12PM - 3PM
264PDT each weekday. And [our forum](https://urbit.org/fora) is a
263PDT each weekday. And [our forum](https://urbit.org/fora) is a
265−great place to post questions.
264+great place to post questions. We've created [this
265+thread](https://urbit.org/fora/posts/~2016.8.30..18.05.18..8ba3~/) to
267For anything else you can always get in touch with us via
268For anything else you can always get in touch with us via
268[`urbit@urbit.org`](mailto:urbit@urbit.org).
269[`urbit@urbit.org`](mailto:urbit@urbit.org).