>éd Monday • 22:07 • April 17th, 2023 22:07 I wonder how close we (urbit writ large) are to being able to build urbit using urbit 22:08 like in a fully end to end manner, vcs in urbit, code editor in urbit, etc. 22:08 doesn't feel like it's too far off 22:09 imagining this through the construct of a Group, it's interesting to think of source code being accessed/browsed via a channel 22:10 or co-edited in a multi-user text editor channel, which could act as a lens (references/scrys?) into the source >galen Monday • 23:06 23:06 we thought about this a bunch in like 2017 23:07 urbithub instead of github
An item on one page might announce through the dom that it can source a particular kind of data. A consuming item on another page can find that source via dom query, retrieve the associated javascript object, and initiate further objec
Ownership - information is different than stuff
Transparency might be second to literacy
Automation is not to be feared but interpreted
Federated Wiki makes use of various visual metaphors for sharing and editing. This might be of interest to those working on building document editors over an effective version control system.
White pages are part of this research project and have been written by me, or forked from others, who might as well be us.
Yellow pages are stored locally in your browser as cookies and only you can see them. Activate 'wiki' on the nav bar below (you should see a checkmark appear), then double-click on these paragraphs to edit them. They should turn yellow.
Blue pages come from a distance, meaning they've been written and shared since the first instance of the Federated Wiki, in 2015, the Smallest Federated Wiki in 2011, and the C2 
server since 1995. Use colored flags at the top of each page show older and newer versions of content.
argument
Checking "wiki" on the nav bar below lets you see other versions of this page. This is a browser-based activity.