The purpose of the museum or cultural institution is not to keep you woke but to extend the boundaries of static media to what can be elaborated in history. Preserving changes in digital records introduces the problem of how to compose meta-data, but this has a complicated history when the artifacts represented are physical entities that can be physically and digitally reproduced, appropriated or even counterfeited. Institutions need the kinds of tools that will make linked data structures amenable to collaborative maintenance and source control. A Federated Wiki allows the collective editing of parallel documentation which could anticipate the future utility of Urbit, but until then the collaborative maintenance of legacy databases remains an open problem for data normalization.
After thanking the audience for the opportunity, I acknowledged Urbit’s creator in his having approved everything that was about to happen including the parts where any industrial product developer would go “no no no no no, this is really not what we’re about, you have the wrong idea, and furthermore, you lack the technical background necessary to grasp the problems under review, etc.” But he never said anything. It took me a few moments of stammering my intention to speak on multi-threaded event-processing, or whatever, for me to get fully comfortable with the fact that all I had to do was get up and put alcohol on the table.
LMAO performance with bourbon and a bag of money as a trustless system
— 𐐝𐐮𐐾𐐮𐑊𐐰𐑌𐐻𐐨 🌕 (@sigilante) October 21, 2024