on master help sign in
fix typos
2dead40Morgan Sutherland
content/posts/2019-5-roadmap.md+13−13
@@ -16,21 +16,21 @@ At a very high level we have two goals for 2019: make Azimuth easier to use, and
16
16
17Next year we’ll begin to move away from some of the MEGACORP software we use in the office and replace it with our own tooling. There’s some exciting work happening in that department, but we’ll cover that in a future post.
17Next year we’ll begin to move away from some of the MEGACORP software we use in the office and replace it with our own tooling. There’s some exciting work happening in that department, but we’ll cover that in a future post.
18
18
19−For some related recent thinking on all of this, see [The 100 Year Computer](./posts/essays/the-100-year-computer/), [The Current State of Landscape](./posts/essays/the-current-state-of-landscape/) and [Azimuth as MultiPass](./posts/essays/azimuth-as-multipass/).
19+For some related recent thinking on all of this, see [The 100 Year Computer](/posts/essays/the-100-year-computer/), [The Current State of Landscape](/posts/essays/the-current-state-of-landscape/) and [Azimuth as MultiPass](/posts/essays/azimuth-as-multipass/).
20
20
21For now, let’s just look at what’s on the immediate horizon:
21For now, let’s just look at what’s on the immediate horizon:
22
22
23## Azimuth
23## Azimuth
24
24
25−At lunch the other day someone on our team said something like, ‘We built a complete and working public key infrastructure, but we haven’t told anyone about it.’
25+At lunch the other day someone on our team said something like, ‘We built a complete and working public key infrastructure, but we haven’t told anyone.’
26
26
27It’s true. Azimuth is operational, secure, and well tested. It’s a pretty cool piece of technology, and it’s out there in the world for anyone to use. It also doesn’t require that you use Arvo — Arvo happens to make use of Azimuth, but it’s a completely separate system.
27It’s true. Azimuth is operational, secure, and well tested. It’s a pretty cool piece of technology, and it’s out there in the world for anyone to use. It also doesn’t require that you use Arvo — Arvo happens to make use of Azimuth, but it’s a completely separate system.
28
28
29So, the question is, why haven’t we told the world about it?
29So, the question is, why haven’t we told the world about it?
30
30
31−I tend to think that in order for a technology to succeed, it not only has to be an important technical innovation, it also has to be easy to understand as a product. And that’s our answer: we’ve undersold Azimuth because we want it to be easier to understand by *using*, not just by reading the code. Azimuth is quite elegant as a piece of technology, but that it doesn’t matter until it has a great user experience to match.
31+I tend to think that in order for a technology to succeed, it has to not only be an important technical innovation, but also easy to understand as a product. And that’s our answer: we’ve undersold Azimuth because we want it to be easier to understand by *using*, not just by reading the code. Azimuth is quite elegant as a piece of technology, but that doesn’t matter until it has a great user experience to match.
32
32
33−That’s why, in the near term, we’re focused on building on top of Azimuth ourselves. We can’t ask others to go down roads if we haven’t already been down them ourselves.
33+That’s why, in the near term, we’re focused on building on top of Azimuth ourselves. We can’t ask others to go down roads if we haven’t already been down ourselves.
34
34
35So, here’s what we’re building first:
35So, here’s what we’re building first:
36
36
@@ -38,7 +38,7 @@ So, here’s what we’re building first:
38
38
39- A simplified onboarding flow for getting an Azimuth point that’s simple to share with friends over email, text or as a URL.
39- A simplified onboarding flow for getting an Azimuth point that’s simple to share with friends over email, text or as a URL.
40- A redesigned and improved Bridge for managing your points.
40- A redesigned and improved Bridge for managing your points.
41−- An interface that allows you to easily send money between Azimuth points – without running Arvo.
41+- An interface that allows you to easily send money between Azimuth points without running Arvo.
42
42
43### Q3 2019
43### Q3 2019
44
44
@@ -51,15 +51,15 @@ Still under consideration:
51
51
52### 2020
52### 2020
53
53
54−Azimuth is beginning to feel like [multipass](./posts/essays/azimuth-as-multipass/) (coming soon), with a variety of ways to use Azimuth points without ever booting Arvo
54+Azimuth is beginning to feel like [multipass](/posts/essays/azimuth-as-multipass/), with a variety of ways to use Azimuth points without ever booting Arvo
55
55
56## Arvo
56## Arvo
57
57
58The Arvo interface has always been held back by Arvo’s technical immaturity. This is still true to some degree. The system has not stabilized completely.
58The Arvo interface has always been held back by Arvo’s technical immaturity. This is still true to some degree. The system has not stabilized completely.
59
59
60−But! We’ve been using Landscape quite a lot lately. I use it daily, in fact — even on my phone. An encrypted (although not audited — so let’s not call it ‘secure’), authenticated chat where I own the keys and can read the source code is pretty cool, really. The interface isn’t perfect, but it’s nice. Landscape is a great preview of where we’re going: a simple, permanent, self-sovereign computer.
60+But! We’ve been using Landscape quite a lot lately. I use it daily, in fact — even [on my phone](https://itunes.apple.com/us/app/landscape-urbit/id1393148862). An encrypted (although not audited — so let’s not call it ‘secure’) authenticated chat where I own the keys and can read the source code is pretty cool, really. The interface isn’t perfect, but it’s nice. Landscape is a great preview of where we’re going: a simple, permanent, self-sovereign computer.
61
61
62−There are still rough edges, and Landscape is not nearly general purpose enough. But we have plans:
62+There are still rough edges, and Landscape is not nearly general purpose enough, but we have plans:
63
63
64### Q2 2019
64### Q2 2019
65
65
@@ -70,9 +70,9 @@ There are still rough edges, and Landscape is not nearly general purpose enough.
70### Q3 2019
70### Q3 2019
71
71
72- A significant overhaul to Gall, our application model, making it much simpler for users to write apps or ‘agents’ in Arvo.
72- A significant overhaul to Gall, our application model, making it much simpler for users to write apps or ‘agents’ in Arvo.
73−- A new version of the compiler that makes us less reliant on jets. This will eliminate a major obstacle to achieving network continuity -- i.e., the ability for ships to upgrade themselves totally over-the-air, forever.This will clear the way to continuity (a key to being totally upgradeable over the air).
73+- A new version of the compiler that makes us less reliant on jets. This will eliminate a major obstacle to achieving network continuity, or the ability for ships to upgrade themselves totally over-the-air, forever.
74−- A significant overhaul and stability update to Clay, our filesystem, making it possible for us to trust it for self hosting, search it easily, and depend on it for long-term data storage.
74+- A significant overhaul and stability update to Clay, our filesystem, making it possible for us to trust it for self-hosting, search it easily, and depend on it for long-term data storage.
75−Tooling for hosting and hopefully a beta program for hosted Arvo instances run by Tlon.
75+- Tooling for hosting and hopefully a beta program for hosted Arvo instances run by Tlon.
76
76
77### 2020
77### 2020
78
78
@@ -83,7 +83,7 @@ Tooling for hosting and hopefully a beta program for hosted Arvo instances run b
83
83
84Historically, we’ve been shy about even acknowledging we have a community at all. We’ve often felt like it was far too early to invite others in to the system.
84Historically, we’ve been shy about even acknowledging we have a community at all. We’ve often felt like it was far too early to invite others in to the system.
85
85
86−But, now that enough people clawed their way in I have been convinced that it’s time to evolve our approach. As long as we’re up front about the state of this 100 year computer -- that it’s live, but incomplete -- I think it’s a good thing to welcome people on board.So long as we’re upfront about the state of this 100-year computer (that it’s live but incomplete), it’s a good thing to welcome people on board. There are more areas for contribution that we readily admit, and there’s plenty to play with.
86+As long as we’re up front about the state of this 100 year computer – that it’s live, but incomplete – I think it’s a good thing to welcome people on board. There are many opportunities for contribution and there’s plenty to play with.
87
87
88Hoon school was the first effort in this direction. We intend to do a lot more:
88Hoon school was the first effort in this direction. We intend to do a lot more:
89
89
@@ -97,7 +97,7 @@ Scaling Hoon school up to include both a track for experts and for beginners, an
97
97
98### Q3 2019
98### Q3 2019
99
99
100−- Hoon School participants understand clearly how to contribute a Modulo agent, and invite others into it.
100+- Hoon School participants understand clearly how to build a Modulo agent, and invite others into it.
101- The road toward building an Azimuth module is well understood, paved, and clear.
101- The road toward building an Azimuth module is well understood, paved, and clear.
102- We have clear instructions and tutorials for building Azimuth modules and using Azimuth as a login or reputation primitive.
102- We have clear instructions and tutorials for building Azimuth modules and using Azimuth as a login or reputation primitive.
103
103
content/posts/azimuth-as-multipass.md+1−1
@@ -10,7 +10,7 @@ posts = ["Essays"]
10
10
11![](https://media.urbit.org/site/posts/essays/azimuth-as-multipass-1.png)
11![](https://media.urbit.org/site/posts/essays/azimuth-as-multipass-1.png)
12
12
13−Why can’t I just walk up to a door and have it open for me? Why can’t I simply arrive at a restaurant and have them know I’m there? Shouldn’t I be able to buy a ticket to a show with my Multipass, then scan it at the entrance and use it to buy drinks?
13+Why can’t I just walk up to a door and have it open for me? Why can’t I simply arrive at a restaurant and have them know I’m there? Shouldn’t I be able to buy a ticket to a show with my Multipass then scan it at the entrance and use it to buy drinks?
14
14
15Why should I have to log in with MEGACORP? Today, in most cases, it’s a different MEGACORP for every single context. It’s a MEGAMESS.
15Why should I have to log in with MEGACORP? Today, in most cases, it’s a different MEGACORP for every single context. It’s a MEGAMESS.
16
16
content/posts/the-state-of-landscape.md+5−5
@@ -32,21 +32,21 @@ Anyway, let’s show off some of the specifics, and give an update on this exper
32
32
33Landscape is pretty simple. It lets you subscribe to chats, in the spirit of IRC, and ‘collections’, which are effectively forums or blogs with comments. You can also direct message with other running ‘ships’ or Arvo nodes.
33Landscape is pretty simple. It lets you subscribe to chats, in the spirit of IRC, and ‘collections’, which are effectively forums or blogs with comments. You can also direct message with other running ‘ships’ or Arvo nodes.
34
34
35−For the most part, this happens through a web interface that you can access at `https://ship.arvo.network` or via `localhost:8080`.
35+For the most part, this happens through a web interface that you can access at `https://ship.arvo.network` or via `localhost:80`.
36
36
37−There’s also an iOS app, available in the app store, that you link to your ship the same way you log in through a browser.
37+There’s also an iOS app, [available in the app store](https://itunes.apple.com/us/app/landscape-urbit/id1393148862), that you link to your ship the same way you log in through a browser.
38
38
39## Landscape: The Bad Parts
39## Landscape: The Bad Parts
40
40
41−What’s keeping us from asking others to use this thing more aggressively? Let’s walk through them (while keeping in mind, they’re all [things we’re working on](/posts/essays/2019-5-roadmap/)):
41+What’s keeping us from asking others to use this thing more aggressively? Let’s walk through the reasons (while keeping in mind, they’re all [things we’re working on](/posts/essays/2019-5-roadmap/)):
42
42
43### 1 - Arvo has rough spots
43### 1 - Arvo has rough spots
44
44
45−They have gotten a lot better, and we’re working on them, but there are still a few things that can crash your Arvo ship. This, of course, has nothing to do with your Azimuth point. That’sIt’s completely separate and, as far as we know, secure.
45+They have gotten a lot better, but there are still a few things that can crash your Arvo ship. This, of course, has nothing to do with your Azimuth point, which is completely separate and, as far as we know, secure.
46
46
47The first (and most severe) is a bug in our event persistence that occurs very rarely. Basically, there are conditions under which you can cause events not to be properly written to disk and corrupt your event log. It’s pretty unlikely, but it’s unacceptable for a real product since it basically causes you to have to wait out the current network era.
47The first (and most severe) is a bug in our event persistence that occurs very rarely. Basically, there are conditions under which you can cause events not to be properly written to disk and corrupt your event log. It’s pretty unlikely, but it’s unacceptable for a real product since it basically causes you to have to wait out the current network era.
48
48
49−The second is that Ames (our network protocol) has occasional connectivity problems. Originally, we thought we had found this issue as being related to [a timer bug](https://github.com/urbit/arvo/pull/1072). It may be, but the networking is in the process of a major overhaul — so we’ve implemented a few bandaids to make the situation workable. `|bonk` sometimes needs to be used to reset connections between peers. It’s an ugly fix.
49+The second is that Ames (our network protocol) has occasional connectivity problems. Originally, we thought we had found this issue as being related to [a timer bug](https://github.com/urbit/arvo/pull/1072). It may be, but the networking is in the process of a major overhaul — so we’ve implemented a few bandaids to make the situation workable. `|bonk` sometimes needs to be used to reset connections between peers, and `:ethmanage` sometimes need to be used to re-synchronize with the blockchain. It’s an ugly fix, but it usually works.
50
50
51Relatedly, we have occasionally been seeing errors caused by the Arvo network being slow to register keys from the blockchain. If you’re a newly registered Azimuth point, and your keys were just put on-chain, it can take some time for that change to propagate. This can result in a confusing situation for new ships.
51Relatedly, we have occasionally been seeing errors caused by the Arvo network being slow to register keys from the blockchain. If you’re a newly registered Azimuth point, and your keys were just put on-chain, it can take some time for that change to propagate. This can result in a confusing situation for new ships.
52
52