Are We a Model or a Document

Post-war, it was pop art and conceptual practice. Or maybe it was model trains and LISP. The model train was "out there", perhaps brought to MIT by visiting artists en route to a happening. Along with LISP, the signals, lights and sensors consumed the creative visions of MIT hackers. The trains moved. They also ran. Check out older versions of this document to see where we've been.

I began using Federated Wiki to render the writing that I do as an artist analagous to the shifting contexts of art's technological reproduction. When I was asked to lay out a vision of research and development for Urbit's economic potential on a macroscale, I became interested in comparing the evolutionary perspective of early open-source pioneers to the concerns of Urbit's community of developers.

Is it possible to integrate wiki app stack into urbit's ecosystem using the principles of the open web? stack.fed.wiki

The dialectic of ideology and technology is not a number. If the goal of Urbit, and Web 3 at large, is to restore the user's agency and claim over their own data and computational environments, without having to rely on third party interference, then it follows that our valuation model must work the same way. If the value of a network is exponential, not polynomial [reed vs metcalfe], we don't have to rely on complex data, layers and parameters to reason about value. We can look closer.

Contexts, crime scenes, collaborations...


Proposals

Is it possible to integrate wiki app stack into urbit's ecosystem using the principles of the open web? stack.fed.wiki

Here we point to others who can build a Gall app for moons based on wikicentric distribution principles