cone,

a widening trail of ripples throughout Knowledge traceable, however indirectly, to a given commit (publishing a new book, fixing a typo, anything in between); the ripples may be actual or potential, intended or not: from immediate listeners (styling, categorizing, metadata) to remotest, unimaginablest, long-after bit flips many namespaces away — expanding and fading, cone-like, along the time and distance axes. The idea is that a cones tip trigger is someones conscious action while its Knowledge body is mostly automated — even if the distinction is often hazy (as in a Minds fleeting thought precipitating a deep public cone via her headcloud of direct-link feeleries).  ■    Cone braiding may well be a lifes work: testing, coordinating, twinning and twining, meaningifying actual and potential downcone trails — designing unlikeliest processing pipelines, hiding triggers for words that may never be said, notions impossible to develop (“not in our day and age”); conework — an amplified version of the old human “ideasphere” in which no thought dies traceless — perfects Knowledges echo-chamber responsiveness which, for many, is what makes it live and worth living in. Only naturally, others choose, with or without a stated reason, to wall up — fortify their inside the rock cells, block “coning in” and/or “out”; or only use the term negatively, as in “staying outside the cone” of something — unwilling “to even be aware.”

< complexity  |  consensus >

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License