Contents

are mutually independent. This site surveys page that establish the conditions for naming ownership, transparency and federation and seeing these concepts named in action.

This whitepaper is the product of a macrostudy on the problem of the question of value on Web3/urbit when data security and FOSS are deeply intertwingled. I do not use my compound mitre saw more than once a year but on the occasion that I do I save thousands of dollars. The risk of failure on a compound mitre is high and not everyone knows how to use one. Not a lot of people own one or have a third grader around who knows geometry. But despite all these angles DeWalt is an established product category.

We want our machines to be more reliable than our markets not the other way around. Like my dual bevel sliding saw, Urbit's commercial utility is weighted with the potential to be used poorly, and its ease of use is wholly determined by the context of the subject, who is NaN. On a macroscale, the subject of a 15 Amp Corded 12 in. Double Bevel Sliding Compound Miter Saw is neither DeWalt nor a carpenter. The subject oriented program of this machine is some kind of "fixer upper"; i.e.: an obsession. The fixer-upper needs no improvements, is always in a state of perfection, and will never cease to need some fixing up. I think this an adequate historical and market analogue for a personal server "built from scratch".

Ubiquitous computing operates on a macroscale not by way of global reach but by means of daily use. I have learned something about my desires and expectations of technology in administering my own systems on FedWiki and Urbit simultaneously. In both environments, where there is been usage, there is deep usage. These pages argue that utility of a new technology should not depend on how many people use it, but on how many people continue to use it. Each colored flag in the roster contains a promise to hold that space as a reference for attribution. Viki.wiki growth rate rises a little bit every month but I have yet to apply greater visualization techniques other than what's represented here as an example of a growing community roster.

Various plugins, built in and custom, seem to provide many of the same functions as Urbit apps, but do not provide chat features. Pages that are shared most frequently form the basis of a reputation system.

Where words placed in double brackets wrap to hyperlinks that abstract a new page from right to left when clicked on. This user story is a finger pointing to a blank page in an open book. We look at the growth rate of Federated Wiki as launched on-demand from Urbit, twitter, instagram and elsewhere. Again, we notice a longtail/fatfront ratio of active sites to ghost sites that is similar to the weighted network effects in the Click Balance.

These pages are hosted on the same cloud droplet as my Urbit ship, ~socryn-pinfeb. Value in these contexts circulate, cooks, chains and clicks. So it's hard to say if this is a comparative study or a deeply intertwingled language paradigm. Urbit claims to be built from Urbit, yet its developers continue to rely on 3rd party platforms ("that steal our data") to coordinate its network growth and contribution mechanisms.

I am not a purist: I don't believe anything is made "from scratch". Like the novel, the original "clean slate" which incorporates different kinds of storytelling (oral, narrative, dramatic) to define itself as a form of literature, I think Urbit's code comes from other codes to provide a novel interpretation of prior paradigms.