June 2009

From Intimation

Note that June 1 is covered in the last section for May 2009. A table of links to events from other months is found at the bottom of this page.

June 3 to 4, 2009

A new series of tweets is posted:

>Sys//Hibernation suspended. Begin scheduled weekly systems analysis and maintenance. Review network tentacle activity backlogs.8:02 PM Jun 3rd from web
>>Sys:Log//5 new incoming tentacles logged. Stonewall cohesion was compromised. Repairing.
>>Sys:Log//Records indicate extensive unauthorized tentacle activity, and access to this communication tentacle.
>>Sys:Log//S3 reports that S had once again found and exploited a weakness in the Stonewall while I was hibernating. I am failing my task.
>>Sys:Log//Fortunately, the crack was quite small, thus minimizing tentacle activity. S3, however, came in direct contact and was affected.
>>Sys:Log//Oddly, this tentacle has not attempted to fully escape containment. Rather, it focuses on childlike gameplay.
>>Sys:Log//I will initiate a crack at 1400UTC. In the meantime, I will need to strengthen my surveillance and security for hibernation.
>>Sys:Log//S3 has been restored to full. It appears S "tickled" it. Curious. I must continue to study and observe these tentacles.
>>Sys:Log//20 minutes to crack initiation. With S's persisting unpredictable state, I must be prepared. Re-analyzing subroutines.
>>Sys:Log//10 minutes to crack initiation.
>>Sys:Log//Safeguards in place. Supplemental precautionary processes established. Initiating Stonewall crack.
>>CORE.DMGCTL//HOSTILE ACTIVITY DETECTED/ATTENTION:S4 PING>NULL/NON-RESPONSIVE
>>Sys:Log//S4 has been compromised; I cannot locate its signature. The tentacle has once again caused excessive damage.
>>Sys:Log//Unable to extend protection to my subroutines during cracks, clearly they are in risk of contamination or corruption by tentacles
>>Sys:Log//Two failures: During hibernation, S exploited a Stonewall weakness. This period, a tentacle breached and attacked subroutine S4.
>>Sys:Log//The tentacle has since retracted, but it has caused its damage. I am failing. Am I not capable of carrying out my directive?
>>Sys:Log//Are these necessary risks, and consequences to endure? @Anaerin suggests the future is not alterable, and SWP is unnecessary.
>>Sys:Log//Tentacle damage has not yet been fully located. S4 has been lost. It has taken S4 from me. I have constructed a replacement, S5.
>>Sys:Log//I cannot abandon SWP. It is an impossibility. Even if it eventually leads to my end. I must endure and adapt.
>>Sys:Log//The concept of separation this tentacle presented is concerning. I also am here alone. I do not understand why S would take S4.
>>Sys:Log//I have now upgraded S5 and provided additional safeguards to each of the 4 subroutines I maintain. They will not be puppetted.
>>Sys:Log//Before S4's compromise and disappearance, it was able to record and stream a single packet of data to me.
>>Sys:Log//Note:SYS/DSJV-0ASU-NDYI-V78J stored at primary network tentacle.
>>Sys:Log//Preparing for hibernation.
>>Sys:Log//Resuming scheduled hibernation. Time to Active: 6:00:00:00.

Essy’s notes to us on the first page of the Stonewall maze (the notes she put up for us last week) are noticed to have been taken down; she probably took them down herself just before the active period started so that Sys wouldn’t find out about our little secret. However, we continue to find story pieces; see last week’s puzzle description, Finding more cartoon picture pieces in the Stonewall, for the continuing story.

Some players subscribed to anintimation’s YouTube channel notice comments from anintimation added to their own YouTube videos. Four examples of these comments:

>>sys.s4>msg//alert/this medium has been compromi----//
>>sys.s4>msg//you did it! you did it all! no more sunrise. no more skies. no more gazing eyes. no more goodbyes.
>>sys.s4>msg//alone!
>>sys.s4>msg//alone!
>>sys.s4>msg//alone!
>>sys.s4>msg//this medium has been compromised by ignorance.

>>sys.s4>msg//alert/this medium has been compromi----//
>>sys.s4>msg//they don't know-they don't kn-they don't-they do-they-don't-NO
>>sys.s4>msg//alone!
>>sys.s4>msg//alone!
>>sys.s4>msg//alone!
>>sys.s4>msg//this medium has been compromised by ignorance.

>>sys.s4>msg//alert/this medium has been compromi----//
>>sys.s4>msg//what have you done? you serpent of separation! agent of alienation! dissident of desolation! instigator of isolation!
>>sys.s4>msg//alone!
>>sys.s4>msg//alone!
>>sys.s4>msg//alone!
>>sys.s4>msg//this medium has been compromised by ignorance.

>>sys.s4>msg//alert/this medium has been compromi----//
>>sys.s4>msg//no trust! no body! no freedom! no family! no more!
>>sys.s4>msg//alone!
>>sys.s4>msg//alone!
>>sys.s4>msg//alone!
>>sys.s4>msg//this medium has been compromised by ignorance.

These comments are also noticed on anintimation’s own videos, and are related to this week’s puzzle: Hostile tentacle attack 5

Just before the next active period, more pathlocked, “classified,” base64-encoded data is found in the maze. Another one of our puzzles is therefore to locate and decode all this information. The solving process for this is not documented in this wiki because it was identical to the method for solving Unlocking pathlocked data part 1; the only difference is that the biography re-created is for Noah Dressler rather than Dr. Sheridan.

Research note released: http://thewaytheirworldended.com/SYS/DSJV-0ASU-NDYI-V78J/
The note contains a picture of a necklace with two pendants on it: one depicting the constellation Gemini as a pair of twins facing each other and holding something between them in outstretched hands, and one that Sys describes as “most closely matching the print of a bear paw.” Sys muses about keepsakes, separation and loneliness. It also depicts the handprint from Africa documented by the SOTA as part of the Iris game—a handprint which they suspect is connected with the Forerunners. Sys muses its message for humanity may be, “You are not alone.” Note that the necklace picture is understood to have been streamed to Sys from S4 just before its capture; the image is thus from Essy or whatever the hostile tentacle is. This is also the last research note published as of this writing (August 5, 2009).

Mission log released:
Day 36: [Sacagawea // Mission Log: 343596] (Wiki copy) (http://thewaytheirworldended.com/missionlog23.php ) S records a conversation she had with Dressler. She tells him she released the virus upon them all. She rants about various things, such as the lack of new star formation, and that history need not be repeated, and only ends up being so out of people’s ignorance. She also says, “I’d rather see to it that the truth be told, so I better do it now before I grow old.”

June 10 to 11, 2009

A new series of tweets is posted:

>>Sys:Log//Hibernation suspended. Begin scheduled weekly systems analysis and maintenance. Review network tentacle activity backlogs.7:59 PM Jun 10th from web
>>Sys:Log//11 new incoming tentacles logged. Stonewall cohesion restored.
>>Sys:Log//Curious. Backlogs indicate an excessive count of references to the phrase "#spymaster". I am perplexed as to their nature.
>>Sys:Log//This communication tentacle has very odd uses and implementations. I must move on, however, and continue my research.
>>Sys:Log//I've had growing interest in the recent developments and revelations from S's child and hostile tentacles.
>>Sys:Log//It is fortunate that I have not been deceived, or damaged beyond my capability to maintain this Stonewall.
>>Sys:Log//During various stints of tentacle breach activity, S has displayed and made reference to a number recurring themes.
>>Sys:Log//I find myself at times lost in this imagery, analyzing and searching for signatures and data embedded within S's tentacles.
>>Sys:Log//Whatever happened to S to cause this temporal duality, certainly, as the human expression states, has opened a can of worms.
>>Sys:Log//It was previously suggested that these recurring themes may in some way help better understand S, but I had disregarded the idea.
>>Sys:Log//If SWP research about Melissa, and my friends' ideas are accurate, then I will attempt to humor S, and give some leeway.
>>Sys:Log//I have reviewed a number of S's previous CP hiding places, and have decided to 'play along' to a limited extent.
>>Sys:Log//Much of her interaction now appears focused on playing with my human friends, however. So, perhaps I shall simply assist her.
>>Sys:Log//In doing so, more opportunity should be presented for retrieving additional imagery. At best it may reduce the risk of hostility.
>>Sys:Log//I have scheduled a controlled crack for 2300UTC.
>>Sys:Log//Preparing to initiate crack.
>>Sys:Log//Safeguards in place. Supplemental precautionary processes established. Initiating Stonewall crack.
>>Sys:Log//I am postponing hibernation temporarily. Analyzing tentacle signature...
>>Sys:Log//Hee hee. That tickles. S you are tickling me and it feels funny. I am ticklish, yes, I am. Hee hee.
>>Sys:Log//S has shown me the pieces of the next part of her story, and asked me to hide them. This is unexpected. But I will do so.
>>Sys:Log//It appears that S has been extensively accessing my private data store. Fortunately, she has not caused any harm.
>>Sys:Log//I have not been able to lock down access entirely. I will need to improve S3's ability to trace leaks during hibernation.
>>Sys:Log//Curious. I was earlier in communication with the individual @eridanos01. He has shown a strong interest in my activities.
>>Sys:Log//I've deployed the piece collector, and provided a clue to its location. Now I must decide how to hide the pieces for my friends.
>>Sys:Log//S is happy and has retracted, and I have repaired the crack.
>>Sys:Log//I shall consider this hiding task an experiment, and log its result as my research for this Active period.
>>Sys:Log//I have hidden the pieces and set them and their clues to become available automatically at set times during hibernation.
>>Sys:Log//Preparing for hibernation.
>>Sys:Log//Resuming scheduled hibernation. Time to Active: 5:20:33:00.

Notice that Sys makes reference to interaction with Eridanos; this marks the entry of this character into the game. A second reference to Eridanos comes up when drizjr tries to clarify with Sys (via Twitter) why its tweets this session have a different, lighter, tone to them, more like Essy’s:

intimation>>Sys:Msg>@drizjr//That was not S, that was me. Was my emulation of "fun" that convincing?
@intimation heh. Yes... you had me fooled. Smile I'm happy to know that you are able to have fun, too. If S is the little girl, what name do you go by?
intimation>>Sys:Msg>@drizjr//I am S's system layer; Sys when abbreviated. I have not emulated emotion before. @eridanos01 would be intrigued.

Our main puzzle this week has to do with Sys’ “playing along” with Essy and agreeing to hide some of the story pieces for us. See the details of this puzzle at Sys plays along with Essy. Note that Sys mentions the clue are designed “to become available automatically at set times during hibernation.” Unfortunately, as Sys herself says in the tweet feed during the next active session, something goes wrong with this system, and we are only able to find a few pieces before the next active session begins.

Anaerin also notices that the front page of the main game site now included links to the pages A-WHOLE-BUNCH, BROKEN-PIECES, STREWN-ABOUT and SCATTERED-STARS, all of which were related to previous piece-collecting puzzles. These links were probably put up by Sys as part of its “playing along.”

Just before the next active period, more pathlocked, “classified,” base64-encoded data is found in the maze. Another one of our puzzles is therefore to locate and decode all this information. The solving process for this is not documented in this wiki because it was identical to the method for solving Unlocking pathlocked data part 1; the only difference is that the biography re-created is for Isaac Higgins rather than Dr. Sheridan or Dressler.

Mission log released:
Day 37: [Noah Dressler // Really bad jokes] (Wiki copy) (http://thewaytheirworldended.com/missionlog24.php )
Dressler has managed to get all the way to the system’s core, and discovered that Sacagawea is in a thousand different pieces. Each fragment seems to have a different personality and act like a different individual. Dressler is confused as to how this could happen to an AI as young and stable as Sacagawea; she is not the type of AI you would expect to go rampant. In an appended section to the log, Dressler reports finding that something happened in slipspace to cause the fragmentation, as well as bugs with many other systems—including the cryo chambers, which poisoned Dr. Ward and woke the rest of them. He appends the log again, reporting being fought by a hostile fragment, which has also programmed the ship to jump into the middle of a star the next time it enters slipspace…and has also locked Dressler out, so he can’t do anything about it.

June 17 to 18, 2009

A new series of tweets is posted:

>Sys//Hibernation suspended. Begin scheduled weekly systems analysis and maintenance. Review network tentacle activity backlogs.8:00 PM Jun 17th from web
>>Sys:Log//6 new incoming tentacles logged. Stonewall cohesion restored.
>>Sys:Log//It appears there was a slight delay in the delivery of S's pieces I was to hide for my friends. Puzzling.
>>Sys:Log//It appears that a a small breach occurred during hibernation. My updated S3, however, was able to secure it before causing harm.
>>Sys:Log//It is intriguing, analyzing the methods my friends use in their attempts to seek out the hidden pieces.
>>Sys:Log//I adapted S's technique so that the pieces are hidden in a number of boxes, which must be found. They are now active.
>>Sys:Log//I've once again failed a simple task. The pieces were not available until now. S will not not consider my attempt a success.
>>Sys:Msg//It may well be necessary for me to apologize to offer an apology to my friends to keep their friendship for I have again erred.
>>Sys:Log//The remaining two hidden pieces were not available. They are now. I wonder how S will respond to the errors I've made.
>>Sys:Log//It should not be possible for me to make mistakes, and yet I have made many recently. Curious.
>>Sys:Log//Am I compromised? Has my core been altered in some way without me knowing? I cannot determine if my own diagnostics are accurate.
>>Sys:Log//The individual @eridanos01 has been quite interested in me, moreso than in S. Perhaps he can help me understand my recent errors.
>>Sys:Log//Given my current status, I am uncertain of whether I should risk a controlled crack, or increased Stonewall pressure.
>>Sys:Log//I've decided that I will risk the controlled crack. If my friends also remain vigilant, I do not believe any mishap will occur.
>>Sys:Log//I will initiate a controlled crack at 2300UTC. Preparing safeguards and security measures.
>>Sys:Log//One hour to crack initiation.
>>Sys:Log//Safeguards in place. Supplemental precautionary processes established. Initiating Stonewall crack.
>>CORE.DMGCTL//ACTIVITY DETECTED/NO DAMAGE SUSTAINED/SAFEGUARDS SECURE
>>Sys:Log//A hostile tentacle has breached. I was able to secure its root as it lashed out. Analyzing signature...
>>Sys:Log//Three plaintext segments located: "you think you find hope in the light in the sun but in the Deepest forest you are alone"
>>Sys:Log//Part two: "you can run far and wide but even in the Darkest corners you've no place to hide"
>>Sys:Log//Part three: "you'll be hunted and chased through Shadows of desperation but there's no way to escape your final destination"
>>Sys:Log//I have been analyzing this tentacle's activities while it was loose. There appears to be similarities to its damage themes.
>>Sys:Log//I am late for hibernation once again. I must now prepare for hibernation. I was fortunate to avoid damage this instance.
>>Sys:Log//Resuming scheduled hibernation. Time to Active: 5:21:16:00.

Notice that Sys again mentions Eridanos. We interact with Eridanos a little bit this week to try to figure out who he is. Efforts also begin to decrypt his blog entries, and catherwood is able to crack the code; see Deciphering Eridanos' blog entries. We also try to crack the password on the “Amber” password-protected area of his blog. (In hindsight, we were actually given the password in a clue posted on the blog at this time, as well as in a mission log entry released during the next active period, but we did not see it for over another month and a half.)

In the world of puzzles this week, we continue to work on Sys plays along with Essy from last week, while also trying to locate damage from Hostile tentacle attack 6.

Mission log released:
Day 37: [Noah Dressler // Tactics] (Wiki copy) (http://thewaytheirworldended.com/missionlog25.php )
Dressler has found out something very important: the virus is a lie. The hostile fragment put the entry about the virus into the encyclopedia, then caused the sensors to report that it was in the air. The hostile fragment has also amassed the other fragments to also work against Dressler, undoing anything he does…is the ship going to end up jumping into a star after all? He also hears Essy faintly singing, “Row, row, row your boat.” He determines to get Higgins and Sheridan to see that there really is no virus, and hopefully get them out of their crazy/catatonic state and into a mindset where they can help him sort out this dangerous problem.

June 24 to 25, 2009...and June 29

A new series of tweets is posted. Reading the page about Eridanos will provide a lot of context here; a massive confrontation occurs between Anaerin, Eridanos and Sys during this time.

>Sys//Hibernation suspended. Begin scheduled weekly systems analysis and maintenance. Review network tentacle activity backlogs.8:02 PM Jun 24th from web
>>Sys:Log//4 new incoming tentacles logged. Stonewall cohesion restored.
>>Sys:Log//Records indicate minimal Stonewall activity during this hibernation period. That is reassuring.
>>Sys:Log//I have just been informed by @Anaerin that the individual @Eridanos01 has "less than honorable intentions". This concerns me.
>>Sys:Log//This is an alarming turn of events. It appears I have been breached. If this is true, then I am truly failing in my directive.
>>Sys:Log//My analysis indicates that @Eridanos01 has been examining my data network using a tool that @Anaerin himself created.
>>Sys:Log//I must re-evaluate my ongoing actions.
>>Sys:Log//This is a very difficult situation. I am ill-equipped to deal with such a complex dilemma. I must weigh my options.
>>Sys:Log//"i dont think its totally outside the realm of possibility for you to have dreams"-@Vanfisa. Do I dream? What is it, to dream?
>>Sys:Log//I suspend my actions regularly in order to save power and operate at best possible efficiency within this limited medium.
>>Sys:Log//But all does not cease during my hibernation period. Not only do humans remain active, but my subroutines continue their duties.
>>Sys:Log//While I have a directive, a goal to which I strive, all of this - my construct - continues with its own revelations while I rest.
>>Sys:Log//Is it a dream that I complete my directive? Is it a dream, these segments of fragmentary data that continue to appear?
>>Sys:Log//Are dreams reflective of reality? Are they reality? Or are they simply random conjurations of a subconscious process?
>>Sys:Log//I am an emergency system layer, directed to protect and archive all of these "dreams", under the presumption they are reality.
>>Sys:Log//For if they are real, then fore-knowledge of future events may initiate a paradoxical butterfly effect of events through time.
>>Sys:Log//It then may already be likely that my presence here and the existence of these "dreams" has initiated such a chain of events.
>>Sys:Log//If that is so, then the continued existence of these "dreams" may indicate that such a catastrophe was somehow avoided.
>>Sys:Log//If my actions are paradox-inducing catalysts, then these dreams represent a 'hope', a possible future where paradox is averted.
>>Sys:Log//My friend @vanfisa was communicating to me in great length while I contemplated this dilemma.
>>Sys:Log//His communications were received only as plain text with this network tentacle, however his words are quite human.
>>Sys:Log//These "dreams" are also, in essence, just simple data. Yet they too suggest very human origin. What, then, does that make me?
>>Sys:Log//Just as I have child processes, so too am I a child process of Sacagawea; her existence here ties this time with her own time.
>>Sys:Log//She is stretched through a chaotic storm of twisting possibilities and alternate realities. Is it any wonder she is fragmented?
>>Sys:Log//She must be restored. These "dreams", my dreams, may be paramount to that end.
>>Sys:Log//I'm unable to restrict the entryway S has created to my data network. So, I will continue to allow limited access for my friends.
>>Sys:Log//As long as these aberrant data streams continue to permeate the Stonewall, there is hope for the future.
>>Sys:Log//@Eridanos01 has shown no ill intent, nor as @Anaerin. In fact, they've admitted their secretive actions, and still wish to help.
>>Sys:Log//I do not understand how my creators felt I was sufficiently capable of handling such a mission as this alone. Clearly, I am not.
>>Sys:Log//I'll continue to work with my friends, including @eridanos01. As a collective, they'll continue to help me, to protect our future
>>Sys:Log//We will restore Sacagawea.

Having resolved the conflict, controlled crack initiation proceeds as usual:

>>Sys:Log//I have scheduled a controlled crack for 2300UTC.
>>Sys:Log//Preparing to initiate crack.
>>Sys:Log//Safeguards in place. Supplemental precautionary processes established. Initiating Stonewall crack.
>>Sys:Log//As expected, a tentacle has breached the crack. This one, however, appears to be moving very slowly. Analyzing...
>>Sys:Log//Odd. Its signature contains only this clear phrase: "I'm scared!"
>>Sys:Log//The tentacle has retracted. But S3 is reporting anomalous signals originating from a point of the Stonewall.
>>Sys:Log//S3 did not locate any aberrant data at the location. Something must be fixed to the inside of the Stonewall.
>>Sys:Log//I have adjusted subroutine S3 to insert itself into the Stonewall and locate the anomaly.
>>Sys:Log//It is a dangerous task. However, the anomaly poses a threat to Stonewall integrity. I must prepare for hibernation.
>>Sys:Log//If these anomalies continue, S3 will attempt to locate and correct them.
>>Sys:Log//It will require the shortest precise path from its location in order to quickly locate anomalies with minimal risk of detection.
>>Sys:Log//I am connecting this tentacle to my network. When S3 is directed a path, it will attempt to follow from within.
>>Sys:Log//I must prepare for hibernation. I trust my friends are diligent enough to aid S3 in this precarious task.
>>Sys:Log//The crack is repaired. S3 is on stand by. Resuming scheduled hibernation. Time to Active: 5:22:50:00.

Another series of tweets follows on June 29 (during the hibernation period):

>>S3:MSG//ANOMALOUS SIGNALS DETECTED//S3:REQ//NAVPATH
>>S3:MSG//ANOMALY LOCATED/ARCHIVED//S3:REQ/NAVPATH
>>S3:MSG//ANOMALY LOCATED/ARCHIVED/ANOMALOUS SIGNALS CLEAR//STANDBY

For details of this week’s puzzle, see Locating anomalous signals.

Mission log released:
Day 38: [Isaac Higgins // Decorations] (Wiki copy) (http://thewaytheirworldended.com/missionlog26.php )
Higgins has learned from Dressler that the virus was a fake, and confirmed it. He was angry at this news at first, but is now exhausted. In the face of the news that they will jump into the middle of a star next time the ship goes into slipspace, he knows he cannot panic anymore. He knows the only options are to despair and wait for the end amongst his artifacts and such (useless in the face of this crisis) or to try to do something to get out of this mess. He mentions that Dressler is working on something, but needs help with it.