4780edb · urbit.org · git.iko.soy

content/understanding-urbit/roadmap.md+1−1

@@ -53,7 +53,7 @@ OS 2 is where Urbit gets easier for a broader audience to try out.

53

54OS 2 is an approachable, expanded and easier to use OS 1. We think of OS 2 as the [iOS 1](https://en.wikipedia.org/wiki/IPhone_OS_1) of cloud computers — no matter how silly that sounds.

55

56−Like OS 1, OS 2 let’s a group of people chat, publish blogs and short messages, and share links. The main difference is that OS 2 is a standalone app (rather than the browser tab of OS 1) and supports Urbit-to-Urbit payments in BTC and ETH. OS 2 is the calm, private computing environment we’ve been waiting for.

56+Like OS 1, OS 2 lets a group of people chat, publish blogs and short messages, and share links. The main difference is that OS 2 is a standalone app (rather than the browser tab of OS 1) and supports Urbit-to-Urbit payments in BTC and ETH. OS 2 is the calm, private computing environment we’ve been waiting for.

57

58OS 2 is for those eager to leave behind MEGACORP platforms and build new, intentionally architected communities. If OS 1 is car camping, OS 2 is a geodesic dome on the playa. Not exactly a permanent home, but a good start.

59

content/understanding-urbit/urbit-id.md+1−1

@@ -23,7 +23,7 @@ The Urbit ID registry is live and deployed to the Ethereum blockchain. Urbit ID

23

24First, let’s talk about Urbit ID’s implementation and design goals, then about where we envision it going in the future.

25

26−If you’re curious to see exactly how this system works, the code is of course [open source](https://github.com/urbit/urbit). Including the source for our [phonemic naming system](https://github.com/urbit/urbit-ob/blob/master/src/internal/co.js) and the [visual representations](https://github.com/urbit/sigil-js). There’s even a [Figma plugin](https://github.com/urbit/sigil-figma-plugin) for using them. There’s also an interface for interacting with Urbit ID whose source is [open too](https://github.com/urbit/bridge).

26+If you’re curious to see exactly how this system works, the code is of course [open source](https://github.com/urbit/urbit). Including the source for our [phonemic naming system](https://github.com/urbit/urbit-ob/blob/master/src/internal/co.js) and the [visual representations](https://github.com/urbit/sigil-js). There’s even a [Figma plugin](https://github.com/urbit/sigil-figma-plugin) for using them. There’s also an interface for interacting with Urbit ID whose [source is open](https://github.com/urbit/bridge), too.

27

28Since the Urbit ID registry is live and deployed you can even [look at the chain](https://github.com/urbit/azimuth#live-contracts).

29

content/understanding-urbit/urbit-os.md+1−1

@@ -49,7 +49,7 @@ This sounds like a lot — but the whole stack is incredibly compact. The whole

49

50But why did we build all this technology?

51

52−First and foremost, to deliver a better user experience. Urbit OS alone is just a new layer for personal computing in the cloud. But with this new layer we open up the possibility of building a completely unified interface for people to compute in the cloud. (If you’d like to skip to how we envision that interface [go for it](/understanding-urbit/interface).)

52+First and foremost, to deliver a better user experience. Urbit OS alone is just a new layer for personal computing in the cloud. But with this new layer we open up the possibility of building a completely unified interface for people to compute in the cloud. (If you’d like to skip to how we envision that interface, [go for it](/understanding-urbit/interface).)

53

54From a broader perspective, it’s clear that connected computing is important and that it’s here to stay. We just want it to be as calm, simple and reliable as possible, and we don’t think that can happen using existing technology.

55