Hostile tentacle attack 8

From Intimation

Here is the Twitter feed for this week:

>>S5:MSG//ERROR/ANALYZING12:07 AM Jul 16th from web
>Sys//Hibernation suspended. A system error occurred during activation. S5 has located and corrected a glitch from the recent altercation.
>>Sys:Log//Scheduled systems analysis and maintenance complete. 7 new incoming tentacles logged. Stonewall cohesion at full strength.
>>Sys:Log//Backlogs indicate little to no Stonewall activity since entering hibernation. I am curious as to the status of S.
>>Sys:Log//S4 remains quarantined. During the altercation with the tentacle, S5 managed to sever the interface. S4 was saved in the process.
>>Sys:Log//It was therefore prudent to place S4 in quarantine, not knowing what effects may have befallen it while in the tentacle's grasp.
>>Sys:Log//AI does not simply vanish into non-existence. There must be reason to this silence.
>>Sys:Log//I have come to the decision, with the help of my friends, to initiate a controlled crack.
>>Sys:Log//Due to the extreme volatile nature of the situation, I am enlisting each active subroutine to help guard the crack.
>>Sys:Log//I will initiate the crack in 50 minutes.
>>Sys:Log//It is vital that I determine the status of S. This is the only way.
>>Sys:Log//Safeguards in place. S1, S2, S3, S5 prepared. S4 quarantine holding. Preparing to initiate crack.
>>Sys:Log//Initiating Stonewall crack.
>>S5//ALERT/SYS:SEIZED//UNABLE TO SECURE//REQ:S1-3//CONFIRM
>>S4:MSG//ERRANT INTERNAL STREAM DETECTED//DUMPING
>>S5:MSG//S4 DATASTREAM DUMP//LOC:[1]
>>S5:MSG//SYS:STATUS//UNKNOWN

Yes, that’s right, the hostile tentacle seized Sys and took it captive. S5 was “unable to secure” Sys (i.e., keep it from being abducted). Not good.

S4, though under quarantine, found and dumped an errant internal datastream, to which S5 gave us a link. The link, http://bit.ly/104eI4 , led to http://thewaytheirworldended.com/SYS/VISUALIZE/S4_DATADISRUPTION-3 , a mostly-monochrome video that seems to be from the perspective of someone running through a forest, followed by a picture of a skull, while coloured blotches similar to the ones used for the sand paintings scroll across the screen.

Nyst was able to figure out “a rough drawing of the paint position and direction it scrolled”:

dante observed, “Looking at the video and Nyst's nice map of the dots, I realized that the different 'sweeps' of the dots overlap -- that is, you can piece together all the dots together by noting which dots from the end of previous set are the same as the beginning of the current set. It's also pretty clear that the dots are in some sort of grid.” He posted a picture of the dots assembled into this grid:

He translated these dots from Braille and found that they read MYTIME / HASCOME in two rows, leading to http://thewaytheirworldended.com/MY-TIME-HAS-COME , another sand painting puzzle.

Filling in the sandpainting generates this image:

drizjr identified the constellation as Phoenix and the highlighted star as Ankaa, leading to http://thewaytheirworldended.com/ANKAA/ …a rather creepy and morbid picture of skulls.

As before, downloading the image and manipulating it revealed hidden graffiti:

This led to the discovery of http://thewaytheirworldended.com/WHO-AM-I/ .