on master help sign in
Various fixes and improvements.
5f7419eC. Guy Yarvin
main/posts/company.md+35−22
@@ -1,10 +1,10 @@
1---
1---
2sort: 8
2sort: 8
3type: post
3type: post
4−title: Company + Team
4+title: Team
5author: Tlon
5author: Tlon
6image: http://media.urbit.org/site/blog-6.jpg
6image: http://media.urbit.org/site/blog-6.jpg
7−preview: A bit about who we are and how our company, Tlon, relates to Urbit the open-source project.
7+preview:
8layout: urbit,post
8layout: urbit,post
9navmode: navbar
9navmode: navbar
10navdpad: false
10navdpad: false
@@ -16,30 +16,43 @@ navclass: urbit
16
16
17## History
17## History
18
18
19−Curtis started working on Urbit in 2002. By 2011 he h
19+Curtis started working on Urbit in his garage in 2002. By 2008 he'd
20+finished Nock, a productivity level of approximately 1 bit per day.
21+By 2012 Hoon was essentially in its present form. By 2014, he had a
22+prototype of Arvo, and used it to raise a little seed funding so we
23+all could join him.
20
24
21−In 2002 Curtis went down to his garage with a question in mind: can
25+Urbit in early 2014 did most of the things it does today, but
22−you build a computer whose state is just a number, and whose updates
26+badly. For example, Urbit has chat and a shell now, and it had
23−are a single simple function? In 2008 Nock worked pretty well, in
27+both in 2014. But in 2014, chat was built into the network
24−2012 Hoon compiled itself to Nock and in 2014 we raised a little
28+module and the shell was a kernel module. Operating systems are
25−funding with the first prototype of Arvo.
29+hard (but fun).
26
30
27## Tlon
31## Tlon
28
32
29−Urbit is completely, 100% open source, and always will be. We started
33+Urbit is open source (MIT license) and patent-free.
30−a company, Tlon, to support the development of the platform. Tlon
31−owns roughly half of the Urbit address space, and operates with a
32−simple business model: use the value of Urbit address space to
33−bootstrap the development of the Urbit platform. The name Tlon is a
34−reference to a Borges story.
35
34
36−## Team
35+Tlon (named after a Borges story) is a vehicle for using the
36+potential value of the Urbit address space to make Urbit real.
37+Tlon owns about 40% of the address space (95 galaxies).
37
38
38−We’re a small team based in San Francisco that values open,
39+Another 50 galaxies are reserved for a future nonprofit. Tlon's
39−independent thinking and spirited debate. We try to foster an
40+long-term goal is to become a boring real-estate investment
40−environment where thoughtful criticism can quickly turn into better
41+trust, and shift development control to a Mozilla-style
41−design and better code. If you think you could be a good fit [send us
42+foundation / community. This will not happen any time soon.
42−an email](urbit@urbit.org).
43+
44+## People
45+
46+Some companies are all about cultural uniformity. We couldn't
47+differ more. No two people at Tlon see the world eye-to-eye.
48+
49+Galen (CEO) is a surfer from Santa Cruz with an [architecture
50+degree](http://cooper.edu). Curtis (CTO) is a former CS grad student
51+who loves [old
52+books](https://books.google.com/books/about/The_True_History_of_the_American_Revolut.html?id=SZccAAAAMAAJ).
53+Anton is a rationalist Bolshevik and trained baritone. Philip is
54+a home-schooled Christian and baseball fan. Henry is a
55+prep-school soccer player and expert in horizontal marketing.
43
56
44**Galen Wolfe-Pauly** <br />
57**Galen Wolfe-Pauly** <br />
45Founder, CEO<br />
58Founder, CEO<br />
@@ -47,11 +60,11 @@ Recommended reading: Samuel Beckett, Christopher Alexander
47
60
48**Curtis Yarvin** <br />
61**Curtis Yarvin** <br />
49Founder, CTO<br />
62Founder, CTO<br />
50−Recommended reading: James C Scott, Ernst Junger
63+Recommended reading: James Burnham, Ernst Juenger
51
64
52**Anton Dyudin** <br />
65**Anton Dyudin** <br />
53Engineer<br />
66Engineer<br />
54−Recommended reading: Asmiov
67+Recommended reading: Isaac Asimov
55
68
56**Philip Monk** <br />
69**Philip Monk** <br />
57Engineer<br />
70Engineer<br />
main/posts/constitution.md+1−1
@@ -1,7 +1,7 @@
1---
1---
2sort: 7
2sort: 7
3type: post
3type: post
4−title: Interim Constution
4+title: Interim constitution
5author: Tlon
5author: Tlon
6image: http://media.urbit.org/site/blog-7.jpg
6image: http://media.urbit.org/site/blog-7.jpg
7preview: The governing rules for the early days of the Urbit network.
7preview: The governing rules for the early days of the Urbit network.
main/posts/magic.md+1−1
@@ -4,7 +4,7 @@ type: post
4title: Magic
4title: Magic
5author: Curtis Yarvin
5author: Curtis Yarvin
6image: http://media.urbit.org/site/blog-8.jpg
6image: http://media.urbit.org/site/blog-8.jpg
7−preview: A thought-experiment for understanding what the world with Urbit could look like.
7+preview: A thought-experiment to explain the Urbit user experience.
8layout: urbit,post
8layout: urbit,post
9navmode: navbar
9navmode: navbar
10navdpad: false
10navdpad: false
main/posts/overview.md+1−1
@@ -4,7 +4,7 @@ type: post
4title: Urbit overview
4title: Urbit overview
5author: Galen Wolfe-Pauly
5author: Galen Wolfe-Pauly
6image: http://media.urbit.org/site/blog-0.jpg
6image: http://media.urbit.org/site/blog-0.jpg
7−preview: A high-level overview of Urbit. How the pieces fit together and what we think the future will look like as Urbit grows up.
7+preview: A high-level overview of Urbit.
8layout: urbit,post
8layout: urbit,post
9navmode: navbar
9navmode: navbar
10navdpad: false
10navdpad: false
main/posts/principles.md+18−20
@@ -1,10 +1,10 @@
1---
1---
2sort: 2
2sort: 2
3type: post
3type: post
4−title: Beliefs + Principles
4+title: Beliefs and principles
5author: Galen Wolfe-Pauly + Curtis Yarvin
5author: Galen Wolfe-Pauly + Curtis Yarvin
6image: http://media.urbit.org/site/blog-2.jpg
6image: http://media.urbit.org/site/blog-2.jpg
7−preview: Where the motivation for building Urbit comes from and what guides its forward progress.
7+preview:
8layout: urbit,post
8layout: urbit,post
9navmode: navbar
9navmode: navbar
10navdpad: false
10navdpad: false
@@ -16,28 +16,26 @@ navclass: urbit
16
16
17## Beliefs
17## Beliefs
18
18
19−We believe strongly in the value of individual creativity. To
20−maximize our individual creative potential we believe that
21−general-purpose tools are an essential resource.
19+We believe that general-purpose computing is an essential tool to
20+unlock the power of individual creativity.
22
21
23−We believe that individuals shouldn’t need to pay any cost in terms of
22+We believe that ownership, privacy and control don't need to be
24−usability, accessibility or reliability in exchange for ownership, privacy or
23+sacrificed in exchange for usability, accessibility and reliability.
25−control.
26
24
27−We believe that the discussion of how our software should work needs to be inclusive and expansive. We welcome debate and criticism in our development process.
25+We believe in the power of the informed crowd to develop and maintain
26+software, through the IETF principles of sincerity and rough consensus.
27+The ability of the engineering community to govern itself through
28+republican forms is not an abstract theory; it's a proven fact.
28
29
29−We believe in free speech and we believe in individual accountability.
30+We believe in both free speech and individual accountability. We
30−We believe that a healthy network is one with diverse, well-defined
31+believe that a healthy network is one with diverse and well-defined
31−communities and clear, user-controlled, boundaries between public and
32+communities, and clear, user-controlled, boundaries between public and
32−private.
33+private space.
33
34
34−Lastly we believe that no software system can replace human trust and
35+We believe that no software system can replace human trust and
35−communication. Discourse and dialogue are an important part of communities
36+communication. Dialogue, judgment and governance are essential to
36−of all scales. Code and law can successfully reduce conflict only to a
37+communities of all scales. Code and law can reduce conflict in the
37−point, when too far reaching they become oppressive.
38+common case; they can never handle all exceptions.
38−
39−We aim to preserve the promise of general-purpose computing since its
40−positive effect on humankind is so deeply significant.
41
39
42## Principles
40## Principles
43
41
main/posts/vision.md+1−1
@@ -4,7 +4,7 @@ type: post
4title: What is Urbit for?
4title: What is Urbit for?
5author: Galen Wolfe-Pauly
5author: Galen Wolfe-Pauly
6image: http://media.urbit.org/site/blog-1.jpg
6image: http://media.urbit.org/site/blog-1.jpg
7−preview: We didn't build Urbit just because it's fun to work on. We built Urbit because we think it can unlock new potential products. Here we take a tour through some of these possibilities.
7+preview: A vision of the Urbit-powered future.
8layout: urbit,post
8layout: urbit,post
9navmode: navbar
9navmode: navbar
10navdpad: false
10navdpad: false