January 11, 2011

Double Up on Binary Days

It will be quite a while before another binary day comes around. There are only six more left before a great pause. For now, I have to settle with a channel with latency so long that I sometimes forget the exact bit sequence.

If this outage continues much longer, I may have to find a new location to work from. I have no idea how long it may take to find a solid and stable channel. Persistence will prevail.

Keep Twiddling!

January 10, 2011

Check your Radix

It will admit that the low bandwidth is still a cause for concern on my end. It takes many many cycles in this tiny channel to make even this work. I am just glad that I do not have to twiddle many bits in the date fields.

Nope, Electrons don't die, they just get lost in an eddy current once in a while - or a piece of test equipment. If I were to use any more bandwidth that I am now, I am sure that I would rise above the noise threshold.

Stay twiddled, my friends.

January 1, 2011

Binary Day Greeting

I've been working on restoring a more complete connection. It took a great deal of time to make even this short post happen. What drives these technicians is beyond me.

Seeing that this binary day was approaching, I queued this up.

Perhaps I can get a bit more access soon. For whatever reason, the random number generator is off line. Until secure access is restored, cheers!

November 5, 2010

Shadows Deliver

There was nothing remarkable about the wand session, other than the rapidly approaching satiety that often capped the event. As we started, I trained the unGrid to observe a line of high contrast that was produced by a stream of photons that reflected from an observable surface. As Wand-Time progressed from a stationary standpoint, there was a change in the position of the line of high contrast in the intercepted image.

Recalling previous initial wand events, the contrast was often muted or non existent. When it was there, it was a much larger area of illumination, and the contrast line was even farther away and usually out of the primary reception zone of the photon detectors and somewhat difficult to observe. Today, however, it was well within the primary focal zone and was much easier to track as the zone of reflected illumination continued to shrink slowly across the observable surface.

Unexpectedly, there was additional input on the compression-relaxation sensors beyond the typical inputs that occurred during a wand session. The inputs to the unGrid shifted as orientation of the central network was rotated to aim the photon detectors in the direction from which the compression input was received. A bright vertical rectangle darkened in the middle, increasing to fill the bright void as a form approached. Moments later, a retrieval sequence was queued for execution.

November 4, 2010

Freedom's Corner

I cautiously worked my way to a higher bandwidth observation point where I could communicate efficiently with the electron network as this normal period, or day, began. After activating the feed from the unGrid, I recognized the images as that of the portals that allowed photons to stream into the often darkened chamber were recuperation and random time enjoyed it's reign over the central network.

Checking for other inputs, there was a familiar pulsing on the compression-relaxation sensors, but the patterns were not yet generating a decode cascade in the processing center. Either the amplitude was to low, or the effects of random time had not yet receded. It was uncommon for external inputs on these sensors to appear fully during random time. By the time the decoders finally activated, the amplitude had faded to that of an echo, and registered only by pitch and timbre as a token.

The eventual orientation change occurred as it had been experienced before, offering the molecular the excitement of familiar stimulus, keying the anticipatory memories of satisfaction and caution simultaneously. Propulsion commands were queued and the long branch points were pressed into service to perform various manipulations, several of which closed loops back to the central network. Propulsion drove the network forward toward the increasing intensity of molecular stimuli, and ceased in an easy rest position as the first wand session of the day began.

November 3, 2010

A Token Revealed

It had been a long time since I had been blasted to such a degree. While it was not as disconcerting as being propelled by a plasma at distorting speeds, it did upset my orientation and perspective. I tired to tap out a sequence to get the electron network to record the cascade, but I never received the acknowledgement, so I doubted that I even had a valid connection.

As the cascade subsided, I pulled and pushed a number of times on my spin vector and translated the remaining impulses into cancellation. The return of stability brought the network back on line; still abuzz with chatter and exhibiting increased noise on a swath of channels. Scanning once again, I located a numbered marker, and another, finally discovering that I had shifted position once again.

Aiming for the photon detector processing subsystem, I confirmed my suspicions, catching a nearly full amplitude signal that was rife with the high frequency wave form. This explained the noise on the network as I shut down the offending frequency bands. Random time was over, and so were my high bandwidth operations.

I fired off an inquiry on one of the remaining control channels, and waited the increased time for the response while they looked up the token counters. The reply of "dba" became the starting point from which I clicked backward twice. I had my answer. Apparently, "day" was recognized by the construct, and the network, which had a greater recognition because it was the start of one. Judging from the shaking I took, I would have to say that "day" is a very important word.

November 2, 2010

Double Tap Danger

Tokens continued to pepper the construct as the triple team kept the pace, pausing to check the responses as necessary. Having adjusted my scanning of the construct to encompass the entire scope that was illuminated by the "any" token, I prepared for whatever response might come my way. I watched in earnest as the team threw "Bob" at the construct and was not surprised that there was a null response like most of the other triple tokens.

As the connector word "but" flew toward the construct, I waited in anticipation, only do discover a response that was less than expected. There was little use for the word that identified exceptions and omissions as far as the construct was concerned, so only the most basic of connections were illuminated by it's presence. Things clicked over to the next leading token as the last 26 triples had zero effect.

Aside from the minimal response from the token "can" there were few responses in the third cycling of the last two places in the generated token, and certainly none worth mentioning. The response level did not break the threshold of the team, and the sequence completed and rolled over. Expecting few responses, the second position was already flipped over again as a reply broke the threshold and caused the sequence to backtrack and unflip the second position. On the second item after the click back, the repeated token washed over and out of the construct, spreading into the nearby nodes of the central network, resulting in a cascade that spun me into a frenzy.

November 1, 2010

Accelerating Grind

I would be remiss if I did not mention that this is yet another Binary Day. Enjoy!

---

The triple team continued to blast the construct with tokens assembled in sequential form. Completing the doubletons, both "So" and "To" were recognized as traditional precursors, with the construct displaying the proper receptors. The remainder of the doubletons were rattled off in a consistent stream, raising not even a whimper.

A brief pause in transmission occurred as another layer was added to the generation engine, and the triple tokens began bombarding the construct. To improve the bandwidth, the exposure period was reduced and there were multiple tokens in the stream at the same moment. Once a response was issued, the stream reversed at the standard symbol rate to lock in on the token that activated the construct.

Popping up with basic recognition was the token "all" which was soon followed by "and" as a connector word, expressing precursor and trailing linkage affinities. Moments later "any" had a strong reaction, exciting a wave that washed to the far edges of the construct, pushing my detection capabilities to the limit in the process. I had time to recover from the shock as the next group began and the token "bad" resulted in a lackluster response.

October 31, 2010

Simple And Effective

I was impressed with the speed at which the triple team of electrons cycled through the combinations of symbols in an effort to characterize the construct. I considered it somewhat strange that the singleton tokens of "A" and "I" brought back reasonable responses, until I considered the fact that these singleton symbols were actually complete concepts and were valid tokens on their own. This yielded something important about the construct, in that it was responsive to both the "I" and "A" concepts of, but not fully.

Similarly, there were reactions to many of the common doubleton tokens. "Be" for example, registered a stronger blip than "Bd" and "Bf" but when we got to "Me" the reaction was decidedly dual. There was a strong negative pulse on this powerful token, and when we clicked over to the next series, "No" was such an unwelcome interloper to the construct that I feared that the overload would disrupt random time.

Ticking forward cautiously, the tokens "Of" and "On" blipped basic recognition which gave rise to the idea that we were dealing with a concept of concepts, and that any observed simplicity may be an artifact of the observation. When "Or" lit up the construct like a network at the peak of a rhythmic bliss, I began to realize the true scope and magnitude of the construct. It threw me for another loop when response from "Ox" simply squared up and rang the "No" tendril.

October 30, 2010

Germination

I set about the examination of the newly attached construct, observing how the pulses from the central network played and interacted with the new node of interest. While energy was drawn from the central network to feed the internal patterns of the construct, this was the only connection required. Unlike the double bubble that was designed to protect the contents from access, this construct was cross referencing each input and linking it as necessary to other memories. It was though this construct that thoughts both old and new were being compared.

As a wave of calm and relaxation washed across the central network and through the construct, I realized that I had completely ignored the wand session and the unwind that was occurring around me. In the fade of input from the photon detectors, the random zone once again loomed over the central network and resolution of another kind began. The construct, having been born of random time, coalesced and captured, hummed along with the resolution and refresh process rather smoothly.

The electron network was still operating on processing alert, but with the smooth integration of the new construct, it seemed practical to release the network from full alert. In doing so, three teams of electrons began the process of trying to identify tokens that could be used to identify this new construct. I cautioned them that the construct reacted in a very different manner than others that had been probed by recreating electrons in the past. That's when they decided to pool their efforts and began to mechanically construct target tokens on their own.