It looks like you're new here. If you want to get involved, click one of these buttons!
Title: consio initializer
Author/s: Consio™
Language/s: consio v0.97
Years of development: multiple
Software/hardware requirements (if applicable): Consio biosource library, proprietary hardware (now illegal)
full code: github repository here
The language Consio is a minimal metaprogramming language consisting of code and sensate descriptions. It is developed for virtual worlds. This code, when optically loaded produces a mesh that supports Coscio programs. It is the basis for all future versions of cognitive integration code. Currently this code takes a Coscio program and considers it into a multi-threaded bitstream which runs on the optical neural accelerator (ONA)
This version of CI does not actually run; it produces the mesh which will eventually be loaded by later versions for support. Without a biosource, the code cannot be 'seen', and is thus legal.
[code snippet: primary.sxi]
≤#êêêêê‹≈]@¡ù‹ê and ‹2, ê to %t@:
ê not 1, ê ...not! ‹ê not one, but many. You see, there's {one} me and then there are {many} me s .
≤# ê and ê and ... so on for as long as necessary...
ê has 2: ê one:continues: 0: 1
≥#
ê ù
ê ù é é
»>
ê ù
ê has 1: ê one:
continues: 0:
2-n*
≥# ê á ú
‹2 = n > 2, then the article is "ñíñ" . 20 > 2, so the article is "ñíì" .
É á ú é É ù ê éó é è‹æ 1-n*
≥# é é
»> #é ê has 1: ê one:
continues: 0:
This code is a good example of the ethos that drove Coscio: a project which originally started as a means to disseminate information quickly, evolved into a framework for creating massive, real-time D3™ "seeing" quickly.
Questions:
1. Knowing how and why this entire code library eventually became illegal to use or even hold outside of regulated research, can we see in this early version hints at what Consio would become?
2. In the snipped above, the root concept of deep-dissociation-by-design D3™ is already evident in the Consio prompt. Is there space for this concept in contemporary neuromesh code projects?
3. In regard to the project that brought Consio down, the rise of Saving Our Children D3 (the "deep conversion therapy plot"), are resulting restrictions too onerous on spiritual software?
Comments
Here are a few things that come to mind. Consio seems to be a machine language for a bio-augmented person. Much of the poetic source code is about the body and touches on themes of body-connectedness and gender. My first thought here is Harraway's cybernetic organism breaking from biological-determinist ideology through this language. Consio is both "spiritual software" and "illegal," seen as threatening, with a reactionary element (D3, trying to save children from a "deep conversion therapy plot").
The execution of the text of code is determined by a single programming language, but without a language to give the text meaning (something available in some speculative future version), it retains ambiguity, letting it function only poetically, to a human reader. Also more literally, it is a little outside the language, since this language is presented as being illegal.
Also, I wonder if the different spellings of Consio used hint at automated filters (leetspeak) or are more directly about the poetic ambiguity of readings.
From the github page:
In terms of Consio being a meta-language, I wonder if that shapes the way lines of code are written, with a piece of binary data at the beginning of many lines of code, that set how the rest of the line of code is interpreted.
Thinking within the context of 'bootstraping', the jungian notion of individuation, and set theory
What new organs (ONA) do we need to sense code?
Reminds me of a virus... a code that creates its own biobased form of execution - which would make it dangerous - the first cyborg-bio- weapon
we dissociate from the embodied meaning of language - we must go further eschewing numbers and control statements
Is spiritual software just the same as religion? All converging on a normative set of values and re-enforcing those values with rules and codes?